Leaderboard Rules and Fair Play
This page explains how Slitheroo handles live scoreboards, which runs count, and what can cause a score to be ignored. It exists so players and reviewers can see the rules in one place instead of guessing from the UI alone.
What Leaderboards Exist
- Daily Top 10: resets each UTC day and highlights the best runs for the current date.
- All-Time Top 50: keeps the strongest historical scores across the project.
Which Runs Count
Ranked runs are eligible for leaderboard submission. Daily Challenge uses a seeded board and is intended as a skill comparison mode, but the exact storage and display rules can change as the mode evolves. Zen is for practice and does not compete in the same way as Ranked. Timed mode is a score-attack variant and may be handled separately from classic ranked progression depending on the live rule set.
Nickname Rules
Your chosen nickname is the public label attached to your score. Use something stable so your progress stays recognizable over time. Nicknames that are abusive, deceptive, spammy, or obviously designed to interfere with the leaderboard may be removed or blocked.
How Duplicate Runs Are Handled
The leaderboard system is designed to prefer legitimate best runs instead of raw submission volume. Practical anti-spam controls are used so that one player cannot flood the board with repeated low-value entries or easy duplicates.
From a player perspective, the important rule is simple: use one nickname consistently and focus on real runs. If a score does not appear, it may have failed due to connection issues, validation, or backend protection rules.
What Can Invalidate A Score
- Network failure during submission.
- Malformed or suspicious payloads.
- Duplicate or abusive activity detected by the backend.
- Nickname violations.
- Future rule changes that narrow which modes count toward public rankings.
What To Do If A Score Looks Wrong
If your score is missing or the board looks inconsistent, send the nickname used, the approximate time of the run, the mode you played, and the score you expected to see to wsuperheros@gmail.com. That makes it much easier to trace whether the problem was local, network-related, or backend-related.