Poker Mavens 4.25 Released
Posted: Tue Jul 29, 2014 2:54 pm
Upgrade page:
http://www.briggsoft.com/patches.htm
Changes:
Implemented new permissions system for restricting table and chat access to specific players. This gives a site administration better control over table (and chat) access without having to use passwords. For example, you may want to setup a "newbie" table that only new sign-ups can play on. Or implement a satellite tournament where both registration and/or unregistration is limited to specific players.
Each player now has a "Permissions" setting which can contain a comma-separated list of permission tokens. There is no limit to the number of tokens but each one must be 15 alphanumeric characters or less in length. Tokens are also case sensitive. Ring tables now have a "Play permission" and "Observe permission" setting which can be blank (giving everyone access) or can have a single permission token, giving access only to players who have a matching token. Likewise, tournaments now have "Register permission", "Unregister permission", and "Observe permission" settings. In the Client Settings group on the System tab, there is a new "Lobby chat permission", allowing you to restrict write access to the lobby chat feature.
The old Password and Private settings in ring games and tournaments still work but you cannot combine password and permission access together at the same table or tournament. Also, the old "Player chat" and "Observer chat" settings have been replaced with corresponding "Player chat permission" and "Observer chat permission" settings. So if you previously had either of these disabled, you will need to specify a permission token (that no one has) to replicate the disabling of those features. You can simply call that token "No" or any non-blank string that you want.
A new AccountsPermission command has been added to the API to facilitate adding, removing, or querying for individual permission tokens assigned to a player. The existing AccountsAdd and AccountsEdit can be used to set multiple tokens for an account. In the client lobby, a new "Show permissions" command has been added to the Account menu.
Bug fixes:
Fixed ring game add/clone bug that prevented table opening. In versions 4.21 through 4.24, if you created a new ring table and did not keep the default name, an index mismatch occurred internally that prevented the table from opening in the client (until it was edited).
Fixed table graphics rendering bug in client. Previously if you happened to open an active table in the middle of an animation, sometimes the table would not render any graphics elements.
Fixed TournamentsMessage recording bug in API. Now this command will correctly record the message in the hand history file if "Save player chat" is enabled in the log settings.
Fixed error message format bug in API. Previously there were several error responses that returned in legacy format even if JSON format was specified in the parameters.
http://www.briggsoft.com/patches.htm
Changes:
Implemented new permissions system for restricting table and chat access to specific players. This gives a site administration better control over table (and chat) access without having to use passwords. For example, you may want to setup a "newbie" table that only new sign-ups can play on. Or implement a satellite tournament where both registration and/or unregistration is limited to specific players.
Each player now has a "Permissions" setting which can contain a comma-separated list of permission tokens. There is no limit to the number of tokens but each one must be 15 alphanumeric characters or less in length. Tokens are also case sensitive. Ring tables now have a "Play permission" and "Observe permission" setting which can be blank (giving everyone access) or can have a single permission token, giving access only to players who have a matching token. Likewise, tournaments now have "Register permission", "Unregister permission", and "Observe permission" settings. In the Client Settings group on the System tab, there is a new "Lobby chat permission", allowing you to restrict write access to the lobby chat feature.
The old Password and Private settings in ring games and tournaments still work but you cannot combine password and permission access together at the same table or tournament. Also, the old "Player chat" and "Observer chat" settings have been replaced with corresponding "Player chat permission" and "Observer chat permission" settings. So if you previously had either of these disabled, you will need to specify a permission token (that no one has) to replicate the disabling of those features. You can simply call that token "No" or any non-blank string that you want.
A new AccountsPermission command has been added to the API to facilitate adding, removing, or querying for individual permission tokens assigned to a player. The existing AccountsAdd and AccountsEdit can be used to set multiple tokens for an account. In the client lobby, a new "Show permissions" command has been added to the Account menu.
Bug fixes:
Fixed ring game add/clone bug that prevented table opening. In versions 4.21 through 4.24, if you created a new ring table and did not keep the default name, an index mismatch occurred internally that prevented the table from opening in the client (until it was edited).
Fixed table graphics rendering bug in client. Previously if you happened to open an active table in the middle of an animation, sometimes the table would not render any graphics elements.
Fixed TournamentsMessage recording bug in API. Now this command will correctly record the message in the hand history file if "Save player chat" is enabled in the log settings.
Fixed error message format bug in API. Previously there were several error responses that returned in legacy format even if JSON format was specified in the parameters.