MTG Wiki
Advertisement

The Stack

The stack is the game zone where spells and abilities are put when they are played and where they wait to resolve.[1][2][3] The stack system allows players to "respond" to the actions of other players before those actions take full effect, enabling interactive gameplay even with "instantaneous" effects.

Description[]

Spells and abilities are put on top of the stack as the first step is being played, and are removed from it as the last step of resolving.

Any spell or ability that uses the stack can be 'responded to' by all players, meaning players have a chance to play spells and abilities with it still on the stack. Since the stack resolves in order from top to bottom, those spells and abilities will resolve before the spell they were played "in response" to. Spells and abilities on the stack resolve one at a time, with a chance for each player to play spells and abilities in between each resolution. Actions that do not use the stack, such as paying costs, playing mana abilities, or turning a face-down creature with morph face-up, cannot be responded to.

Rules[]

From the glossary of the Comprehensive Rules (November 19, 2021—Innistrad: Crimson Vow)

Stack
A zone. The stack is the zone in which spells, activated abilities, and triggered abilities wait to resolve. See rule 405, “Stack.”

From the Comprehensive Rules (November 19, 2021—Innistrad: Crimson Vow)

  • 405. Stack
    • 405.1. When a spell is cast, the physical card is put on the stack (see rule 601.2a). When an ability is activated or triggers, it goes on top of the stack without any card associated with it (see rules 602.2a and 603.3).
    • 405.2. The stack keeps track of the order that spells and/or abilities were added to it. Each time an object is put on the stack, it’s put on top of all objects already there.
    • 405.3. If an effect puts two or more objects on the stack at the same time, those controlled by the active player are put on lowest, followed by each other player’s objects in APNAP order (see rule 101.4). If a player controls more than one of these objects, that player chooses their relative order on the stack.
    • 405.4. Each spell has all the characteristics of the card associated with it. Each activated or triggered ability that’s on the stack has the text of the ability that created it and no other characteristics. The controller of a spell is the person who cast it. The controller of an activated ability is the player who activated it. The controller of a triggered ability is the player who controlled the ability’s source when it triggered, unless it’s a delayed triggered ability. To determine the controller of a delayed triggered ability, see rules 603.7d–f.
    • 405.5. When all players pass in succession, the top (last-added) spell or ability on the stack resolves. If the stack is empty when all players pass, the current step or phase ends and the next begins.
    • 405.6. Some things that happen during the game don’t use the stack.
      • 405.6a Effects don’t go on the stack; they’re the result of spells and abilities resolving. Effects may create delayed triggered abilities, however, and these may go on the stack when they trigger (see rule 603.7).
      • 405.6b Static abilities continuously generate effects and don’t go on the stack. (See rule 604, “Handling Static Abilities.”) This includes characteristic-defining abilities such as “[This object] is red” (see rule 604.3).
      • 405.6c Mana abilities resolve immediately. If a mana ability both produces mana and has another effect, the mana is produced and the other effect happens immediately. If a player had priority before a mana ability was activated, that player gets priority after it resolves. (See rule 605, “Mana Abilities.”)
      • 405.6d Special actions don’t use the stack; they happen immediately. See rule 116, “Special Actions.”
      • 405.6e Turn-based actions don’t use the stack; they happen automatically when certain steps or phases begin. They’re dealt with before a player would receive priority (see rule 117.3a). Turn-based actions also happen automatically when each step and phase ends; no player receives priority afterward. See rule 703.
      • 405.6f State-based actions don’t use the stack; they happen automatically when certain conditions are met. See rule 704. They are dealt with before a player would receive priority. See rule 117.5.
      • 405.6g A player may concede the game at any time. That player leaves the game immediately. See rule 104.3a.
      • 405.6h If a player leaves a multiplayer game, objects may leave the game, cease to exist, change control, or be exiled as a result. These actions happen immediately. See rule 800.4a.

Actions[]

Actions that use the stack[]

