Skip to the guide
WORKBENCHHow results are checked

Public record

Every saved run keeps how it was made

The game records how a run was played as you play it. A run helped by Strategy Finder, a Runbook, or continued from a saved replay stays marked that way, so it can never be presented later as an unaided Ranked Challenge.

Open the LeaderboardRead the rules

The five ways a run can be played

Solo

A Standard run played without Finder, a Runbook, or a replay fork.

Finder

A result produced by Strategy Finder or by branching from a Finder search.

Runbook

Standard play with a step-by-step build guide beside the board.

Fork

A continuation created from a position inside a saved replay.

Challenge

A locked Ranked Challenge run begun with a valid server-issued ticket.

What CERT means

  1. The player requests a ticket that locks difficulty, game version, and a server-chosen seed.
  2. The game disables Strategy Finder and guided builds for that run.
  3. The submitted replay has to match the challenge it was started from.
  4. The server checks that the run really came from that challenge, under the published rules, and that it is being submitted for the first time.
  5. A private server replays every move of the run under the exact same rules.
  6. CERT is awarded only when that replay ends in exactly the result you submitted.

CERT is a narrow technical claim. It says that a locked Ranked Challenge replay passed the published verification checks. It is not an account identity, a claim about who operated the device, or a general endorsement.

What the public Leaderboard accepts

  • A clear game version, and rules that match it
  • A game version that is still open for submissions
  • A complete move-by-move record that ends in the result it claims
  • A recognised record of how the run was played — unlabelled, experimental, or foreign saves are refused

All public categories can contain submitted runs. Competitive outcome categories filter those records; an empty category does not imply that submissions were lost.

Public and local boundaries

Replays stay on the player’s device until they deliberately submit a save to the public Leaderboard. A submitted run can include a chosen nameplate and coarse device context used to describe the conditions of play. The game does not publish full browser strings, IP addresses, ticket secrets, or private client identifiers.