Competitive Rulebook

Purpose

A Competitive Rulebook is the authoritative legal and gameplay document that governs ranked play, organized tournaments, and any mode where players compete for standings, rewards, or qualification. It defines the match format, the rating system mechanics, the season structure, the penalties for cheating and unsportsmanlike behavior, the disconnection policy, the dispute resolution process, and the leaderboard rules. Without it, every ruling is ad hoc, every penalty is debatable, and every edge case becomes a community crisis.

Competitive games live and die by player trust. A player who loses a ranked match and drops from Diamond to Platinum will accept the loss if the rules are transparent and consistently enforced. That same player will quit permanently if they suspect the system is arbitrary—if disconnections are sometimes forgiven and sometimes penalized, if boosters face no consequences, or if tournament seeding is opaque. The rulebook is what makes enforcement principled rather than personal.

The document also serves as a contract between the development team and the competitive community. It tells tournament organizers what formats the game officially supports. It tells content creators how leaderboard standings are calculated. It tells anti-cheat engineers which behaviors cross the line from aggressive play to exploitation. And it tells the customer support team exactly when a match result can be overturned and when it cannot.

This is a Required document for any game with a competitive feature. Without it, the team cannot distinguish between a bug report, a balance complaint, and a rules violation—three categories that require entirely different responses.

Who needs this document

What separates a good version from a bad one

Criterion 1: Rating system mechanics are specified with mathematical precision

✓ Strong: “Ranked mode uses a modified Glicko-2 system. Initial rating: 1500, initial RD: 350, initial volatility: 0.06. After each match, rating and RD are updated per the Glicko-2 algorithm. Rating gains/losses are displayed to the player as whole numbers. Placement: 10 matches required before rank is visible; during placement, RD decreases faster (1.5× normal). Players inactive for 14+ days accrue RD at 15 points/day, capped at RD 200. Displayed rank tiers: Bronze (0–1199), Silver (1200–1499), Gold (1500–1799), Platinum (1800–2099), Diamond (2100–2399), Master (2400+). Master tier shows exact rating.”

✗ Weak: “Players earn points for winning and lose points for losing. There are six rank tiers.” (No algorithm, no placement logic, no inactivity decay. Two engineers will implement different rating curves, and players will reverse-engineer inconsistencies immediately.)

Criterion 2: Penalty escalation is defined with concrete thresholds and durations

✓ Strong: “Leaving a ranked match before its conclusion triggers an abandon penalty. First offense: 30-minute queue ban + 50 rating point deduction. Second offense within 7 days: 2-hour queue ban + 100 rating point deduction. Third offense within 7 days: 24-hour ban from all competitive modes + 150 rating point deduction. Offenses decay after 7 clean days. Intentional feeding (detected via heuristic: 0 damage dealt, 5+ deaths, match duration > 5 minutes): same escalation ladder. All penalties are logged and visible to the player in their competitive history.”

✗ Weak: “Players who leave matches will be penalized.” (No escalation, no durations, no decay. Support staff cannot answer “when can I play again?” and players perceive enforcement as random.)

Criterion 3: Disconnection handling distinguishes crashes from abandons

✓ Strong: “If a player disconnects, the server holds their slot for 120 seconds. Reconnection within 120 seconds: no penalty, match continues. If the player does not reconnect within 120 seconds: the match is scored as an abandon for the disconnected player. Remaining players may vote to continue (4v5) or forfeit. If the team forfeits, the disconnected player receives a loss + abandon penalty; remaining teammates receive loss forgiveness (no rating change). The opposing team receives a normal win. Server crash (detected by all 10 players disconnecting within 2 seconds): match is voided, no rating changes for any player.”

✗ Weak: “Disconnected players will be handled fairly.” (No reconnection window, no distinction between client crash and rage quit, no impact on teammates. Every disconnection becomes a support ticket.)

Criterion 4: Season structure and reset logic are explicit

✓ Strong: “Seasons last 90 days. At season end: leaderboard snapshots are frozen and archived. Players in Master tier receive a cosmetic reward based on peak rating. Season reset: all ratings compressed toward 1500 by 50% (new_rating = 1500 + (old_rating − 1500) × 0.5). RD reset to 200 for all players. Placement matches: 5 required (reduced from 10 for returning players). Off-season: 3-day gap between seasons where ranked queue is disabled and only unranked/custom modes are available.”

