310. Battles

Rules in this chapter

• 310.1 Battles A player who has priority may cast a battle card from their hand during a main phase of their turn when the stack is empty. Casting a battle as a spell uses the stack. (See rule…
• 310.2 Battles When a battle spell resolves, its controller puts it onto the battlefield under their control.
• 310.3 Battles Battle subtypes are always a single word and are listed after a long dash: “Battle — Siege.” Battle subtypes are also called battle types. See rule 205.3q for the complete list of…
• 310.4 Battles Defense is a characteristic that battles have.
• 310.5 Battles Battles can be attacked. (See rule 508, “Declare Attackers Step.”)
• 310.6 Battles Damage dealt to a battle results in that many defense counters being removed from it.
• 310.7 Battles If a Siege battle’s defense is 0 and it isn’t the source of an ability which has triggered but not yet left the stack, it’s put into its owner’s graveyard. (This is a state-based…
• 310.8 Battles If a non-Siege battle’s defense is 0, it’s put into its owner’s graveyard. (This is a state-based action. See rule 704.)
• 310.9 Battles Each battle has a player designated as its protector.
• 310.10 Battles A battle can’t be attached to players or permanents, even if it is also an Aura, Equipment, or Fortification. If a battle is somehow attached to a permanent, it becomes…
• 310.11 Battles If a battle that isn’t being attacked has no player designated as its protector, or its protector is a player who can’t be its protector, its controller chooses an appropriate…
• 310.12 Battles Some battles have the subtype Siege. Sieges are subject to special rules.