Game Leaderboards and High Scores
Design scoring and leaderboard periods with stable ranking, duplicate handling, privacy-aware player display and testable replay rules.
Define what the board compares. Record whether a higher score or lower time wins, whether each player keeps a best result or all attempts, and the game mode, rules and version that make scores comparable. Identify the board's official timezone, period boundaries, and tie rule. Keep all-time and seasonal records separate when both exist. ## Key Points - [Google Play Games Services leaderboard concepts](https://developers.google.com/games/services/common/concepts/leaderboards)
skilldb get game-design-skills/game-leaderboards-and-high-scoresFull skill: 30 linesGame Leaderboards and High Scores
Define what the board compares. Record whether a higher score or lower time wins, whether each player keeps a best result or all attempts, and the game mode, rules and version that make scores comparable. Identify the board's official timezone, period boundaries, and tie rule. Keep all-time and seasonal records separate when both exist.
Define the submission contract
Use a canonical result with player identity, ruleset, score, attempt ID and completion time from a trusted source when available. Derive score from authoritative outcomes in ranked play. Treat a submitted attempt ID as idempotent. A retry must return the recorded outcome without granting a new entry. Keep immutable accepted attempts for investigation and update the leaderboard view from them. Define when a disqualified attempt is removed and how its effect is audited.
Select a consistent tie policy. Shared rank can show two players as first, followed by third, while a deterministic display order keeps pagination stable. For exclusive rank, specify the tie-breaker in advance. Avoid using profile edits as a sort key. For elapsed-time boards, store a numeric base unit and render friendly formatting only in the UI.
Set period and visibility rules
Assign each accepted attempt to a period before ranking. Decide how delayed delivery or offline sync affects a closed period and expose that behavior in the game. Keep ruleset changes from silently mixing incompatible scores. When using a platform leaderboard, document how its social, public and time-span variants map to the product decision.
Display an approved public handle or anonymized name according to the privacy design. Offer a current-player view even when the entry is off the first page. Return clear empty, pending and unavailable states. Give participants a route to review a removed score or report abuse.
Verify boundary cases
Seed a board with tied scores and confirm that page turns preserve ordering. Submit the same attempt twice and check accepted count and rank. Test timestamps immediately before and after the cutoff, one late submission, and a profile rename. Use synthetic score data. In a current-player view, compare the displayed rank against the authoritative board query. Record the ordered fixture, rule version and observed results.
Sources
Install this skill directly: skilldb add game-design-skills
Related Skills
Game Mechanics
Trigger when designing core game mechanics, gameplay loops, progression systems, resource economies, risk/reward structures, or feedback loops. Use when the user asks about how game systems feel, what makes gameplay satisfying, emergent behavior, or how to structure the moment-to-moment play experience.
Game UI UX
Trigger when designing game UI or UX, including HUD layout, menu systems, tutorial design, onboarding flows, feedback systems, or input considerations. Use when the user asks about controller vs keyboard+mouse design, accessibility in UI, how to teach players without tutorials, or how to make interfaces that enhance rather than obstruct gameplay.
Godot Development
Trigger when developing games in Godot Engine, writing GDScript or C# for Godot, working with nodes and scenes, configuring signals, or using Godot's physics, animation, and rendering systems. Use for Godot project structure, scene composition, export pipelines, or Godot-specific patterns and best practices.
Idle Game Economy
Balance idle and incremental games by modeling upgrade costs, production rates, milestone pacing, offline gains and prestige with reproducible tests.
Level Design
Trigger when designing game levels, spatial layouts, player flow paths, difficulty curves, or environmental guidance. Use when the user asks about blockouts, pacing within levels, guided exploration, landmark placement, combat arenas, puzzle rooms, or the pipeline from graybox to final polish.
Mobile Game Optimization
Trigger when optimizing games for mobile platforms, managing thermal throttling, battery consumption, memory constraints, or touch input design. Use for mobile GPU profiling, texture compression, draw call batching, asset streaming on limited bandwidth, or shipping a game that runs well on devices from three years ago.