State-Based Actions in Commander: The Rules That Clean Up the Game Automatically

Fantasy illustration of a hooded blue-skinned mage and a goblin collector at a table covered with ornate card decks, miniature dragons, and glowing magical displays, with a red dragon and floating castle beyond arched windows.

Table of Contents

State-based actions are Magic’s automatic cleanup system. They make creatures with lethal damage die, remove extra legendary permanents, eliminate players who have lost, and handle several other conditions before anyone can cast another spell or activate an ability.

No player controls state-based actions, and they do not use the stack. The game checks them whenever a player would receive priority, performs every applicable action simultaneously, and checks again until there is nothing left to do. Only then are waiting triggered abilities put on the stack and priority given to a player. That sequence, defined in the Magic Comprehensive Rules, resolves many of Commander’s most confusing table moments.

When state-based actions happen

State-based actions are checked at priority points. In practical terms, that usually means after a spell or ability finishes resolving, after a player takes a game action that does not use the stack, and at the beginning of most steps and phases after turn-based actions have occurred.

They do not interrupt a resolving spell or ability. Suppose one part of an effect temporarily reduces a creature to 0 toughness, but a later part of that same effect increases its toughness again. If the creature has positive toughness when the effect finishes resolving, it survives the next check. Players do not pause halfway through the effect to send it to the graveyard.

The game also does not stop after one pass. If the first batch of state-based actions creates another applicable condition, the game performs another batch before anyone can respond. There is no tiny reaction window between checks.

The state-based actions you see most often

The complete rules contain a substantial list, but a smaller group accounts for most Commander games:

  • A player with 0 or less life loses the game.
  • A player who has attempted to draw from an empty library since the previous check loses the game.
  • A player with 10 or more poison counters loses the game, apart from the rules exception for Two-Headed Giant.
  • A creature with 0 or less toughness is put into its owner’s graveyard.
  • A creature with lethal marked damage is destroyed.
  • A creature dealt damage by a source with deathtouch since the previous check is destroyed.
  • A planeswalker with 0 loyalty is put into its owner’s graveyard.
  • Tokens outside the battlefield cease to exist.
  • Illegal or unattached Auras are put into their owners’ graveyards, while improperly attached Equipment and Fortifications become unattached.
  • Matching +1/+1 and -1/-1 counters on the same permanent are removed in pairs.

These actions may look similar at the table, but their wording matters. A creature with 0 toughness is put into the graveyard; it is not destroyed, so regeneration cannot save it. Lethal damage and deathtouch generally cause destruction, which means a valid regeneration effect can replace that event.

The legend rule is automatic, not a sacrifice

If one player controls two or more legendary permanents with the same name, that player chooses one to keep. The others are put into their owners’ graveyards as a state-based action. This is neither destruction nor sacrifice.

That distinction affects cards looking for a permanent being sacrificed or destroyed. A permanent sent away by the legend rule can still produce an applicable dies or leaves-the-battlefield trigger, but it does not satisfy wording that specifically requires a sacrifice. Our guide to the legend rule in Commander covers copies, tokens, and the choice of which permanent to keep.

Commander adds two especially important checks

Losing to commander damage

A player who has been dealt 21 or more combat damage by the same commander over the course of the game loses as a state-based action. The damage must be combat damage, and totals from different commanders are tracked separately rather than pooled. A player at 40 life can therefore lose to one commander while appearing perfectly healthy on the life counter.

Because this loss happens during the state-based-action check, nobody can respond after the total reaches 21 by gaining life or removing the commander. Preventing the combat damage or changing combat must happen before that point. For tracking details, see how commander damage works.

Moving a commander from the graveyard or exile

When a commander has entered a graveyard or exile since the previous state-based-action check, its owner may move it to the command zone. This choice is part of the state-based-action procedure. It is not a triggered ability and does not use the stack.

The commander reaches the graveyard or exile before its owner makes that choice. As a result, an applicable dies or leaves-the-battlefield ability can trigger. That trigger waits while state-based actions finish, and it is placed on the stack afterward. Moving the commander to the command zone does not erase the fact that it visited the earlier zone.

A commander going to its owner’s hand or library works differently. Its owner may move it to the command zone instead, using a replacement effect rather than a state-based action. The distinction matters because the commander does not enter the hand or library if the replacement is used.

State-based actions are not triggered abilities

The easiest way to separate the two concepts is to ask whether anything is waiting to go onto the stack. A triggered ability begins with language such as “when,” “whenever,” or “at.” It can trigger during resolution, but it normally waits for the next priority point before being placed on the stack. A state-based action simply happens during the rules check.

Tokens provide a clean example. A creature token destroyed by lethal damage enters the graveyard, so its dies ability can trigger. During the next state-based-action check, the token ceases to exist. After the checks are complete, the waiting dies trigger goes onto the stack. The token is gone, but the trigger remains. Our explanation of tokens entering the graveyard examines that sequence in more detail.

Why players cannot respond to the cleanup itself

Players need priority to cast instants, activate most abilities, or take other responsive actions. State-based actions finish before priority is granted. You cannot respond to a creature being put into the graveyard for having 0 toughness, respond to the legend-rule choice, or squeeze an effect between repeated state-based-action checks.

You can respond to the spell or ability creating the dangerous condition while it is still on the stack. You can also act later if the permanent survives and priority is granted. The useful question is not “Can I respond to the state-based action?” but “What is the last priority point before this condition becomes true?”

Official rules and Commander table conventions

State-based actions come from the game rules; they are not optional shortcuts. A Commander table can use Rule Zero to agree on house rules or altered expectations, but that requires group consensus rather than one player announcing a personal exception. The Commander Rules Committee FAQ describes Rule Zero as a shared pregame agreement.

That social flexibility should remain separate from technical rules questions. A group can agree to a variant, allow casual proxies, or adjust its deck expectations. Unless everyone has explicitly agreed to change a rule, ordinary state-based actions still occur exactly as the rules prescribe. Commander may be a social format, but “my creature looked too cool to die at 0 toughness” remains a difficult rules argument to sell.

A practical way to resolve crowded board states

When several things happen at once, pause and use a consistent order:

  1. Finish resolving the current spell or ability completely.
  2. Identify every state-based action that currently applies.
  3. Perform all applicable actions simultaneously.
  4. Check again because the first batch may have created new conditions.
  5. Repeat until no state-based actions apply.
  6. Put waiting triggered abilities on the stack in the proper order.
  7. Give the appropriate player priority.

This procedure keeps a busy Commander board understandable. It also prevents players from responding in windows that do not exist or missing triggers merely because their sources have already left the battlefield. State-based actions are less a stack of obscure exceptions than the game’s automatic maintenance pass: check the board, clean up everything that must happen, repeat if necessary, and only then let the players act.

References

  1. media.wizards.com
  2. Frequently asked Questions | Official Commander Website