Can I response to a Triggered hability on the stack?
Asked by ElgAbri 4 years ago
Ok, this is what happens in the game:
I have a Parallax Wave and there is my Gilded Drake and a Emissary of Grudges of my opponent removed with the Parallax.
In my turn, I blink the Parallax Wave , making my Gilded Drake and his Emissary of Grudges enters the battlefild again in the same time.
The abilities goes to the stack in APNAP order, Gilded Drake First, Emissary next. Resolving the abilities:
"As Emissary of Grudges enters the battlefield, secretly choose an opponent." - He chooses me.
"When Gilded Drake enters the battlefield, exchange control of Gilded Drake and up to one target creature an opponent controls." - I choose his Emissary of Grudges .
Nobody have anything to do now, than the stack beggins to resolve, and this is the problem (and the question):
My oponent wants to use the activated ability of the Emissary of Grudges (Reveal the player you chose: Choose new targets for target spell or ability if it's controlled by the chosen player and if it targets you or a permanent you control.) to change the target of my Gilded Drake for some other creature.
I say that this is not possible, because there is no priority for him betwin resolving his own trigger on the stack and mine. He says that he can.
So, what happens in this case? the trade happens or not?
Below is the rule:
117.5. Each time a player would get priority, the game first performs all applicable state-based actions as a single event (see rule 704, “State-Based Actions”), then repeats this process until no state-based actions are performed. Then triggered abilities are put on the stack (see rule 603, “Handling Triggered Abilities”). These steps repeat in order until no further state-based actions are performed and no abilities trigger. Then the player who would have received priority does so.
603.3b If multiple abilities have triggered since the last time a player received priority, each player, in APNAP order, puts triggered abilities they control on the stack in any order they choose. (See rule 101.4.) Then the game once again checks for and resolves state-based actions until none are performed, then abilities that triggered during this process go on the stack. This process repeats until no new state-based actions are performed and no abilities trigger. Then the appropriate player gets priority.
Boza, so my oponent is right, his Emissary of Grudges can change the target of Gilded Drake ?
July 10, 2019 10:16 a.m.
I thought I started my previous post with that, but Emissary can redirect the Gilded drake ability.
July 10, 2019 11:04 a.m.
Yes, that's right. Priority is always passed by all players before the anything on the stack resolves. Your opponent has a chance to respond to your ability before it resolves.
July 10, 2019 11:30 a.m.
Oh. I'm not sure if it counts as being ninja-d when the issue was that I got distracted and took 25 minutes to actually hit the post button.
July 10, 2019 11:31 a.m.
Thanks Boza, I understand that he can do it, but I only have a doubt about the rule 603.3b when it sais:
"the game once again checks for and resolves state-based actions until none are performed, then abilities that triggered during this process go on the stack. This process repeats until no new state-based actions are performed and no abilities trigger. Then the appropriate player gets priority."
I think that you can respond to an event as normal, and this can put more triggers on the stack too. But when nobody has nothing to do and the game starts resolving the Trigger stack, you cant respond betwin on and other trigger. This is not correct?
July 11, 2019 10:41 a.m.
In order for any item on the stack to resolve, the players must each pass priority in turn without adding anything to the stack. This applies for every single item in the stack. They don't resolve in one bunch.
So in your scenario, here's what happens, broken down:
-
You blink Parallax Wave , let's say with something that returns it right away, since you didn't say. Your blink effect is on the stack, and the Parallax is still on the board.
-
You have priority first (since you're the one who used the blink effect). You pass without adding anything. Your opponent passes without adding anything to the stack either. Parallax Wave leaves the battlefield, triggering its LTB, then returns with 5 fading counters on it.
-
Triggered abilities go on the stack when a player would next receive priority, and state-based actions are checked first. There are no state-based actions to worry about here, so your Parallax trigger goes on the stack.
-
In order for the trigger to resolve, everyone must pass priority again without adding things to the stack. We'll say you do so.
-
Parallax trigger resolves, returning both Gilded Drake and Emissary of Grudges to the battlefield. Your opponent secretly chooses you for Emissary. Gilded Drake triggers.
-
Still no state-based actions. Drake trigger goes on the stack, and you target Emissary.
-
In order for the Drake trigger to resolve, everyone must pass priority without adding things to the stack. However, when your opponent receives priority, they instead choose to activate Emissary of Grudges , targeting the Drake triggered ability and changing its target to another creature you don't control. There are no timing or targeting restrictions, everything is legal. Now Emissary's ability is on the stack on top of the Drake's.
-
A new round of priority begins with your opponent (since he can hold priority after adding Emissary's ability to the stack). We'll assume that no one else adds anything to the stack as priority passes around the table once.
-
Emissary's ability resolves, switching Drake's target.
-
Another round of priority happens, starting with you (active player) since no one directly added a spell/ability and held priority. We'll again assume no one adds anything to the stack.
-
Drake ability resolves, switching control with the new target, not the Emissary. The stack is now empty.
Your comment about "no priority for him between resolving his own trigger on the stack and mine" doesn't work. First, he has no triggers to worry about. As others have mentioned, choosing an opponent secretly is something that happens as Emissary of Grudges enters the battlefield. It's not a triggered ability (which begin with "when, whenever, or at"). It can't be responded to. It's timing is simultaneous with it entering the battlefield. Your Gilded Drake , on the other hand, has a triggered ability that must go on the stack when a player would receive priority, and then resolve to happen.
Second, currently the only thing that can prevent people from responding to a spell or ability on the stack is the Split Second mechanic, as seen on cards like Sudden Spoiling , which explicitly prevent players from casting spells or activating abilities that aren't mana abilities while it's on the stack (special actions and mana abilities are still allowed). Gilded Drake 's ability doesn't have any effect that would prevent your opponent from activating an ability in response to it.
Third, each item on the stack must resolve individually, and players each receive priority between every item on the stack. You can have a stack four items tall, resolve two of them, add three more, resolve four of them, add another, and so on, as long as players have the means to do so. The stack is not resolved in one large chunk.
Long-winded, but hopefully clears it up for you.
July 11, 2019 11:13 a.m.
This was perfect Kogarashi, thanks a lot for the detailed explanation!
Boza says... #1
Emisarry's first text block starts "as ~ enters the battlefield", meaning the choice is made right before the card ETBs.
The second ability requires to reveal the chosen player and it must be specifically in response to an ability targeting Emissary of Grudges 's controller or his/her permanents.
Even if we assume it is an ETB ability, even then, before any item on the stack resolves, there is a round of priority when any player has a chance to respond. The topmost object on the stack resolves only when all players in succession pass priority without taking an action.
July 10, 2019 9:49 a.m. Edited.