Spells, activated abilities, and triggered abilities become objects on the stack instead of resolving immediately. As described above, this means that responses may go above them on the stack, allowing those to resolve before the original spell or ability.

However, the single action of casting a spell or activating an ability does not use the stack, only the resolution of that spell or ability uses it. For example, if the player with priority declares they are casting Lightning Bolt, the opponent may respond by giving a creature protection from red before it deals damage, but it is too late to force the player to discard the Bolt before it's even cast.

Actions that don't use the stack[]

Actions that don't use the stack can't be responded to by performing other actions before the first action actually happens. However, some actions may be part of a larger process that does use the stack, such as resolving a spell (which could be responded to before the spell starts resolving), or may be part of a process which places an object on the stack, such as casting a spell (in which case the spell can be responded to, but the actions taken while casting it cannot be).

Turn-based actions happen automatically upon reaching specific parts of a turn, and don't use the stack. Some of these actions are technically done by the game itself rather than players, with the players simply manipulating their cards to reflect the new game state.

Special actions are certain intentional actions a player may take when they have priority. By far the most common of these is playing a land. There are also a number of card abilities that enable special actions as well, like morph and foretell, as well as non-keyword abilities on several cards. Conspiracy Draft and Planechase games allow two more special actions.

Activating a mana ability is not considered a special action, but it follows similar rules if activated on its own (rather than while paying a cost).

Paying a cost can never be responded to, even if the actions taken as part of that cost are, in other cases, part of effects that do use the stack. For example an activated ability that includes the very common cost of tapping a permanent can be activated and tapped immediately, and an opponent would not be able to respond with an instant that destroys the permanent first - although they could respond to the ability on the stack later. Mana abilities can also be activated during cost payment (and many other times) without the possibility of response.

Actions taking during the resolution of a spell also don't use the stack, preventing responses in between two sequential spell abilities. However a spell can generally be responded to before any of its abilities start resolving.

Replacement effects are applied without using the stack. However, the continuous effects that create them are usually known ahead of time, and most effects that are replaced do use the stack, so those effects can be responded to before replacement effects start to apply. This includes actions that happen "as" other actions take place, for instance daybound and nightbound cards transforming as day and night transitions occur.

Damage and the stack[]

Damage itself does not use the stack. However, many effects that would cause damage do use the stack, and can be responded to. Combat damage can't be responded to using the stack, but effects can affect damage pre-emptively simply by playing them before the combat damage step begins (during the declare blockers step). Many effects that interact with damage do so as replacement effects: before the damage occurs, stack actions resolve to set up a replacement effect, then when the damage would occur, it is automatically modified by the replacement effect without using the stack.

Between Sixth Edition until Magic 2010, damage events, notably combat damage, existed on the stack before damage was actually dealt. This gave an opportunity for players to respond to prevent damage, but also allowed unintuitive interactions, like removing a creature that had unresolved damage on the stack, which allowed the creature to deal damage despite being absent from play. When this was removed, damage interactions changed to replacement effects, and the institution of damage assignment order made combat predictable enough to use the stack to set up the response to damage before the combat damage step itself.

Trivia[]

  • In flavor terms, the stack is the point when a spell is materializing, the stage between your mind and external reality.[4]
  • The stack was featured as rules card 7 of 9 in the Magic 2011 set.
  • The term stack is used computer science describing the same behavior as in Magic: LIFO (last in, first out).

References[]

  1. Ted Knutson (November 4, 2006). "The Dynamics of a Turn". magicthegathering.com. Wizards of the Coast.
  2. Mark Rosewater (November 20, 2006). "On The Stack". magicthegathering.com. Wizards of the Coast.
  3. Gavin Verhey (November 30, 2017). "The Stack and Its Tricks". magicthegathering.com. Wizards of the Coast.
  4. Doug Beyer (December 10, 2008). "The Flavor of Zones". magicthegathering.com. Wizards of the Coast.

External links[]

Advertisement