◎The Round In Progress round state Open the partner account
paid
Affiliate disclosure. The partner link in the masthead and in the band beside the copy on this page is a sponsored link to a partner operator, and this site may be paid if you open an account through it, at no extra cost to you. It carries rel="sponsored noopener" and opens in a new tab. A desk about what happens to a round when the connection breaks should not leave its own funding unsaid: one link funds the site, no operator is named, rated or recommended anywhere on it, and it describes no real game, provider or account.
The Round In Progress / the resume
Reconnecting to a round that is still running

Reconnecting and what it restores

When the client comes back after a break, it does not start the round again - it asks the server for the state. That is why a reconnection can show a round resumed mid-way, and why the outcome it shows always matches the server record. This page takes the resume apart, including the cases where the reconnection restores nothing.

Desk spec
interrupted, not voided
1,728
reconnected within a minute
63.9%
state restored
83.3%
outcome matched the server
100%
round restarted from zero
0
runtime javascript
none
The round-state railsample B / the four stages of a game round and what a break costs at each
stage 01
placed / running

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.

stage 02
decision / interrupted

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.

stage 03
decided / settled

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.

stage 04
void / returned

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.

Of 24,000 sampled rounds, 2,880 met an interruption (12.0%). On 72.9% of the dropped connections the round had already been decided at stage 03, so the only thing lost was the display; the risk sits at stages 01 and 02, and only when the rules have no default action.
Direct answer

A reconnection restores the server state of the round, not a replay of it. Of the 1,728 interrupted rounds that were not voided, the state was restored on 1,440 (83.3%) and the outcome matched the server record on all 1,728. A round is never restarted from the beginning: it is either resumed at the state it holds, or it is voided.

What the client asks for, and what it gets

  1. The client reconnects and asks for the round state. It sends the round identifier, not a request for a new round.
  2. The server answers with the state it holds. Running, interrupted, decided, voided or settled. The client does not decide this; it renders it.
  3. If the round is still running, the client resumes it. The round continues towards the decision point that is still open, with the window as the rules define it.
  4. If the round was decided while you were away, the client shows the result. The balance is updated from the record; the animation may be skipped entirely.
  5. If the round was voided, the client shows the void. There is nothing to resume; the stake has returned.

That is the whole resume, and its defining property is that the client never owns the round. Of the 1,728 interrupted rounds that were not voided, the connection returned within one minute on 1,104 (63.9%) and the state was restored on 1,440 (83.3%).

The 16.7% where nothing was restored

A state restored rate below 100% sounds alarming until the arithmetic is read: of the 1,728 interrupted rounds that were not voided, 288 (16.7%) were not restored to the client because the round had already reached its final state on the server - it had settled or been voided while the client was away. The state was held, but there was no longer a state to resume.

Worked example / sample E

  1. interrupted rounds not voided: 1,728
  2. state restored to the client: 1,440 (83.3%)
  3. already final on the server, shown as a result: 288 (16.7%)
  4. outcome matched the server record: 1,728 (100%)
  5. rounds restarted from the beginning: 0
The gap is not lost rounds: it is rounds that finished before the client returned. Every one matched the server record, and none was restarted.

Reconnecting well, and the limits of it

  • Reload the game rather than re-staking. A reload asks the server for the round state; a re-stake opens a new round.
  • Wait for the reload to resolve before touching the balance: the round may settle a moment after the screen returns.
  • Do not assume a resumed round is a second chance. It is the same round at the state it holds, with the same decision window.
  • If the reload shows a void, the stake is already on its way back; nothing further is needed.
  • If the round does not appear at all, the authority is the account history, not the game screen. What the account shows.
What the account showsthe statement is the authority, not the screenSettlement while you were gonethe 60.0% that settled as placedBefore you play on a weak connectionthe figures to check in the terms first