Rule Zero is the Commander community's term for the pre-game conversation where players align on expectations before anyone draws a card. Done well, it takes 90 seconds and prevents the most common causes of bad game experiences: power level mismatches, surprise combos, frustrating stax effects, and post-game salt. Done poorly — or skipped entirely — it leaves the pod to discover those mismatches mid-game when there's nothing to do about them.
The reason Rule Zero conversations often fail is not that players don't want alignment. It's that the language used is too vague to produce it. "I'm playing a 7" means nothing when one player's 7 wins on turn 4 with a two-card combo and another player's 7 means a fully-powered battlecruiser that wins by turn 12. This guide provides scripts that are specific enough to actually work.
The Core Script
Before shuffling, each player should cover three things in under 30 seconds:
"This deck is Bracket X." Use the WotC bracket number (1-5), not a 1-10 self-assessed power number. Bracket numbers are anchored to specific card categories (Game Changers, fast mana, tutors, extra turns) and are verifiable. You can run your list through EDHcheck and share the result directly. "My EDHcheck says Bracket 3, speed score 5" is a dramatically clearer declaration than "I'd call it a 7."
"Primary win is Y by turns A-B." Name your actual win condition and your expected win window. "Primary win is Purphoros triggered by token generation, usually turn 8-11." "Primary win is Thassa's Oracle plus Demonic Consultation, usually turn 4-7 with setup." This lets opponents threat-assess you accurately and allows them to decide whether they want to play this pod.
"I run Z tutors and N fast mana pieces." These two numbers tell opponents more about your deck's explosive potential than almost anything else. A Bracket 3 deck with four tutors and Mana Crypt is a different animal from a Bracket 3 deck with no tutors and Sol Ring as its only fast mana.
That's it. Three sentences. 30 seconds per player, two minutes for the whole pod. The game is more fun.
Why Vague Language Fails
The 1-10 power scale has been the dominant Commander language for years, and it consistently produces bad outcomes because it has no external reference point. One player's 6 is another player's 9. The same deck can be a 5 in one local meta and an 8 at a different store because the scale is relative to unstated reference groups.
Bracket language solves this by anchoring to specific card categories. Bracket 3 means "Game Changers present and acknowledged, some tutors, some fast mana." This is the same definition everywhere. A player who declares Bracket 3 and then wins on turn 3 with a fast combo has either misdeclared their bracket or made a mistake in their self-assessment — and you can verify which by checking their decklist against the bracket criteria.
The other failure mode is vague win condition language: "I have some synergies" or "it can get out of hand sometimes." These descriptions tell opponents nothing useful for threat assessment. Threat assessment is how the other three players decide who to interact with and when. If they can't assess your threat accurately, they will either over-target you (because your deck looks suspicious) or under-target you (because you seem non-threatening) until the game reveals which it is. Both outcomes are worse than declaring clearly.
Scripts for Awkward Situations
When someone doesn't know their bracket: "Have you run your deck through EDHcheck? It takes two minutes and gives you an objective bracket you can share. If not, what's your commander and what does your deck do to win?" This redirects to commander-level information that gives enough signal even without a bracket number.
When brackets don't match: "We have a Bracket 2 deck and two Bracket 4 decks here — should we have the Bracket 4 players dial back or should the Bracket 2 player grab a different deck?" This surfaces the mismatch clearly without blaming anyone and gives the pod a decision to make together.
When someone declares and then plays above their stated bracket: Post-game, not mid-game. "That felt faster than Bracket 3 — did the deck outperform your usual?" This opens a recalibration conversation without accusing anyone of lying. Sometimes decks genuinely overperform their expected bracket.
When you're playing a high-salt deck: Declare the salt-generating categories specifically. "This deck runs Armageddon and two extra-turn spells. It's Bracket 4. The land destruction is a core part of the game plan, not a gotcha." Players who are told upfront are far less frustrated than players who are surprised.
Making Rule Zero Faster With EDHcheck
The practical bottleneck to Rule Zero in casual settings is that players don't know their bracket because they haven't analyzed their deck formally. Solving this takes two minutes:
- Paste your decklist (or a Moxfield/Archidekt URL) into EDHcheck
- Note the bracket assignment, speed score, and any Game Changers flagged
- Save the snapshot or screenshot to your phone
At your next game, pull up that screenshot when the pod is forming. "EDHcheck says Bracket 3, speed 5, no extra turns, two Game Changers" is an objective, verifiable declaration that takes three seconds to share and generates almost no dispute.
If you're not sure what your bracket means in terms of gameplay expectations, read Understanding the WotC Bracket System and how to read your EDHcheck power score correctly. These two guides cover the exact language that makes Rule Zero conversations land cleanly.
For event contexts where Rule Zero is part of a larger preparation checklist, see CommandFest 2025 lessons for 2026 and the CommandFest prep checklist.
Why This Works Long-Term
The mechanical reason specific Rule Zero language works is that it gives players a shared reference point for post-game analysis. Instead of "that felt too strong," the conversation becomes "we queued a Bracket 3 and a Bracket 4 together — the Bracket 4 won, which is expected." This produces a feedback loop where players actively recalibrate their bracket declarations based on outcomes, which improves accuracy over time.
Specific inputs reduce emotional reactions. When the post-game analysis can be grounded in bracket expectations rather than feelings about the game, repeat pods become steadily better over time. Players get more accurate about their own decks, clearer about their table preferences, and better at self-sorting into pods that match their experience goals.
Clear language is not just courtesy — it is the mechanism by which Commander gets more fun the more you play it.