Structured User Story #28 - Check followed by Raise and Call

USE CASE #28

During a game with two players, a player can 'check' and the next player can raise (place a bet) and then the first player can then call that raise/bet. This also works for more than two players of course.

Preconditions

A server is running with users connecetd to it and a game is started. If no-one has bet this round, then a user can check and this process has the potential to start along with many other variants. We exclude those variants here since the basic ideas are encompased in the first five use cases anyway!

Success End Condition

Both players have now bet an equal amount of money in the pot, where the first player hadn't bet anything initially.

Fail End Condition

If the person folds rather than 'calling' the raise, then this is a different action, and the first player wins by default (unless, of course, there are more players)

Trigger

One user checks, another user raises/bets.

Description Someone the runs the server on a LAN.
Gui's are running and users are connected (and start a game).
The first round of betting with the blind-bets is over, so all thats left is for users to either check or bet around the table.
When a user bets, then others can either call the bet, raise it, or fold out of the hand and forfeit any money already in the pot.
This process repeats until everyone has called a bet (or checked thru or folded to a winner or series of callers). Then the server moves on to the next action in the game process.