First-party policy
Fair Play and Leaderboards: How Boomnexa Validates Competitive Scores
A Boomnexa leaderboard is intended to compare runs played under understandable conditions. The platform separates local progress from score-bearing submissions, validates supported competitive runs on the server and records integrity evidence before a result is treated as eligible. This guide explains the rule path without pretending that any anti-cheat system is infallible.
Game facts used in this guide
- ✓Ranked submissions use server-issued run tickets where supported
- ✓Score envelopes are checked against game, duration and difficulty rules
- ✓Flagged runs can be excluded from leaderboard eligibility
- ✓Chat and community reports enter an admin review process
A local score is not automatically a ranked score
Many games keep immediate local progress so a run feels responsive. Competitive submission is a separate step. Supported ranked games send a bounded result envelope containing the game, score, duration, difficulty and run identity.
This distinction prevents a value written directly into local storage from becoming leaderboard evidence. Local bests can still help the player track practice without being presented as globally verified.
Run tickets bind a result to a play session
For supported arcade submissions, the server issues a short-lived run ticket before ranked play. The final result must match that ticket’s game and session context. Missing, expired or mismatched tickets fail closed rather than being accepted optimistically.
A run identifier is derived from server-selected session information and a nonce. Reusing the same envelope can therefore be detected instead of creating duplicate ranked entries.
Validation checks plausibility and consistency
The validator compares score, duration, difficulty and game-specific limits. Timing anomalies, replay attempts, device drift and statistical outliers can be recorded as integrity flags. A flag is evidence for review, not permission to publicly accuse a player.
Validated records distinguish verified status from leaderboard eligibility. That allows the system to retain an audit record while excluding a result that does not meet ranking rules.
What happens when a score is disputed
Players should report the specific score or behaviour through the available reporting path rather than confronting another player. Useful reports identify the game, displayed name, approximate time and reason for concern without publishing personal information.
An administrator reviews the stored run evidence and moderation context. Outcomes can include leaving the score in place, removing leaderboard eligibility or requesting further evidence. Automated systems do not issue a final public judgement about intent.
Community conduct is part of fair competition
Harassment, hate speech, sexual content, child-safety concerns, spam and scams can be reported from supported chat surfaces. Players can also mute another display name locally while a report is reviewed.
A high score does not grant permission to target another person. Moderation focuses on the recorded message or run, applies the published categories and keeps reviewer actions separate from public arguments.
Limits and transparency
No browser anti-cheat can promise perfect detection. Boomnexa therefore uses layered evidence, conservative eligibility decisions and human review for disputes. We avoid claiming that an anomaly proves cheating by itself.
Rules may evolve as games change. This page is maintained by Boomnexa, and material updates are dated. Players can use the support route to ask how a specific ranking rule applies.