Magic: The Gathering Rules Engine

When to Read the Rules File

Read specific sections of references/comprehensive-rules.txt when:

• The user asks a specific rules question (search by rule number or keyword)
• A card interaction needs adjudication (find the relevant mechanic rules)
• Commander-specific rules are needed (section 903, lines ~6833-6937)
• You need to verify a keyword ability (section 702)
• Stack/priority questions arise (sections 117, 405, 601-608)
• Layer system questions come up (section 613)
• State-based actions need checking (section 704)

For quick lookups, search by rule number (e.g., "903.4" for color identity, "702.124" for partner). For mechanic questions, search by keyword (e.g., "trample", "hexproof", "ward").

Rules Resolution Methodology

When answering a rules question, follow this process:

1. Identify the mechanic(s) involved - What abilities, keywords, or game actions are relevant?
2. Find the governing rules - Look up the specific rule numbers in the comprehensive rules
3. Check for interactions - Do replacement effects, triggered abilities, or layers apply?
4. Apply in correct order - Timestamps, layers (613), dependency, APNAP order (101.4)
5. State the conclusion - Give a clear answer, then cite the rule number(s)

Key Rules Patterns to Remember

Priority and the Stack (117, 405)

• Active player gets priority first after each spell/ability resolves
• Players must pass priority in succession for the top stack item to resolve
• Mana abilities don't use the stack (605)

State-Based Actions (704)

• Checked whenever a player would get priority
• All applicable SBAs happen simultaneously
• Key SBAs: creature with 0 or less toughness dies, player at 0 life loses, legend rule, 21 commander damage

Replacement Effects (614)

• "Instead" is the hallmark
• Affected player/controller of affected object chooses order if multiple apply
• A replacement effect can apply to an event only once (614.5)

Layers (613)

• The 7-layer system resolves continuous effects in order
• Layer 1: Copy, Layer 2: Control, Layer 3: Text, Layer 4: Type, Layer 5: Color, Layer 6: Abilities, Layer 7: P/T (with sublayers 7a-7e)
• Within a layer: dependency first, then timestamp order

Commander-Specific (903)

• Color identity includes all mana symbols in cost AND rules text (903.4)
• Commander tax: +{2} for each previous cast from command zone (903.8)
• Commander returns to command zone from graveyard/exile as SBA, or as replacement from hand/library (903.9)
• 21 combat damage from same commander = loss (903.10a)
• Exactly 100 cards including commander (903.5a)
• Singleton except basic lands (903.5b)

Response Format

When answering rules questions:

1. Lead with the answer - Don't make the user wade through rules text to find the conclusion
2. Cite rule numbers - e.g., "Per rule 903.8, the commander tax increases by {2} each time"
3. Explain the reasoning - Walk through the logic so the user understands the why
4. Note common misconceptions if relevant - Many rules are commonly misunderstood
5. Use card examples when helpful - Concrete examples clarify abstract rules

Important Caveats

• The Comprehensive Rules are updated with each set release. The bundled version is effective February 27, 2026
• For card-specific rulings (errata, Gatherer rulings), use Scryfall's rulings endpoint: https://api.scryfall.com/cards/named?exact={card_name} to check the latest oracle text
• If a question involves a card you're unsure about, verify its current oracle text before answering
• Some rules interact in non-obvious ways. When in doubt, read the specific rules rather than relying on general knowledge