What the account shows
For every round the desk describes, the authoritative account of what happened is the history, not the game screen. A round that settled while the connection was down appears there as a normal round; a round that was voided appears with the stake returned. This page sets out what the record holds and how to read it after an interruption.
- interrupted and resumed
- 1,728
- outcome matched the server
- 100%
- voided and returned
- 1,152
- rounds restarted
- 0
- record disagreements
- 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.
The account history is the authority on an interrupted round: it records the stake, the outcome and, for a voided round, the returned stake. Because the round is written to the server before the client is told, the history agrees with the round state on every sampled interruption, including the 1,728 that settled while the player was away.
Four lines a record can hold for one interrupted round
| State | What the record shows | Balance effect |
|---|---|---|
| settled | the stake, the outcome and the round identifier | outcome paid |
| voided | the round marked void, with the stake returned | stake returned |
| resumed | the round continued to settlement after a reconnect | outcome paid |
| no default | a timeout resolved by the passive action | outcome paid |
The record does not distinguish a round you watched from a round you did not beyond the state it holds. A settled round is a settled round, which is why the history is a cleaner place to read an interruption than the screen that froze.
Why the record and the screen can disagree for a moment
The record is written at the decision point; the screen is rendered when the client asks for it. Between those two, the balance can look wrong - a win that has not been credited to the display, or a void whose return has not yet reappeared. The disagreement is a timing gap, not a lost round.
Worked example / samples E and I
- interrupted rounds not voided: 1,728
- of those, outcome matched the server record: 1,728 (100%)
- rounds restarted from the beginning: 0
- record disagreements in the sample: 0
- time for the display to catch up after a reconnect: about 1 second
Reading a record after an interruption
- Find the round by its identifier and read the state: settled, voided or resumed.
- Check the balance effect against the state; a void should show the stake returned, not a loss.
- Give the display a moment after a reconnect before comparing it with the record.
- Treat the record as the version to escalate on; the game screen is a rendering of it, not a second source.
- Keep the round identifier for any query, because it is the one key both the record and support share.