Not A Bug Ulamog the Defiler + Solitude

metamorph88

New member
I can't quite tell if this is a bug but I think it is. The way I understand the stack I don't think it worked correctly.

I also recognise I could've played this scenario in my favour but messed it up.


My opponent has an Ulamog the Defiler on the board. I cast solitude using its evoke cost.

Solitude enters, I put the targeting ability on the stack first targeting the Ulamog. I then go to stack the evoke trigger next, but the ward ability has entered the stack already. So the stack is now solitude -> ward -> evoke. I thought it was going to be solitude -> evoke -> ward.

I had just done this a game earlier but I stacked the evoke first, knowing this works in my favour (stack is evoke -> solitude -> ward, I can sack solitude). So I did mess this up, but I thought the ward cannot enter the stack until I finished stacking my abilities. I thought I had to stack all my abilities before my opponent gets priority, so their triggers during my stacking have to wait until priority is received (unless there is a choice the player has to make, in which case APNAP restarts. But in this case there is no choice being made other than putting ward ability on the stack).
 

Torbin

Staff member
Community Team
Tag applied: Not A Bug

The way effects works with the stack is that the first placed on the stack will be the last to be resolved.

In this case, if Evoke is placed first, and Solitude's Exile effect is placed second. Solitude's Exile effect will resolve first, which will triggering the Ward ability of Ulamog, the Defiler in response.

In this order, this would allow the user to sacrifice Solitude to the Ward response of Ulamog being targeted by Solitude.

If Evoke is the last effect to be placed on the stack, it will resolves first, destroying Solitude before the Ward effect resolves on the stack.
 
Top