Leaderboard logic

Leaderboard

A strong leaderboard page needs more than a table. It should explain how positions move, which signals matter most, how ties are resolved, and how a match-level result differs from a season-level standing.

Placement logic Tie-break transparency Season movement
What users should see

A leaderboard is more useful when it explains the shape of competition.

The revised page gives the leaderboard more context so users can understand whether they are looking at a single challenge snapshot, a broader season picture, or a recognition layer that highlights strong repeat performance.

Match board

One fixture, one result set.

This is the most immediate ranking view and should explain who placed where after a completed challenge, including any score processing note.

Season board

A wider view of consistency.

Season standings help users understand how repeat quality, not just one strong result, contributes to reputation and recognition.

Spotlight board

Recognition for standout momentum.

This layer can highlight streaks, format mastery, or sustained placement quality for users who are performing well over time.

Archive board

Past rounds that remain easy to review.

Older leaderboard views help users compare form across different matches and understand how their profile has evolved from fixture to fixture.

How ranks move

Users should be able to tell why their position changed.

Live state Used during match action to show movement while performance data is still settling. This is helpful for engagement, but it should never be mistaken for a guaranteed final result.
Provisional state Displayed after play ends but before final checks are completed. This tells users that the challenge is nearly resolved, but minor adjustments may still affect placement.
Final state Shown after score processing, ranking logic, and tie-break review are complete. This is the version that should feed badges, streaks, and season records.
Tie-break order

Equal scores still need a visible decision path.

  • Published challenge score remains the first comparison point
  • Captaincy or format-specific rule can be used as the next separator
  • Consistency or earlier published system ordering can resolve true ties
  • The ordering logic should be stated before participation, not after disputes begin

Result: clearer ranking states and tie-break logic make the board feel more credible and easier to trust.

What users learn from it

A leaderboard should turn results into insight.

When written and structured properly, the leaderboard becomes more than a result sheet. It helps users compare challenge quality across formats, understand whether a captaincy decision worked, see how close they are to the next badge or tier, and judge whether their recent form is improving or flattening.

That is why this page now treats rankings as part of a larger profile system. A visitor should leave the leaderboard with a better sense of what they did well, where they lost ground, and what kind of challenge may suit them next.