For anyone asking “how multiple triggers go on the stack APNAP explained for players,” the short answer is this: the active player puts their triggers on the stack first, then each other player does the same in turn order. Each player chooses the order of the triggers they control. Because the stack resolves from the top down, the triggers placed by the last player in that sequence will normally resolve first.
That distinction is the whole system in miniature. APNAP determines placement order; the stack’s last-in, first-out structure determines resolution order. On your turn, opponents’ simultaneous triggers will generally sit above yours. On an opponent’s turn, your triggers may sit above theirs. Responses can still change everything after the triggers have been stacked.
What APNAP means in Magic
APNAP stands for active player, nonactive player. The active player is the player whose turn it is. Everyone else is a nonactive player.
When triggered abilities controlled by multiple players are waiting to be placed on the stack, the active player puts all of their applicable triggers on the stack in an order of their choice. The next player in turn order does the same, followed by the remaining players in turn order. This is the procedure established by the Comprehensive Rules.
In a two-player game, that produces two groups: active player’s triggers on the bottom and nonactive player’s triggers on top. In a four-player Commander game, there can be four separately ordered groups. “The nonactive player’s triggers resolve first” is therefore a useful two-player shortcut, but it is incomplete in multiplayer.
The official Magic rules page provides access to the Comprehensive Rules, while Wizards’ player-facing explanation of the stack is a useful refresher on last-in, first-out resolution and priority.
The table procedure for multiple triggers
Do not begin by asking which trigger resolves first. Begin by identifying whose turn it is and who controls each trigger. That prevents the most common APNAP mistake: trying to arrange every trigger according to the outcome players want.
- Identify the event that occurred, such as creatures dying, combat damage being dealt, or a phase beginning.
- Identify every ability that triggered from that event.
- Allow the game to check and perform applicable state-based actions.
- Determine who controlled each triggered ability when it triggered.
- Starting with the active player, have each player choose the relative order of the triggers they control.
- Place those groups on the stack in turn order: active player first, followed by each nonactive player.
- Read the completed stack from top to bottom to determine the expected resolution order.
- Give players the normal opportunities to respond. Do not resolve the entire stack as though nobody receives priority between objects.
Triggered abilities trigger when their triggering events happen, but they are not necessarily placed on the stack at that exact instant. Waiting triggers are put on the stack after applicable state-based actions are checked and before a player receives priority.
Targets and other required choices are handled as each triggered ability is put on the stack. APNAP lets you order abilities you control; it does not let you postpone their required choices until resolution or rearrange another player’s triggers.
You choose the order of triggers you control
Suppose two abilities you control trigger at the beginning of your end step. One says to draw a card, and the other says to discard a card. If you want to draw before discarding, put the discard trigger on the stack first and the draw trigger on top of it. The draw trigger resolves first because it was placed last.
If you instead place the draw trigger first and the discard trigger second, the discard trigger is on top and resolves first. This same-controller ordering principle is illustrated in Wizards’ mechanics guidance: when one player controls multiple triggers, that player orders them, and the one placed last resolves first.
This is a tactical choice, not merely paperwork. Before ordering your triggers, ask what resources, targets, or information each resolution could create for the next one. Put the effect you want to resolve earliest closest to the top.
Be careful with dependencies. If one trigger creates a creature token and another trigger needs a target, you cannot necessarily target the not-yet-created token just because you intend to resolve the token-making ability first. Required targets are chosen while the triggered ability is being put on the stack, when that future token does not yet exist.
A two-player simultaneous death-trigger example
It is Alex’s turn, so Alex is the active player. Alex and Bailey each control a creature with an ability that triggers when that creature dies. A spell destroys both creatures simultaneously.
After the event, applicable state-based actions are checked. Both death triggers are waiting to be put on the stack. Alex puts Alex’s trigger on the stack first because Alex is the active player. Bailey then puts Bailey’s trigger on top. If nobody responds, Bailey’s trigger resolves first, followed by Alex’s.
| Stack position | Controller | Expected order |
|---|---|---|
| Top | Bailey, the nonactive player | Resolves first |
| Bottom | Alex, the active player | Resolves second |
This is why an opponent’s death trigger often resolves before yours during your own turn. It is not because opponents always have priority over the active player. Their simultaneous trigger was placed later under APNAP and therefore started higher on the stack.
Reverse whose turn it is and the result reverses. If the same event occurs during Bailey’s turn, Bailey’s active-player trigger goes on first and Alex’s nonactive-player trigger goes on top.
How APNAP works in four-player Commander
Assume the turn order is A, B, C, D, and it is A’s turn. A board wipe causes each player to control at least one waiting death trigger.
A orders and places all of A’s triggers first. B places B’s triggers above A’s. C places C’s above B’s, and D places D’s last. D’s group is therefore on top. If nobody adds anything else to the stack, D’s triggers resolve first, followed by C’s, then B’s, and finally A’s. Within each group, that player’s chosen order still controls which of their abilities resolves first.
| Placement sequence | Player | Relative stack position |
|---|---|---|
| First | A, active player | Lowest group |
| Second | B | Above A |
| Third | C | Above B |
| Fourth | D | Highest group |
Turn order matters more than the vague label “nonactive player.” B does not get to order C’s or D’s triggers, and the nonactive players do not collectively decide their groups’ arrangement. Each player orders only their own abilities when their place in the sequence arrives.
Commander also makes communication important. Before anyone starts resolving effects, identify every controller and build the stack visibly from A through D. This is especially valuable when triggers involve life loss, card draw, token creation, reanimation, or targets that could disappear before a lower trigger resolves.
APNAP is not the same as priority
APNAP answers how waiting triggers are placed on the stack. Priority answers who may take an action after that process is complete. These are related systems, but they do different jobs.
Once state-based actions have been handled and waiting triggers have been stacked, the active player receives priority. Players can then cast instants or activate abilities under the normal priority procedure. Passing priority does not let a player reorder triggers already on the stack.
After the top spell or ability resolves, it does not mean the next object automatically resolves without interruption. The game checks state-based actions, places any newly waiting triggers on the stack as appropriate, and then gives players priority.
That creates tactical windows between resolutions. If the top trigger changes a target, removes a permanent, alters a life total, or creates a new threat, reassess the stack before passing priority again. Improving at Magic often means treating each priority window as a new decision rather than committing mentally to the whole sequence at once; that same discipline supports better gameplay decisions throughout a game.
State-based actions can decide the result between triggers
Suppose several life-loss and life-gain triggers are stacked. A player at a dangerously low life total cannot simply total all pending gains and losses and apply the net result. Each object resolves separately, and state-based actions are checked before the game proceeds to the next priority window.
If the top trigger reduces a player to a losing life total, a lower life-gain trigger may never save that player. Conversely, a life-gain trigger higher on the stack may create enough room to survive a later life-loss effect. Exact APNAP order can therefore determine who remains in the game.
The practical lesson is to simulate the stack one resolution at a time. After each object, update life totals, permanents, legal targets, and any new triggers. If an unexpected outcome reveals a mistaken assumption, it is a useful candidate for a structured post-match misplay review.
Advanced details that commonly cause confusion
A source leaving the battlefield does not erase its trigger
Once an ability has triggered, its source usually does not need to remain on the battlefield for that ability to be put on the stack or resolve. For a permanent that has left the battlefield, control of its trigger is normally based on who controlled its source when it triggered.
Replacement effects are not triggered abilities
Triggered abilities normally use words such as “when,” “whenever,” or “at.” Replacement effects change how an event happens and do not wait as triggered abilities to be ordered through APNAP. Do not place every effect connected to the same event onto the stack; first determine whether each effect is actually a trigger.
Some triggers require an additional placement stage
The rules include specialized handling for abilities that trigger because another ability triggered. Those abilities can create an additional placement stage after the initial set of waiting triggers has been handled. This is an advanced exception: use the ordinary active-player-then-turn-order procedure first, then consult the exact current rule when a card explicitly cares about another ability triggering.
Shared-team-turn formats use teams
In formats with shared team turns, such as Two-Headed Giant, the active team orders its triggers first, followed by each nonactive team. That differs from applying an individual four-player Commander sequence to the members of each team.
The practical APNAP checklist
Before a board wipe, sacrifice, combat exchange, or other event likely to create several triggers, run this checklist:
- Whose turn is it? That identifies the active player.
- Which abilities actually triggered, and which effects are replacements instead?
- Who controlled each triggered ability when it triggered?
- What state-based actions occur before the triggers are stacked?
- How should the active player order their own triggers?
- Which player comes next in turn order, and how will that player order theirs?
- What is now on top of the completed stack?
- What targets and choices were made as the triggers were placed?
- Where can players respond, and what changes after each resolution?
The most useful shortcut is simple: active player stacks first, everyone else follows in turn order, and the top resolves first. Then slow down whenever life totals, targets, or new triggers could change between resolutions. APNAP tells you the starting order; good tactical play comes from recognizing what that order makes possible.
Frequently Asked Questions
What does APNAP mean in Magic?
APNAP means active player, nonactive player. It defines the order in which different players put simultaneous waiting triggers on the stack.
Who is the active player?
The active player is the player whose turn it is. Every other player is nonactive.
Do triggered abilities enter the stack immediately when they trigger?
Not necessarily. Waiting triggers are put on the stack after applicable state-based actions are checked and before a player receives priority.
Can I choose the order of multiple triggers I control?
Yes. You choose their relative order when putting them on the stack, and the one placed last will normally resolve first.
Whose simultaneous trigger resolves first?
The active player stacks their triggers first, followed by the other players in turn order. If nobody responds, the trigger placed highest on the completed stack resolves first.
How does APNAP work in four-player Commander?
Starting with the active player, each player adds their trigger group in turn order. The last player’s group is highest and normally begins resolving first, with each player controlling the order inside their own group.
When can players respond after triggers are stacked?
After state-based actions are handled and waiting triggers are stacked, the active player receives priority. Players also receive opportunities to act between resolutions rather than resolving the entire stack at once.
Can a triggered ability still resolve if its source left the battlefield?
Usually, yes. Once an ability has triggered, its source generally does not need to remain on the battlefield; control is normally based on who controlled the source when it triggered.
What if an ability triggers because another ability triggered?
The rules can require an additional trigger-placement stage after the initial waiting triggers are handled. Apply the ordinary APNAP procedure first, then consult the current rule for the specific interaction.