Namespaces

Variants

Share

Share
Actions

State-based actions

From MTG Salvation Wiki
(Redirected from State-Based Action)
Jump to: navigation, search
Comprehensive Rules
Game Concepts
Parts of a Card
Card Types
Zones
Turn Structure
Spells, Abilities, and Effects
Additional Rules
700. General
701. Keyword Actions
702. Keyword Abilities
703. Turn-Based Actions
704. State-Based Actions
705. Flipping a Coin
706. Copying Objects
707. Face-Down Spells and Permanents
708. Split Cards
709. Flip Cards
710. Leveler Cards
711. Double-Faced Cards
712. Controlling Another Player
713. Ending the Turn
714. Restarting the Game
715. Subgames
716. Taking Shortcuts
717. Handling Illegal Actions
Multiplayer Rules
Casual Variants

State-based actions are game actions that happen when any of a set of improper conditions arise in the game. Whenever a player would gain priority, state-based actions first check for certain game conditions. If any of those conditions are met, the necessary actions are carried out simultaneously as a single event. Then, any triggered abilities go on the stack and the check is repeated. Once no conditions for state-based actions exist, the appropriate player gains priority.

State-based actions should not be confused with triggered abilities, which use the stack. A creature being destroyed by lethal damage, the "legend rule" and "World rule" are all state-based actions.

From the Comprehensive Rules 704. State-Based Actions

  • 704.1. State-based actions are game actions that happen automatically whenever certain conditions (listed below) are met. State-based actions don't use the stack.
  • 704.2. State-based actions are checked throughout the game and are not controlled by any player.
  • 704.3. Whenever a player would get priority (see rule 116, "Timing and Priority"), the game checks for any of the listed conditions for state-based actions, then performs all applicable state-based actions simultaneously as a single event. If any state-based actions are performed as a result of a check, the check is repeated; otherwise all triggered abilities that are waiting to be put on the stack are put on the stack, then the check is repeated. Once no more state-based actions have been performed as the result of a check and no triggered abilities are waiting to be put on the stack, the appropriate player gets priority. This process also occurs during the cleanup step (see rule 514), except that if no state-based actions are performed as the result of the step's first check and no triggered abilities are waiting to be put on the stack, then no player gets priority and the step ends.
  • 704.4. Unlike triggered abilities, state-based actions pay no attention to what happens during the resolution of a spell or ability.
    • Example: A player controls a creature with the ability "This creature’s power and toughness are each equal to the number of cards in your hand” and casts a spell whose effect is "Discard your hand, then draw seven cards." The creature will temporarily have toughness 0 in the middle of the spell’s resolution but will be back up to toughness 7 when the spell finishes resolving. Thus the creature will survive when state-based actions are checked. In contrast, an ability that triggers when the player has no cards in hand goes on the stack after the spell resolves, because its trigger event happened during resolution.
  • 704.5. The state-based actions are as follows:
    • 704.5a If a player has 0 or less life, he or she loses the game.
    • 704.5b If a player attempted to draw a card from a library with no cards in it since the last time state-based actions were checked, he or she loses the game.
    • 704.5c If a player has ten or more poison counters, he or she loses the game. Ignore this rule in Two-Headed Giant games; see rule 704.5u instead.
    • 704.5d If a token is phased out, or is in a zone other than the battlefield, it ceases to exist.
    • 704.5e If a copy of a spell is in a zone other than the stack, it ceases to exist. If a copy of a card is in any zone other than the stack or the battlefield, it ceases to exist.
    • 704.5f If a creature has toughness 0 or less, it's put into its owner's graveyard. Regeneration can't replace this event.
    • 704.5g If a creature has toughness greater than 0, and the total damage marked on it is greater than or equal to its toughness, that creature has been dealt lethal damage and is destroyed. Regeneration can replace this event.
    • 704.5h If a creature has toughness greater than 0, and it's been dealt damage by a source with deathtouch since the last time state-based actions were checked, that creature is destroyed. Regeneration can replace this event.
    • 704.5i If a planeswalker has loyalty 0, it's put into its owner's graveyard.
    • 704.5j If a player controls two or more planeswalkers that share a planeswalker type, that player chooses one of them, and the rest are put into their owners' graveyards. This is called the "planeswalker uniqueness rule."
    • 704.5k If a player controls two or more legendary permanents with the same name, that player chooses one of them, and the rest are put into their owners' graveyards. This is called the "legend rule".
    • 704.5m If two or more permanents have the supertype world, all except the one that has been a permanent with the world supertype on the battlefield for the shortest amount of time are put into their owners' graveyards. In the event of a tie for the shortest amount of time, all are put into their owners' graveyards. This is called the "world rule."
    • 704.5n If an Aura is attached to an illegal object or player, or is not attached to an object or player, that Aura is put into its owner's graveyard.
    • 704.5p If an Equipment or Fortification is attached to an illegal permanent, it becomes unattached from that permanent. It remains on the battlefield.
    • 704.5q If a creature is attached to an object or player, it becomes unattached and remains on the battlefield. Similarly, if a permanent that's neither an Aura, an Equipment, nor a Fortification is attached to an object or player, it becomes unattached and remains on the battlefield.
    • 704.5r If a permanent has both a +1/+1 counter and a -1/-1 counter on it, N +1/+1 and N -1/-1 counters are removed from it, where N is the smaller of the number of +1/+1 and -1/-1 counters on it.
    • 704.5s If a permanent with an ability that says it can't have more than N counters of a certain kind on it has more than N counters of that kind on it, all but N of those counters are removed from it.
    • 704.5t In a Two-Headed Giant game, if a team has 0 or less life, that team loses the game. See rule 810, "Two-Headed Giant Variant."
    • 704.5u In a Two-Headed Giant game, if a team has fifteen or more poison counters, that team loses the game. See rule 810, "Two-Headed Giant Variant."
    • 704.5v In a Commander game, a player that's been dealt 21 or more combat damage by the same commander over the course of the game loses the game. See rule 903, "Commander."
    • 704.5w In an Archenemy game, if a non-ongoing scheme card is face up in the command zone, and it isn't the source of a triggered ability that has triggered but not yet left the stack, that scheme card is turned face down and put on the bottom of its owner's scheme deck. See rule 904, "Archenemy."
  • 704.6. If multiple state-based actions would have the same result at the same time, a single replacement effect will replace all of them.
    • Example: You control Lich’s Mirror, which says "If you would lose the game, instead shuffle your hand, your graveyard, and all permanents you own into your library, then draw seven cards and your life total becomes 20." There’s one card in your library and your life total is 1. A spell causes you to draw two cards and lose 2 life. The next time state-based actions are checked, you’d lose the game due to rule 704.5a and rule 704.5b. Instead, Lich’s Mirror replaces that game loss and you keep playing.
  • 704.7. If a state-based action results in a permanent leaving the battlefield at the same time other state-based actions were performed, that permanent’s last known information is derived from the game state before any of those state-based actions were performed.
    • Example: You control Young Wolf, a 1/1 creature with undying, and it has a +1/+1 counter on it. A spell puts three -1/-1 counters on Young Wolf. Before state-based actions are performed, Young Wolf has one +1/+1 counter and three -1/-1 counters on it. After state-based actions are performed, Young Wolf is in the graveyard. When it was last on the battlefield, it had a +1/+1 counter on it, so undying will not trigger.