On "cast" triggers, countering and the stack

Asked by dlanz 9 years ago

I was just wondering when "on cast" triggers a resolved as compared to the casted card and any counter spell cards targeting it.

In particular with Jeskai Ascendancy and Remand.

Scenario:If I have 2 blue mana (untapped) and 2 Birds of Paradise (tapped) and a Jeskai Ascendancy out.I cast a 2 mana spell with my open blue mana (I'm tapped out). Am I allowed to cast Remand on my own spell AFTER the Jeskai Ascendancy trigger but before the spell resolves (IE: both Birds of Paradise untap allowing me to pay for the Remand?

I would assume yes. The "casting" mechanic isn't complete until the spell resolves which would take it off of the stack and I would lose the chance to counter. I would imagine this is one of those instances where the player decides the order of precedence.

Dylan says... Accepted answer #1

Yes you are correct, the trigger for Jeskai Ascendancy is on the casting of the spell not the resolution, So in this case the birds would untap, you would loot and they get would get +1/+1 in whichever order you want. Then the spell would go onto the stack allowing you to remand it back to your hand and cast it again.

March 5, 2015 11:14 p.m.

Slycne says... #2

Casting as far are the rules of Magic are concerned is simply taking a card from a zone and putting it on the stack.

Jeskai Ascendancy triggers when you cast the spell. So those triggers end up above that spell on the stack and are resolved first. Because you control both triggers and they happen simultaneously you decide what order to resolve them.

And then remember that in order for any spell to resolve both players need to pass priority on it, so you have a chance after the Jeskai Ascendancy's triggers have resolved, but before the original spell has resolved to make actions. So you do have the opportunity to Remand your own spell.

March 5, 2015 11:19 p.m.

Slycne says... #3

PutridLeech just so there is no confusion. Casting a spell is the act of putting it on the stack. It doesn't enter the stack after the triggers have resolved it being added to the stack is what's triggering them and is there the whole time.

601.2. To cast a spell is to take it from where it is (usually the hand), put it on the stack, and pay its costs, so that it will eventually resolve and have its effect.

March 5, 2015 11:24 p.m.

Epochalyptik says... #4

Technically, Slycne, casting is the entire process of putting a spell onto the stack, making decisions for it, and paying its costs. The spell is not cast until all of the steps in the casting process are complete. This is relevant because it may affect whether certain on-cast abilities trigger. Specifically, if a permanent that is the source of an on-cast ability is sacrificed as part of the payment of an additional cost, the on-cast ability won't trigger (there was a question about this rather recently, actually).

March 5, 2015 11:37 p.m.

This discussion has been closed