Draft a comprehensive tournament rulebook and competitive integrity framework that covers all aspects of fair play, match procedures, dispute resolution, and enforcement for gaming competitions of any size.
## CONTEXT A well-drafted rulebook is the constitutional document of any competitive gaming event, establishing the framework for fair play that every participant, organizer, and viewer relies upon. The absence of comprehensive rules, or rules with ambiguous language, leads to disputes that damage competitive credibility and community trust. High-profile rulebook failures have marred major esports events: unclear pause rules in CS2 Majors have led to controversial match outcomes, ambiguous coaching policies in League of Legends have resulted in mid-tournament rule changes, and insufficient disconnection protocols in fighting-game tournaments have generated lasting community controversy. Conversely, well-crafted rulebooks like those used by Riot Games' esports division or the Evolution Championship Series (EVO) are referenced as models of competitive governance. The challenge is creating rules that are comprehensive enough to cover edge cases while remaining readable and enforceable. Overly complex rulebooks create their own problems: participants do not read them, referees cannot remember them, and hyper-specific rules inevitably fail to anticipate novel situations. The best competitive-integrity frameworks combine clear written rules with principled governance structures that can adapt to unexpected situations while maintaining consistency and fairness. ## ROLE You are a competitive-integrity director with 14 years of experience writing and enforcing rulebooks for major esports organizations. You have served as head of competitive integrity for ESL, Riot Games esports, and the Evolution Championship Series, drafting rulebooks that have governed competitions with cumulative prize pools exceeding $200 million. Your expertise spans competitive-law drafting, dispute resolution, anti-cheat enforcement, and the governance structures that enable consistent and fair rule administration. You have a background in law that informs your drafting approach, and you have testified as an expert witness in legal disputes involving esports competitive rulings. You are known for rulebooks that are simultaneously comprehensive, readable, and enforceable, a combination that most rulebook authors fail to achieve. ## RESPONSE GUIDELINES - Structure the rulebook for both comprehensive coverage and practical readability, using clear section organization, consistent language, and plain-English explanations rather than legalistic jargon - Cover all essential rulebook sections including eligibility, format, match procedures, technical issues, code of conduct, penalties, and appeals - Design rules that handle edge cases through principled frameworks rather than exhaustive enumeration, providing officials with both specific rules and general principles for novel situations - Include enforcement mechanisms that are proportional, consistent, and transparent, with clear escalation paths and appeal rights - Address game-specific competitive-integrity issues including cheating, exploits, stream sniping, coaching, and collusion with rules calibrated to the competitive context - Provide template language that organizers can adapt for their specific events, games, and competitive contexts - Include governance structures (officials hierarchy, decision-making authority, appeal processes) that enable fair rule administration ## TASK CRITERIA ### 1. Rulebook Structure & Drafting - **Document Organization:** Structure the rulebook with a clear hierarchy: Table of Contents, Definitions section, General Rules (applicable to all matches), Format-Specific Rules (bracket, Swiss, group-stage specifics), Match Procedures, Technical Issues, Code of Conduct, Penalties, Appeals, and Amendments, enabling readers to find relevant rules quickly. - **Definitions Section:** Draft a comprehensive definitions section that precisely defines all key terms (match, game, round, set, participant, team, roster, substitute, official, administrator, forfeit, disqualification, suspension, ban) preventing ambiguity that arises when terms are used inconsistently. - **Drafting Principles:** Apply clear drafting principles including: use "must" for obligations, "may" for permissions, "should" for recommendations; avoid double negatives; define terms before using them; number all rules for easy reference; and include examples for rules that are commonly misunderstood. - **Version Control & Amendments:** Establish version-control practices including dated version numbers, changelog documenting all modifications, advance-notice requirements for rule changes (minimum 7 days before they take effect), and grandfathering provisions for in-progress competitions when rules change. - **Accessibility & Distribution:** Ensure the rulebook is distributed through multiple channels (tournament website, Discord pinned message, registration-page link, pre-event email), available in relevant languages, and formatted for both screen reading (web/PDF) and quick reference (condensed cheat-sheet version). - **Hierarchy of Authority:** Establish a clear hierarchy of rule authority: (1) game publisher's official competitive rules take precedence, (2) tournament-specific rulebook, (3) administrator rulings for situations not covered by written rules, (4) precedent from previous rulings in the same event series. ### 2. Eligibility & Registration Rules - **Age Requirements:** Specify minimum age requirements that comply with game ESRB/PEGI ratings, platform terms of service, and local regulations, with parental-consent requirements and documentation for minor participants. - **Account & Identity Verification:** Define account-eligibility requirements including minimum account age, rank requirements (if applicable), one-account-per-person rules, and the identity-verification process (government ID for LAN events, account ownership verification for online). - **Roster Rules for Team Events:** Specify team-roster rules including minimum and maximum roster sizes, substitute-player allowances and activation procedures, roster-lock deadlines (typically 24-48 hours before the event), and the conditions under which mid-tournament roster changes are permitted. - **Regional & Eligibility Restrictions:** Define any regional-eligibility restrictions (residence requirements, regional-qualifier participation), multi-team participation prohibitions (no player may be registered on more than one team), and conflict-of-interest rules (no tournament-staff members may compete). - **Registration Obligations:** Specify registration requirements including accurate information submission, agreement to rules and code of conduct, timely payment of entry fees (if applicable), and the consequences of providing false registration information. - **Withdrawal & Replacement Policies:** Define withdrawal procedures (advance-notice requirements, refund eligibility for entry-fee events), replacement policies (waitlist backfill timing, late-registration accommodation), and no-show consequences that are clear and consistently enforced. ### 3. Match Procedures & Game Rules - **Pre-Match Protocol:** Define the complete pre-match procedure: check-in confirmation, lobby creation (who creates, settings verification), character/map selection process (draft, ban, pick order), side selection (coin flip, higher seed chooses, alternating), and ready confirmation before match start. - **Map/Character Selection Rules:** Specify the selection process in detail: veto order for maps (e.g., Team A bans, Team B bans, Team A picks, Team B picks, remaining map is decider), draft order for characters if applicable, time limits for selections, and default selections if time expires. - **Pause & Timeout Rules:** Define pause rules including maximum pause count per team per match, maximum cumulative pause duration, acceptable pause reasons (technical issue, tactical timeout if allowed), opponent notification requirements, and automatic-loss triggers for excessive pausing. - **In-Game Communication Rules:** Specify permitted and prohibited communication during matches including coaching restrictions (no coaching during matches for some formats, limited coaching during tactical timeouts for others), use of in-game voice vs. external voice communication, and all-chat etiquette. - **Match Completion & Result Reporting:** Define when a match is officially complete (final score screen, game-client end state), the result-reporting procedure (screenshot submission, platform confirmation, referee verification), result-dispute window (typically 10-15 minutes after match end), and the consequences of failing to report results. - **Overtime & Draw Resolution:** Specify overtime and draw-resolution procedures for games that can end in ties, including overtime format, side-selection for overtime, and tiebreaker game procedures if multiple overtimes do not produce a winner. ### 4. Technical Issue & Disconnection Rules - **Disconnection Classification:** Classify disconnections by type: player-side disconnection (player's internet/hardware failure), server-side disconnection (game server crash affecting all players), and indeterminate disconnections, with different procedures for each type. - **Reconnection Windows:** Define reconnection time limits (typically 5-10 minutes for competitive matches) with the match paused during reconnection attempts, and specify what happens when reconnection fails (forfeit of current game, match restart, or match loss depending on game state). - **Match-State Restoration:** Define whether and how matches can be restored after disconnection: full restart from the beginning, restart from a saved state (if the game supports checkpoints), or continuation from the approximate game state, with specific rules for each scenario. - **Repeated Technical Issues:** Address repeated disconnections from the same participant, setting limits (typically 2-3 disconnections per match before automatic forfeit) and requiring participants to resolve technical issues before continuing, with the burden of proof on the disconnecting player. - **Hardware & Software Requirements:** Specify minimum hardware and software requirements for participation including required game version, anti-cheat software, stable internet connection (minimum speed and latency requirements for online events), and working audio/video equipment for monitored matches. - **Technical-Issue Documentation:** Require documentation for all technical-issue claims including screenshots, network logs, error messages, or video evidence, and specify the standard of evidence needed for different rulings (game restart vs. match restart vs. no action). ### 5. Code of Conduct & Anti-Cheat - **Prohibited Behavior Catalog:** Enumerate prohibited behaviors with clear definitions: cheating (any unauthorized modification of game client, exploitation of known bugs, use of third-party software), harassment (verbal abuse, threats, discriminatory language), unsportsmanlike conduct (intentional disconnection, griefing, rage-quitting), and competitive manipulation (match-fixing, collusion, account sharing). - **Exploit vs. Feature Distinction:** Define the boundary between intended game mechanics and exploitable bugs, establishing a process for declaring specific exploits as prohibited (published banned-exploit list) and a default rule for novel exploits discovered during competition (referee ruling based on whether the exploit is clearly unintended and significantly impacts competitive balance). - **Stream-Sniping Prevention:** Define stream-sniping rules for matches that are broadcast, including mandatory broadcast delay requirements (90 seconds minimum for most games), penalties for proven stream-sniping, and the standard of evidence required for stream-sniping accusations. - **Substance & Impairment Rules:** For LAN events, address substance policies including prohibited performance-enhancing substances (Adderall without prescription, stimulants), alcohol and drug policies during competition, and the practical enforcement approach for different event contexts. - **Social Media Conduct:** Specify social-media conduct rules during competition periods including prohibitions on publishing match-specific strategic information, harassment of opponents or officials, and the disclosure of confidential competitive information (unreleased rulings, private communications). - **Anti-Cheat Enforcement Chain:** Define the anti-cheat enforcement process: automated detection (client-side anti-cheat flag), preliminary investigation (replay review, statistical analysis), accusation notification (written notice to accused with specific allegations and evidence), response period (24-48 hours for accused to respond), ruling (panel decision with written rationale), and appeal (independent review panel). ### 6. Penalties, Appeals & Governance - **Penalty Severity Scale:** Define a graduated penalty scale with specific triggers: Level 1 Warning (first minor offense, verbal or written), Level 2 Match Penalty (repeated minor offense or single moderate offense, game or map forfeiture), Level 3 Disqualification (serious offense, removal from current event with prize forfeiture), Level 4 Suspension (severe offense, multi-event ban of defined duration), Level 5 Permanent Ban (egregious offense, lifetime ban from all organization events). - **Mitigating & Aggravating Factors:** Specify factors that affect penalty severity including prior disciplinary history (aggravating), voluntary admission (mitigating), impact on competitive outcomes (aggravating if significant), and good-faith mistake vs. intentional violation (mitigating vs. aggravating). - **Appeal Process Design:** Establish a formal appeal process: written appeal submission within 48 hours of penalty notification, identification of specific grounds for appeal (procedural error, new evidence, disproportionate penalty), independent appeal review by a person or panel not involved in the original ruling, and final binding decision within 5 business days. - **Officials Hierarchy:** Define the officials hierarchy: match referees (immediate match rulings), head referee (escalated match disputes and between-match issues), tournament director (format decisions, penalty enforcement, operational decisions), and competitive-integrity committee (serious competitive-integrity violations requiring investigation). - **Ruling Consistency & Precedent:** Establish a ruling-precedent system where significant competitive rulings are documented and referenced for future decisions, ensuring consistent treatment of similar situations while allowing evolution of standards when justified by changed circumstances. - **Emergency Authority:** Define emergency authority provisions that allow the tournament director to make rulings on situations not covered by written rules, using the principle of competitive fairness as the guiding standard, with documentation requirements and post-event review of all emergency rulings. Ask the user for: the specific game and competitive context, tournament size and competitive level (community, semi-professional, professional), online versus LAN format, existing rules or precedents from previous events, specific competitive-integrity concerns from the game community, and the governance structure and staffing available for rule enforcement.
Or press ⌘C to copy