Page 1 of 1

Poker Mavens 5.16 Released

PostPosted: Thu Jul 20, 2017 4:21 pm
by Kent Briggs
Upgrade page:


Added "Minimum name length" option to Account Settings. Previously this was fixed at 3, meaning that player names had to have at least 3 characters in them. Now the minimum can be anywhere from 1 to 10 characters. The max length is still fixed at 12 (to fit in the allotted space). Changing this setting does not affect existing accounts.

Localhost IPs now exempted from duplicate IP restrictions. Previously if you had "Allow duplicate IPs" set to No in the system settings or the ring table setting, that would also block the administrator from making more than one local connection on or 0:0:0:0:0:0:0:1. Now those two addresses are exempt from that setting.

Fixed bring-in/sitout bug in 7-card tournaments. If a player was sitting out in a Stud or Razz tournament and got the Bring-In and all remaining players just called that value, the sitter is folded right after that. However a bug in the server was telling the clients that the last player to call had folded instead of the sitter and thus the wrong cards were removed from the screens. Selecting "Refresh table" from the table menu would fix it but now that bug is permanently fixed.

Fixed all-in small blind bug in tournaments. If the small blind was all-in while the big blind was sitting out and everyone else folded, the small blind would win the entire big blind instead of just the portion that matched their all-in. That has now been fixed and the big blind receives a refund on the overbet.

Tournaments can now be started in resetting mode. Prior to version 5.15 the reset time was fixed at 30 seconds and thus it was only a short wait if you wanted to manually start the tournament again. But since that is now an adjustable setting that could last for days, the code has been changed to abort the reset period if the tournament needs to start again before then.

Improved error handing for SQLite write failures. Previously a fatal error (such as out of disk space) would trigger an error in the Accounts.db file write code that could not recover until the program was reset. Now the code will attempt a rollback after a fatal error to clear the last transaction so that if the fatal condition goes away, the file i/o code could continue on.