Magic Combat & the Stack Explained: Responses, Blockers, Priority and Timing
← All Magic: The Gathering guides
Most confusing Magic exchanges become easier when you separate three things: paying a cost, putting a spell or ability on the stack, and resolving it. Combat adds a sequence of steps, each with its own decisions. You cannot interrupt every action at every moment, but you often have more than one useful opportunity to act.
Use the examples below with simple practice cards first. A card’s own wording and current rules can change the result. This guide explains the normal sequence, not every possible exception.
The stack resolves from the top
When you cast a spell, it normally goes on the stack. Most activated and triggered abilities use it too. If another spell or ability is added in response, that new object sits above the earlier one. When everyone passes in succession, only the top object resolves. Players then get another opportunity to act before the next object resolves.
The stack is not a pile that must all resolve at once. Nor is it a contest in which the last player to speak always wins: costs, targets, timing restrictions, and what each effect actually does still matter.
Priority is the opportunity to act
Having priority lets you cast an appropriate spell or activate an ability. The active player normally receives priority after a spell or ability resolves. Players pass priority in turn order. With an empty stack, everyone passing normally advances the step or phase; with something on the stack, everyone passing causes the top object to resolve.
You do not normally receive priority during untap, and you do not cast an instant midway through a spell resolving. If a spell tells someone to draw three cards, you cannot wait for the second draw and insert another spell before the third just because it is an instant.
In practice, communicate plainly: “I cast this, targeting your creature,” “Before that resolves,” or “I want to act before attackers.” Agreeing on a shortcut is useful; rushing through it after someone has asked to respond is not.
Costs happen before responses
Casting includes choosing applicable modes and targets, determining costs, and paying those costs. Other players do not interrupt that process halfway through. If sacrificing a creature is a cost to activate an ability, the sacrifice has already happened when opponents can respond to that ability.
Removing the source of an ability generally does not remove the ability from the stack. If an activated ability is already there, destroying its creature does not automatically counter it. Read whether the ability needs information from its source or has another relevant condition.
Mana abilities usually resolve without using the stack. Tapping a basic land for mana is therefore different from casting an instant. Playing a land is also a special action rather than a spell; the land play itself is not something to counter.
What happens if a target disappears?
Targets are chosen when a targeted spell or ability is put on the stack, and they are checked again as it tries to resolve. If every target is illegal, it does not resolve. If at least one target remains legal, it can resolve and affect legal targets as its instructions allow.
This is why a removal spell aimed at a creature normally cannot switch to another creature after its original target is sacrificed. Changing a target requires permission from an effect; it is not a free adjustment. Also distinguish a targeted spell from an effect that never uses the word “target” in its relevant rules text.
Know the combat checkpoints
- Beginning of combat: A chance to act before attackers are declared.
- Declare attackers: The active player declares attackers as a turn-based action. Players can then act.
- Declare blockers: Defenders declare blockers. Players can then act with those blocks known.
- Combat damage: Creatures assign and deal combat damage according to the rules. Players do not respond between normal damage assignment and that damage being dealt.
- End of combat: A final combat step before the next main phase.
Tapping an attacker before it is declared can stop it attacking, provided no rule changes that. Tapping it after it has been declared attacking does not remove it from combat. Similarly, tapping a creature already declared as a blocker does not normally stop it blocking or dealing damage.
A blocked creature usually stays blocked
Suppose a 4/4 attacker is blocked by a 1/1. The attacker’s controller removes the blocker before combat damage. The 4/4 is still blocked. Without trample or another relevant ability, it does not suddenly deal its damage to the defending player.
Trample changes damage assignment, so removing blockers can matter differently. Flying and reach affect which blocks are legal. Deathtouch changes what counts as lethal damage in relevant damage-assignment situations. Read these abilities before deciding when to spend a removal spell or combat trick.
Older videos may describe a required damage-assignment order for multiple blockers. Current rules no longer use that old ordering requirement. Do not apply a remembered tutorial automatically to modern play; use the current Comprehensive Rules when a multi-block depends on precise assignment.
First strike creates a separate damage step
When first strike or double strike is involved, combat can have an initial damage step and a normal one. A creature with first strike can kill an opposing creature before that creature gets to deal normal combat damage. Players can act between those steps after the first damage has happened and the game has checked its consequences.
That response window does not exist between two creatures dealing ordinary combat damage simultaneously. A 2/2 and 3/2 that damage each other normally both die; the 3/2 does not survive just because its power is larger.
Triggers, counters, and damage are not interchangeable
A triggered ability starts with wording such as “when,” “whenever,” or “at.” Remembering the trigger is different from activating an optional ability. A +1/+1 counter physically changes a creature’s stats while it remains; damage marked on a creature does not reduce its printed toughness.
A 4/4 with 3 damage marked is still a 4/4, not a 4/1. It is closer to lethal damage for that turn. If something gives it -1/-1, it becomes 3/3 with 3 damage marked and is normally destroyed as a state-based action. These distinctions matter for effects that look at power or toughness.
A repeatable method for resolving a confusing exchange
- Pause and name the current step or phase.
- List spells and abilities on the stack from bottom to top.
- Confirm targets, modes, and costs already paid.
- Resolve the top object, then check the game state and relevant triggers.
- Offer the next priority opportunity instead of sweeping the whole stack away.
At a store event, call a judge rather than rebuilding a disputed sequence from memory after several more actions. At home, look up the relevant card and rule together. Being able to describe what happened is usually the fastest route to understanding why.
Official sources & further reading
Rules and product details checked against Wizards of the Coast resources. Examples and learning recommendations are B3’s own.
- Current Comprehensive Rules
- Official combat and spell-casting lessons
- The Stack and Its Tricks: worked examples
- Oracle card text and rulings