✗ Weak: “Seasons reset periodically.” (No duration, no reset formula, no reward logic, no off-season plan. Players cannot plan their grind and community managers cannot announce accurate timelines.)

Common mistakes

Publishing rules after launch. Teams ship ranked mode and plan to “finalize rules later” based on player behavior. By the time rules are published, the community has established its own norms—and any official rule that contradicts community expectations is perceived as a retroactive punishment. Write the rulebook before competitive mode goes live, even if it’s short.

Using vague language that invites lawyering. Rules like “unsportsmanlike behavior will be penalized” create more disputes than they resolve. Players will rules-lawyer every word. Specify exact behaviors (leaving, intentional feeding, win trading, account sharing) with exact detection methods and exact penalties. Vague rules aren’t rules—they’re wishes.

Identical penalties for all offense severity. A player who disconnects once due to an ISP outage and a player who has abandoned 15 matches in a week are not the same. Without escalation tiers and decay windows, the system either punishes casual disconnects too harshly (driving away legitimate players) or punishes serial offenders too leniently (eroding competitive integrity).

Ignoring edge cases in team-based modes. What happens when a player disconnects before the match starts? What if a premade group has one player banned mid-tournament? What if a match ends in a draw but the format requires a winner? Each unaddressed edge case becomes a support ticket or a Reddit post. Enumerate them in the rulebook.

No version history or changelog. Competitive rules change—new penalties, adjusted rating formulas, modified season lengths. Without a versioned changelog, players cannot tell when a rule changed, and support staff cannot determine which ruleset was active when a disputed match occurred.

How to use this document

When to create it

Write the competitive rulebook after the game design document establishes the competitive mode concept (ranked play, seasons, skill-based matchmaking) but before the competitive mode enters any form of player testing—including closed beta. Players in beta will form expectations about how ranked play works, and changing rules after those expectations are set is far more costly than publishing clear rules from the start.

Who owns it

The competitive/esports designer or game director owns the rulebook. The engineering lead, community manager, and customer support lead are mandatory reviewers. Rating algorithm changes require engineering sign-off. Penalty changes require community and support sign-off, because those teams bear the enforcement burden.

How AI agents should reference it

get_standard_docs(type="video_game", features=["competitive"])
→ competitive_rulebook in documents[]
→ agent reads rulebook before implementing any ranked mode, penalty, or season system
→ agent validates that rating calculations match the documented algorithm
→ agent ensures penalty escalation logic matches documented thresholds and decay windows

The prompt_snippet — “Ensure the project has a competitive rulebook covering tournament formats, match rules, player conduct standards, and dispute resolution” — tells the agent to verify all four dimensions are concrete and enforceable.

How it connects to other documents

The Competitive Rulebook is downstream of the Game Design Document (which defines the competitive mode concept and player motivations) and upstream of several implementation documents. The Networking Specification must implement the disconnection detection and reconnection window the rulebook defines. The Anti-Cheat Design must detect the specific prohibited behaviors the rulebook enumerates—the rulebook says what is banned, the anti-cheat doc says how it’s detected. The Matchmaking Specification implements the rating algorithm and queue restrictions the rulebook describes. Community Guidelines establish general conduct standards that the rulebook extends with competitive-specific penalties.

Recommended Reading

• “Elo Rating System” on Wikipedia and the original paper by Arpad Elo — Foundational reading for anyone designing a competitive rating system; understanding Elo’s assumptions and limitations is essential before choosing Glicko-2 or TrueSkill.
• “Matchmaking in Multiplayer Games” by Josh Menke (GDC talks, various years) — Practical design talks from the lead matchmaking engineer on Halo and Overwatch; covers rating system design, season resets, and the tension between match quality and queue times.
• “Fair Play: How Online Game Companies Handle Cheating and Toxic Behavior” by various authors at Riot, Blizzard, and Valve — Industry case studies on penalty systems, tribunal models, and how published rulebooks interact with automated enforcement at scale.