The stack is the part of Magic where new players quietly stop following. Three triggered abilities resolve in the wrong order, someone says “in response,” and the table loses the thread. The good news is that the stack is not actually complicated — it is a last-in, first-out pile of objects with a clean priority loop. The bad news is that triggered abilities, replacement effects, and layered continuous effects all wear similar costumes, and players conflate them. This is a working guide to tracking the stack at a real table, written for Commander pods that want fewer arguments and cleaner play.
The mental model: a literal stack of plates
Spells and abilities go onto the stack one at a time. The most recently added one resolves first — last in, first out. Nothing on the stack does anything until it resolves. Between every spell or ability, every player gets a chance to respond. That is it. The hard part is not the rule; the hard part is keeping a clear picture of which plate is on top, which players have passed priority, and what the order of events will be when the dust settles.
Priority in one paragraph
After any player puts a spell or ability on the stack, that same player keeps priority — they can do something else before passing. When they pass, priority goes to the next player. Once every player passes in a row without adding anything, the top object on the stack resolves. Then the active player gets priority again. Most arguments at casual tables come from skipping that “every player passes” step.
If you are not sure whether someone has priority, the answer is almost always: the person who just did the thing.
Triggered abilities: not on the stack until they're put there
A common mistake: a triggered ability fires the moment its condition is met. It does not. It triggers — meaning it is queued — and then the next time a player would receive priority, the ability is put on the stack. This matters because multiple triggers can accumulate before anything is put on the stack, and they go on in a specific order. The active player puts theirs on first, in any order they choose; then each opponent in turn order does the same.
Worked example: three triggers, one upkeep
- You control three permanents that each trigger at the beginning of your upkeep.
- All three trigger simultaneously when your upkeep begins.
- Before any player gets priority, you choose the order. The one you put on the stack last will resolve first.
- Once they're on the stack, you receive priority and can respond before any of them resolve.
Players who treat triggers as “they go on in the order they printed on the cards” will miss this. The active player has full control of their own trigger order. That control is occasionally a decisive line of play.
Replacement effects don't use the stack
This is the rule that catches people. A replacement effect — anything with the word “instead” or “as ... enters” — does not go on the stack and cannot be responded to. Doubling Season is the canonical example. When you would create a token, Doubling Season modifies the event before it happens; there is no trigger to counter. If you wait for the token to appear and then try to respond, you have already missed the window because nothing was ever on the stack.
How to spot one
- “If ... would ..., instead ...” — replacement effect.
- “As [permanent] enters the battlefield ...” — replacement effect.
- “When ... happens, ...” — triggered ability, uses the stack.
- “Whenever ...” — triggered ability, uses the stack.
Layered continuous effects: the part nobody loves
When the board has multiple effects modifying the same permanent, you cannot just resolve them in the order they came down. Magic uses a seven-layer system to determine the final state of a permanent, and the layers always run in the same order regardless of when the effects were created. Once you accept the layers, most weird Anointed Procession plus Opalescence plus Humility scenarios stop being weird.
- Layer 1 — copy effects (this card becomes a copy of that one).
- Layer 2 — control-changing effects.
- Layer 3 — text-changing effects.
- Layer 4 — type-changing effects.
- Layer 5 — color-changing effects.
- Layer 6 — ability-adding and ability-removing effects.
- Layer 7 — power and toughness, with sub-layers a–d.
Layer 7 has its own sub-order: characteristic-defining abilities, printed-value setters (“is 3/3”), modifications by static effects, and counters last. Power and toughness arguments at the table almost always live inside layer 7's sub-layers.
Tracking it without losing the room
At the casual table, the trick is not memorizing every rule. It's slowing down at three specific moments: when something triggers, when someone says “in response,” and when a permanent's characteristics change mid-combat. At those moments, name what's happening out loud, in order. “That triggers. Before it goes on the stack, anything? Okay, on the stack. I have priority. Pass. Pass. Pass. Resolves.” Boring is the goal.
A short script that fixes most arguments
- “Holding priority” — “I cast this and before passing I'm going to cast that.”
- “In response” — “I'd like to respond before yours resolves.”
- “Floating mana” — “Before priority passes, I'm tapping for mana to use later this step.”
- “Letting it resolve” — “No response, it resolves.”
When to actually open a tool
Most stack interactions resolve fine with a verbal protocol. When a new player at the table needs to see how priority and LIFO actually play out, TheStack.gg's stack page walks through a Counterspell-on-Counterspell-on-Lightning-Bolt sequence step by step — you can play, pause, and reset the animation. It's an explainer, not an interactive board, but it makes the rule click faster than any paragraph of rules text. For the keywords behind any spell or ability, the glossary is a tap away.
For an actual messy in-game stack — three triggers, a Strionic Resonator copy, two counterspells in the air — the right tool is still pen and paper. Name what's happening out loud, write the order down if you have to, and let nobody pass priority until everyone agrees on what's on the stack.