The states a round can be in
A round that is interrupted does not disappear; it holds a state until the rules move it on. There are six states in the samples - placed, running, interrupted, voided, resumed and settled - and reading them is the whole of the desk in one page. This page defines each one and gives the rule that moves a round from one to the next.
- states of a round
- 6
- interrupted rounds
- 2,880
- voided, stake returned
- 40.0%
- resumed and settled
- 60.0%
- outcome mismatch
- 0
- runtime javascript
- none
The stake is committed and the round is running. A break here, before the round is decided, is the only break that can void the stake - and only if the rules have no default action.
The decision window is open. A dropped connection or a timed-out decision is decided here: by a default action, by a void, or by the window expiring.
The outcome is fixed on the server. A break now is a display problem only: the round settles as decided and the result is shown on reconnect.
The round is voided and the stake returns to the balance. This is a rule outcome, not a loss: the money is where it started.
A game round holds one of six states: placed, running, interrupted, voided, resumed or settled. The state says what the rules will do next, and the stake sits in exactly one place at each. An interruption is not a seventh outcome; it is a state that the rules then move on - to a void that returns the stake or to a settlement that stands.
The six states, and where the stake sits in each
| State | What it holds | The rule that moves it on | Stake |
|---|---|---|---|
| placed | the stake is committed, the round has not started | the round starts, or the round never starts and voids | at risk |
| running | the round is being played out | the outcome is decided | at risk |
| interrupted | contact with the client is lost | a default action, a void, or reconnection | held |
| voided | the round is cancelled by a rule | the stake returns to the balance | returned |
| resumed | the client is reconnected to the round | the round continues to settlement | at risk |
| settled | the outcome is fixed and the balance updated | nothing - the state is final | paid |
The table is the answer to most interruption questions in one view. A stake is never in two places at once: it is at risk, held, returned or paid, and the state tells you which.
Why interrupted is a state and not an outcome
It is tempting to read an interruption as a result - as though the round ended when the connection did. The samples say the opposite. Of the 2,880 interrupted rounds, none was left in the interrupted state: 1,152 were moved to voided (40.0%) and 1,728 to resumed and then settled (60.0%). The interruption is a way-point.
Worked example / sample D and sample E
- interrupted rounds: 2,880
- moved to voided, stake returned: 1,152 (40.0%)
- moved to resumed and settled: 1,728 (60.0%)
- left in the interrupted state: 0 (0.0%)
- of the 1,728 resumed, state restored: 1,440 (83.3%)
- of the 1,728 resumed, outcome matched the server: 1,728 (100%)
Reading the state from the screen
- A frozen screen after an animation has played usually means the round already reached settled; the money has moved.
- A frozen screen with a countdown on it means the round is interrupted with a decision window open - the state where a default action can decide the stake.
- A message about a void is the voided state; the stake is on its way back to the balance.
- A reload that shows the round still in progress is the resumed state; the round was restored from the server, not restarted.
- The authoritative state is in the account history, not on the game screen. What the account shows.