How a score reaches the leaderboard
The on-screen score gives immediate feedback. A public result exists only after the server connects it to a valid session and replays the recorded game.
Blockfall scoring
Blockfall base points are 100 for one row, 200 for two, 300 for three and 800 for four. Here is an example excluding drop points: a first four-line clear gives 800. If the very next piece also clears four rows, it gives 800 + 400 back-to-back bonus + 2 × 50 combo bonus = 1300; the two clears total 2100. The combo grows when consecutive pieces clear rows and resets when a piece locks without a clear. Soft drop adds 1 point per row descended; hard drop adds 2. Those movement points are separate from this example.
Journey can add obstacles, rising rows or timed targets, but each session stores its exact rules. A leaderboard compares only verified results that belong to the relevant mode and event.
Colorfall scoring
In Colorfall Classic, each cleared piece earns a base value and later cascade waves in the same move use a larger multiplier. A prepared cascade can therefore be worth more than several isolated matches of three.
Journey uses a newer engine whose special pieces, blockers, goals and star thresholds are part of a published level revision. Completing the level may require both enough score and every listed objective.
Session and replay data
Starting a run creates a unique session token, seed, engine version, rules version and rules hash. The browser records player inputs on the game timeline. Recoverable checkpoints are submitted during longer games so a closed page or temporary network pause does not immediately destroy the attempt.
A checkpoint is not a new final result and cannot rewrite history. The final input list must extend the prefix already held by the server. One session accepts one terminal submission, so retrying cannot grant duplicate leaderboard entries or rewards.
Server-side replay
On submission, the server checks the token, owner, session state, deadline, engine version, rules hash, input structure, timestamp order and duration limits. It then starts the same engine with the same seed and applies the inputs in order.
The client’s claimed score may be retained for diagnostics, but the verified score comes from the server replay. A competition run must reach a legal terminal state: game over or the exact configured time limit. An unfinished state cannot become a final record.
Verified, rejected and recoverable
VERIFIED means the replay matched its session and the server calculated a result. REJECTED means the input sequence did not pass the contract and cannot enter the leaderboard. A transport or server failure may remain recoverable so the same valid payload can be sent again.
The interface should not show raw JSON or pretend that a failed submission succeeded. It offers retry or a safe route back. An earlier verified best remains even when a new attempt scores less or fails verification.
A replay is an input record, not a video of the score
In a Blockfall replay, an input records an action such as moving left or rotating and its game timestamp. The server does not watch pixels or read the score from a screenshot. It reconstructs the game associated with that session and applies the recorded actions. Colorfall records the swap coordinates and timing instead. A client sending a larger claimed score without the corresponding legal play does not thereby earn that score.
Three situations should be kept separate. A legal completed replay can become VERIFIED. A contradictory or invalid replay cannot become a ranked result. A request that never reaches the server may need a retry, but a network problem is neither proof of cheating nor proof that a result was saved. Use the result screen’s actual confirmation. Retrying the same accepted submission must not create a second reward or a second attempt result; starting another game is a different operation with its own session.
A result can need review without being lost
The score shown at the end of play is not by itself proof that a public result has been accepted. The server reconstructs the run and the competition may also place a result under fair-play review. A held result stays out of the official ranking while it is reviewed; this is not the same as a final finding of cheating.
Read the result message and your account notification. They explain whether submission is still pending, a retry is available, or a review is needed. An attempt restoration is shown when it actually occurs; do not assume every connection failure or held result grants a new attempt. If you need help, send support the competition, approximate time and the visible message. Do not send passwords or payment details.
Frequently asked questions
Does the leaderboard use the latest or the best result?
Classic and Weekly use the best verified result for their ranking rules. A rejected attempt does not replace it.
Why does the server replay the game?
It prevents the browser’s number from becoming the authority. Every point must arise from legal inputs in the same engine.
Does a lost connection always lose the run?
Not necessarily. Checkpoints and recoverable submission can preserve a valid session, but final verification must still complete.
Does a result awaiting review mean I have been disqualified?
No. Review and a final decision are different states. Follow your result notification; the held score is not counted publicly while the review is open.

