Briggs Softworks

Can you please consider adding a "time" cost payment structure vs Rake? Timed cash game play is very common in poker, especially the higher end stakes in private brick and mortar rooms, and having a software that supports this would be nice VS having to create timed functionality from the ground up using API functionality.

Thanks!

Timed rake is common in brick and mortar setups only because it's easier to implement. There's no reason to do it in online play where it's automated per hand. You would just get people trying to game the system by only playing hands in between the rake times.

> There's no reason to do it in online play where it's automated per hand.

There are major reasons to do timed play VS rake. For example, rake is illegal in some areas whereas timed play is not. There are also business case scenarios whereas you want to do timed play instead of rake. In short, allowing for timed play is an extremely valuable option to have support for instead of just rake.

> You would just get people trying to game the system by only playing hands in between the rake times.

This is only the case if timed play was limited and incorrectly implemented. Instead, I would suggest allowing the site operator the option of tying timed play to one of these 2 options:

- Timed play table-wide (this means all players play time at the same time on a table-specific timed event (eg, every 30 minutes for the whole table)) or

- Timed play player-specific (players pay time upon posting their first hand at the table and timed event (eg, every 30 minutes for the specific player) happens to each player individually based on their specific time information.

Further, you could add another option of doing timed play agnostic of specific table sitting and whollistic of a particular player's play. For example, if a player sits and plays across 10 tables, on and off, for a total table-sit time of 120 minutes, then you have __ occurances of ___ timed events that remove ___ credits to that player. This makes time for that player tied to the player's sit-time and no tied to a player time. This is likely the best option as it essentially micro-collects player time in a better fashion as it does not tie time play to a single table or to a single full table time session.

Hopefully you can understand this and consider implementing it right away!