A result that can be checked
AREN8 does not ask a leaderboard to trust a number sent by a browser. A competitive result is built from a server session, recorded inputs and an independently replayed game.
What deterministic means
A deterministic engine produces the same result from the same seed, stored rules and timestamped input sequence. It does not make the game predictable or remove player choice. The player still chooses every placement; what can be repeated is the engine’s response.
A competition session snapshots its engine version and ruleset. A later software update must not silently reinterpret an older run. Weekly participants share the same event seed. A Tournament additionally stores a competition contract that binds the event, seed, engine and rules hash.
Why a client score is not enough
The browser must show immediate feedback, but the end-user device is not a trusted authority for a public leaderboard. AREN8 treats the displayed score as a claim. The server receives the moves and timeline and calculates the result again with its trusted engine.
If only a number were submitted, it could be changed without playing. Replay verification makes every point depend on an allowed input. The server also checks session ownership, expiry, engine version, rules and a legal terminal state.
Equal rules across different devices
Players use different phones, displays and connections. AREN8 separates simulation from visual rendering: a faster display can make motion look smoother, but it cannot change collisions, piece order, valid actions or the server scoring rule. Inputs are placed on the simulation timeline.
Network access starts the session, saves checkpoints and submits the result; it is not a source of extra points. If saving is interrupted, the client should offer recovery or retry. An unverifiable result is not silently promoted.
Anti-cheat without punishing players
Verification is not an accusation. It makes a leaderboard entry explainable. Rejection reasons are stored in diagnostics so a broken session, version mismatch, interrupted payload and prohibited input can be distinguished.
Security internals are not exposed in a way that helps bypass them, but the public contract is clear: a result belongs to one server session, final submission is one-time and the trusted replay must reach the same legal outcome.
Where strict verification applies
Verification matters most in Weekly and Tournament, where players are directly compared. Verified Classic and Journey results also use server logic, but their progression purpose is different. Admin test runs must not grant public rewards or affect fair rankings.
Journey power-ups belong to progression and cannot improve Weekly or Tournament scores. AREN8 can therefore offer long-term inventory without mixing purchased or earned assistance into competitive rules.
Frequently asked questions
Does AREN8 record a video of the game?
The primary evidence is a compact replay: seed, versions, rules, timestamps and inputs. A replay view reconstructs the run from those data.
Can a high-refresh display generate more points?
No. Rendering frequency is separate from simulation and the server recalculates the score from the same deterministic rules.
What happens to a rejected result?
It does not enter a verified leaderboard or replace a better valid score. The technical reason is retained for diagnostics.