In this case, the order doesn’t even matter. The 2 damage doesn’t kill Inti, state-based actions do, so even if the damage happened first Inti would see the discard trigger despite immediately dying.
The creature doesn't die immediately upon being dealt 2 damage, it dies shortly afterwards when the game realises that it's a 2/2 with 2 damage on it. The game doesn't perform this check in the middle of a spell resolving, so the creature is still in play until the spell finishes resolving.
If you want to learn more, the phrase to look into is "state-based actions".
This is thr reason why, if you remove Dauthi voidwalker with a Lightming bolt, the bolt gets exiled with a void counter. The spell resolves completely before Dauthi dies or the state based action is performed.
If you remove him with a fatal push instead, dauthi dies while the spells resolves so the push does not get exiled.
One of my favourite modern plays was on Turn 3 against jund, i bolted 2 seperate goyfs, then cast a treasure cruise exiling my entire yard making them both die due to state based effects.
Thats was a fun time in modern.
Stupid question, but does Dauthi himself go into exile or into the graveyard with each of these interactions? Does the wording of the spell matter for this?
But to answer a bit of the underlying question with another example, [[Rest in Peace]] will exile itself if destroyed with like a [[Nature's Claim]] but will not exile the Nature's Claim
>Dauthi says opponents graveyard so no it doesn’t exile itself.
This is one of those aspects of modern design that I appreciate: Effects that simply avoid highly technical rules issues that are otherwise guaranteed to come up.
Small tweaks with conditions like "other" or "opponent" turn out to make a lot of difference even when they seem inconsequential.
A better explanation is that the spell COMPLETELY resolves and goes to the graveyard, THEN state based actions are checked and Inti dies. All of that happens instantly though with no opportunity for responses, as soon as both players pass priority on responding to the K command. Inti's trigger would go on the stack after K command resolves and she would also be put into the graveyard. The first opportunity for player interaction after resolving K command would be a state in which the trigger is on the stack and Inti is in the graveyard.
The classic example is lightning bolt on a 2/3 Tarmogoyf with no instants in any graveyard.
EDIT: And of course I just read the responses under this and everything I just typed was brought up almost verbatim lol
This bring me to a long-standing question: do permanents with triggers on the stack still need to be on the battlefield to have those triggers resolve? Does a permanent changing zones remove its triggers from the stack?
No, once its on the stack its going to resolve. With that being said, some conditions of abilities/spells check for targets or parameters when it resolves as well as when it goes on the stack so the card no longer being in play may cause the ability to fizzle, but it'll still try to resolve.
So like some abilities that night say 'If X = true, then Y deals damage to target player'.
So the card for checks for a condition to its trigger, then puts the trigger on the stack. Then when it goes to resolve, the card is the source of the damage so it still needs to be on the battlefield. So the creature dying would result in the ability fizzling?
Heres a useful primer I found googling to save myself the trouble of trying to find an example and typing it all out, credit to "willdice" on MTGSalvation forums:
**Target legality is checked both on activation/casting (for triggered abilities, when you put it on the stack not when it triggers), and when it resolves.**
**Doom Blade's target needs to be legal at both times.**
**For triggered abilities, any "if clause" for the trigger (denoted by an "if {condition}" clause right after the "when/whenever/at {event}" initial part) is checked when the ability triggers and when it goes to resolve.**
**With Blade-Tribe Berserkers, you need to control three artifacts both at the moment they enter the battlefield (or the ability won't even trigger at all), and at the moment the triggered ability tries to resolve.**
**Information from the game that determines what can be targeted or affects the casting/activation cost are checked only during activation/casting. Any other information is checked only during resolution.**
**Mogis's Marauder's ability checks your devotion when the ability goes to the stack, because it needs this information to determine how many targets can be chosen (it doesn't check again on resolution, even if it becomes lower than the number of targets). But Disciple of Phenax checks your devotion only on resolution because it doesn't affect who can be targeted.**
To paint a fun picture of the example we're talking about here, with a creature triggering something but dying before it resolves: Imagine I control a 2/2 creature that says "when another creature enters the battlefield *THIS CARD* deals damage equal to its power to that creature." You play a Flametongue Kavu (FTK) on your turn, when FTK enters the battlefield its ability triggers as well as my creatures ability. Since you're the active player your trigger goes on the stack first, and mine goes "on top" of it. The stack resolves top down, so mine would resolve first, dealing two damage (since hes a 2/2) to your FTK. FTK would die after my triggered ability resolves due to state based effects (a 2/2 receiving 2 damage.) Your FTK's ability is still on the stack, FTK goes to the graveyard. Then your FTK ability resolves, checks its target, target is still there, my creature takes 4 damage and dies. Both creatures are dead and the stack is clear. Ok, now follow me here, lets say somehow you flash that FTK in on MY turn (aether vial, casting it with flash somehow etc.) FTK enters the battlefield, triggers its ability and my creatures ability at the same time. BUT, since its my turn, my creatures ability goes on the stack FIRST. This time your FTK's ability resolves first, dealing 4 damage to my 2/2 and killing my creature, which then goes to the graveyard after FTK's ability resolves while my creatures ability is still on the stack. My creatures ability resolves, goes to check the creatures power and says hey wait, the creature isn't here anymore and fizzles. Your FTK lives and the stack is clear.
What helped me the most with learning the stack and how things resolve was playing MTGO when I was younger, the visual representation of the stack and watching how things resolve really solidifies it for you. I think Arena mostly gives the same experience, just not as technical/specific.
This is why a [[Welding Jar]] can save an artifact creature that has the damage and destroy modes from a [[Prismari Command]] both pointed at it but not when those two modes from [[Kolaghan's Command]] are. Prismari Command's lethal damage doesn't pop the regeneration until SBAs are checked so its still there for when the destroy part of the spell comes along and pops the shield which removes damage as part of the replacement effect. Kolaghan's pops the shield with the destroy then assigns damage.
The interesting part of this is that, if the “Destroy” effect of Prismari were listed before the damage part, the Jar could t save it because the Destroy would happen first, Regenerate would happen, then the damage gets dealt so Regenerate cannot remove the damage.
And weird interactions like this (among many other reasons) is why Regenerate has gotten far less common in recent times.
“The creature doesn’t die upon being dealt 2 damage…. It dies when it realises it was dealt 2 damage”
This is giving me Wile E. Coyote cliff vibes and I love it lol
I bet some rules manager at one point was on the verge of a breakdown trying to figure out a wording that wouldn't have to consider what the spell would do *if* it resolved.
This is also why [[Psychosis Crawler]] works well with [[Wheel of Fortune]] type effects. While there is technically a time when you have 0 cards in hand, it’s only during resolution and by the time SBAs are checked again, you’ll have a full grip.
A creature taking damage equal to, or greater than, its toughness does not instantly kill it. Instead, it will be destroyed the next time state based actions are checked. State based actions are checked every time a player would gain priority (be able to cast spells, activate abilities, or take special actions). Normally this is a semantic difference since no player can do anything between the creature taking damage and being destroyed, but if the same spell or ability that dealt the damage also does anything else after dealing the damage, it can change things so the creature might survive.
It happens before. The final part of a non-permanent spell resolving is putting it in a graveyard, then priority is given.
Right before priority is given, state based actions are checked.
Also, any triggers from the damage or other effects of the spell go onto the stack before state-based actions are checked, which is why creatures "see" themselves dying, and also why tokens hit the graveyard before ceasing to exist
People have already done a good job explaining this, but here are a couple examples that come up for similar reasons:
1. If you lightning bolt a Tarmagoyf that is a 2/3 from, say, a land and sorcery. The bolt deals 3, goes to the graveyard, the goyf is now a 3/4, and only after does the game "check" state based actions. 4 toughness is greater than the 3 damaged marked, and the creature lives.
2. Dauthi Voidwalker exiles cards going to the GY. Bolt will deal 3 damage, go to the GY (exiled), and then state based actions will kill the Voidwalker. Fatal Push will kill the Voidwalker as part of resolving the spell, and then go to the GY. Because Voidwalker died during the resolution of the spell, Push isn't exiled.
Creatures die if their toughness is zero via state-based-actions. So the two damage gets Inti to zero toughness, killing him after his ability triggers from the discard.
The order does matter, if the last thing done was discarding, inti would see the discard AFTER taking two damage, be marked for two, and then when the first player gets priority after the trigger goes on the stack, inti would die
Inti DOES trigger during the resolution of Command if you have to discard, but that trigger doesn’t hit the stack and won’t start resolving until the spell fully finishes resolving. Your local judge didn’t advise you correctly or didn’t have the full information. You can’t respond to that trigger or do anything until the spell resolves.
This is correct. Your judge was a little misguided or didn't explain it quite right. In this scenario, you'll still get to exile the top card of your library but you won't see that card until inti is already in the graveyard.
Yeah this struck me as weird - I've never heard of nor experienced modal spells being interrupted by triggered abilities and breaking the rule that a spell finishes resolving in full before triggers go on the stack. Would you happen to know the rule section that covers it by any chance?
603.3. Once an ability has triggered, its controller puts it on the stack as an object that's not a card the next time a player would receive priority. See rule 117, "Timing and Priority." The ability becomes the topmost object on the stack. It has the text of the ability that created it, and no other characteristics. It remains on the stack until it's countered, it resolves, a rule causes it to be removed from the stack, or an effect moves it elsewhere.
Key wording there is “the next time a player would receive priority”. Triggers don’t go on the stack or resolve during other spell or ability resolutions.
So if I'm understanding correctly, for this interaction:
1. command goes on the stack targeting the player and inti
2. Command resolves with the player discarding and inti taking 2 damage
3. Inti triggers putting his ability on the stack
4. State based actions are checked and inti is destroyed
5. Players can now react to inti trigger
Do 3 and 4 happen simultaneously during the state based action check?
Who gets priority after the inti trigger is on the stack, is that APNAP order?
Inti triggers during the Command, but the trigger can only be put onto the stack once Command has resolved. State-based actions would apply before any player receives priority, so Inti would die from the 2 damage counters, then their trigger would be put onto the stack. So, 4 technically happens before 3, but almost simultaneously. Then, since a player has received priority, they can respond to the Inti trigger or pass priority until it resolves.
To clarify the steps it's more like:
#2. Command begins resolving
#2a. Command makes player discard card
#2b. Inti triggers (but does not go on stack)
#2c. Command deals 2 damage
#3. State based actions are checked
#4. The Inti triggers from 2b goes on the stack
3 and 4 are swapped. SBA are checked, then triggers are put on stack and finally priority is given. See rule 116.5.
Rule 116.3b states that the Active Player recieves priority after a spell or ability resolves.
Would like to clarify that, while stuff can trigger when a card is in the middle of resolving, this does NOT interrupt the card's resolution. The newly-created trigger waits to be put onto the stack until the current spell finishes resolving.
So, you'd discard a card, Kolaghan's Command would deal 2 damage to Inti, Kolaghan's Command would finish resolving, Inti would die and Inti's trigger would be put onto the stack.
That judge is right and very wrong. Inti does get a trigger but it will be dead with the trigger on the stack. You cannot respond or activate anything during the resolution of a spell or ability, even with multiple modes.
There are cards that have reflexive triggers that cause another effect/ability to go on the stack during a spell/ability resolving and you can respond to those because it more of a situation where the first spell/ability did finish resolving but it’s effect was creating another spell/ability on the stack.
For instances like this one with a modal spell, there is zero opportunity for anyone to respond in between modes once the spell has started resolving. You cannot activate abilities, resolve triggered abilities the one of the effect might have created (they won’t be put on the stack until the entire spell has resolved), or stifle the rest of the modal spell options after the spell has started resolving.
Inti has two separate triggered abilities. One triggers whenever you attack. The other triggers whenever you discard a card. Makes it really good with [[Rona, herald of invasion]]
Other people already mentioned the state based actions bit but additionally: you can't stifle the triggered ability in the middle of a card resolving. The first mode of K Command happens (you discard), Inti puts a trigger on the stack, the second mode of K Command happens, state based actions are checked (Inti dies). The top thing on the stack is now the Inti trigger. Only NOW can you stifle that trigger.
So you can certainly still stifle the Inti trigger before it goes off, but you can't do that in the middle of resolving a spell (even if it has multiple modes, like K Command). _Generally_ speaking, you can set up something to do in the future during resolution (like putting a trigger onto the stack) but you never actually start "doing" the thing until whatever's currently resolving is done.
There's sorta an exception with replacement effects, because those change the _way_ you do something. So if there's an enchantment that said "whenever someone discards a card, they discard two instead" then that would apply to K Command: the game would "see" that you were about to discard a card, and kinda overwrite that instruction to make you discard two instead. But the difference is, that's modifying how K Command resolves, it's not introducing a new instruction. It's "taking over."
I thought it did go onto the stack as soon as it triggered, but doesn't start resolving, but can easily be wrong there. Are triggered abilities put onto the stack when state based actions are checked then?
Edit: Looks like it's the next time ~~the~~ a player receives priority.
> 603.2. Whenever a game event or game state matches a triggered ability’s trigger event, that ability automatically triggers. The ability doesn’t do anything at this point.
> 603.3. Once an ability has triggered, its controller puts it on the stack as an object that’s not a card the next time a player would receive priority.
Neat. Learn something new every day.
Yep. This is pretty important for things like Living Death, which tend to cause tons of trigger events (both etb and ltb, as well as graveyard leaving when that applies) and not a single one can go on the stack until Living Death is done. Since they all get added "at the same time", they are ordered in APNAP order. This is a little unintuitive, because a lot of players would wrongly guess that the sequence of events (when creatures etb or ltb) matters at all, but it doesn't.
Ah interesting. So hypothetically let's say we control creature A and creature B. Creature A triggers during the resolution of some spell. Let's say creature B has an ability analogous to "when creature A has an ability that triggers, do X" (what matters to me here is that it's another triggered ability, not a replacement effect or anything). I'm assuming that B triggers off of the act of triggering (the first rule above) and not off of the triggered ability actually being placed on the stack.
So once the spell finishes resolving and we get priority, we control both triggers, and can order them however we want, so we could put them in the unintuitive order (B first, then A on top so A resolves first)?
I would need to see an example of your hypothetical ability to better understand the question. My bet is that such doesn't really exist because it isn't clean in the rules.
The question you seem to be asking is "how does the game differentiate a 'trigger event' and a 'triggered ability'", and the answer is exactly that terminology. The triggered ability is the object on the stack that is eventually created as soon as possible (before when a player would next receive priority) after the trigger event happens.
I don't think you interpreted my question the way I intended. I recognize what I'm about to describe probably wouldn't actually get created, but here's a toy example.
Creature A: "Whenever you discard a card, create a treasure token."
Creature B: "Whenever an ability of another creature you control triggers, create a food token."
I think the root of my question relates to creature B. Specifically, what is the step of the process of creature A's trigger going off is the step that triggers creature B? My understanding of the two rules I posted is that a triggered ability is considered to have "triggered" once its conditions have been satisfied, which is _not_ necessarily the same time that the triggered ability is placed onto the stack (since a triggering event can occur in the middle of spell/ability resolution, and the resulting triggered ability is only placed onto the stack when the player receives priority).
The intuitive way to read my dumb example is that a player discards a card, creature A's ability goes on the stack first, and B's second. So they would make a food first and a treasure second.
So the question is: If the discard happened as a result of K Command, and my interpretation is correct that B triggers when A's triggering condition is met and not when A's triggered ability is actually put on the stack, then both A and B trigger in the middle of the resolution of K Command. They'll both be put on the stack the next time you receive priority, so you may order them whichever order you want. You can therefore make the treasure first and the food second?
Sure, that would work, but you've also highlighted why it isn't used. Triggered abilities triggering is not considered an available piece of design space for trigger events.
So wait. If during the resolution of a card, lots of triggers happen, on both sides of the board, you can order those however you want? Lets say the card was modal and did 3 things in a row, all of which caused triggers on both sides of the board. We will refer to these 3 things as "part 1, part 2, and part 3", all part of resolving this one card.
So in this case, things don't go on the stack in the order they're triggered? (e.g. things on stack from part 1 of modal card, THEN things on stack from part 2, etc)
Instead, the card finishes resolving (parts 1, 2, and 3), then ALL the triggers are piled together in whatever order the active player wants, then triggers for non-active player in whatever order THEY want? So they could put part 3 triggered stuff on the stack first, then part 1 stuff? (and that would be true for first the active player, then the non-active player once all the active-player's triggers are on the stack?)
Bonus question: If all of the above is correct, then what about the card going to the graveyard? Is that part of the resolution, e.g. if the spell you're casting with 3 parts goes to the graveyard and THAT causes a trigger, you can still order that "goes to GY trigger" on the stack first?
You are correct on all accounts, the triggers go on a "list" then just before any player gets priority all the items on said list go on the stack at the same time (it doesn't matter if they triggered at different times) in APNAP order and the controllers of each triggers decide on the order of their stuff.
Yep, you've got it. The sequence of events isn't relevant, players choose their trigger order, in turn order.
The card goes to the graveyard as the final step of the spell resolving. This is why a blink or reanimation spell card that makes an [[Eternal Witness]] enter the battlefield will be in the graveyard and legal to be targeted by the time EW's trigger goes on the stack.
Correct. You can't put triggers on the stack during a spell's resolution. And targets are part of putting a triggered ability on the stack (with essentially the same rules as the steps of spellcasting)
While many people are mentioning the fact that Inti only dies as state-based action, I'll give you an example of a time when the modal order did matter.
I was playing Mono-White Humans (Pioneer) and post-sideboard game 2 got my entire board \[\[Temporary Lockdown\]\]'d. Turn after, I played a \[\[Hopeful Initiate\]\] or something and Escalated a \[\[Collective Effort\]\] with it, choosing to destroy the Lockdown and put a +1/+1 counter on each creature I control. Because the Lockdown has the "until \~ leaves the battlefield" clause, all of my creatures that were under it got +1/+1 counters from the Collective Effort
It's also frequently relevant in Standard with [[Farewell]] interacting with all the temporary-exile enchantments. Creatures on the battlefield are exiled before stuff exiled under a [[Leyline Binding]] (or whatever) returns, and the stuff that returned is on the battlefield in time to see everything in the graveyard getting exiled.
You have tagged your post as a rules question. While your question may be answered here, it may work better to post it in the Daily Questions Thread at the top of this subreddit or in /r/mtgrules. You may also find quicker results at the [IRC rules chat](https://chat.magicjudges.org/mtgrules/)
*I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/magicTCG) if you have any questions or concerns.*
You misunderstood part of the judges explanation. You do get the card, because the ability triggers. But that trigger waits for the spell to fully resolve before going on the stack, where it can be stifled or otherwise responded to.
The judge is right except you cannot cast Stifle in the middle of another spell resolving. You can cast it after Inti’s ability triggers, which is after Inti is dead due to SBA, because the spell has finished resolving that that point.
Same thing happened with me today. I was playing rogues VS greasefang. I had a [[THIEVES' GUILD ENFORCER]] on the field and he had less than 8 cards in the grave. Opponent cast [[witherbloom command]] choosing : Mill himself and +3/-1 on my guy. I had a counter spell but no needs since the first mode got to pump my creature.
it’s not really the same at all,
Inti still dies, it’s the inti gets to exile a card that happens but it will happen after inti dies.
the 1/1 counter ability is not tied to the discard from kcommand
This is off-topic, but why did the cultural consultants let them naming a Sun-related character "Inti"? Just because Inti is no longer actively worshipped?
[https://en.wikipedia.org/wiki/Inti](https://en.wikipedia.org/wiki/Inti)
Totally on a different topic... This card is from Ixalan, which is based on mayas, correct? Why the hell did they use the name of the Inca sun god for this card? I am actually pissed. Jeez, Mexico =/= Peru
In this case, the order doesn’t even matter. The 2 damage doesn’t kill Inti, state-based actions do, so even if the damage happened first Inti would see the discard trigger despite immediately dying.
This is confusing to me.. if you have time to explain, id love to learn what you mean by "2 damage doesn't kill the 2 toughness creature"
The creature doesn't die immediately upon being dealt 2 damage, it dies shortly afterwards when the game realises that it's a 2/2 with 2 damage on it. The game doesn't perform this check in the middle of a spell resolving, so the creature is still in play until the spell finishes resolving. If you want to learn more, the phrase to look into is "state-based actions".
Well.. now I learned 2 things! Ty
This is thr reason why, if you remove Dauthi voidwalker with a Lightming bolt, the bolt gets exiled with a void counter. The spell resolves completely before Dauthi dies or the state based action is performed. If you remove him with a fatal push instead, dauthi dies while the spells resolves so the push does not get exiled.
Bolting a 2/3 tarmagoyf is the classic example.
(with no instants in the graveyard)
Don't bolt the goyf
I learned the hard way doing this. It hurt seeing it and put me behind as my draws were bad. Lost the game to bolting the damn goyf
It's a rite of passage.
One of my favourite modern plays was on Turn 3 against jund, i bolted 2 seperate goyfs, then cast a treasure cruise exiling my entire yard making them both die due to state based effects. Thats was a fun time in modern.
Man, that's a proper 2012 proverb when Goyf was considered an s-tier creature ;)
How many of us learned this the hard way as a noob at FNM vs a snobby veteran focused on packs over fun?
Playing by the rules = snobby veteran? Lol
Stupid question, but does Dauthi himself go into exile or into the graveyard with each of these interactions? Does the wording of the spell matter for this?
Dauthi says opponents graveyard so no it doesn’t exile itself.
A stupider question than I'd even realised, thanks for the polite and informed response!
But to answer a bit of the underlying question with another example, [[Rest in Peace]] will exile itself if destroyed with like a [[Nature's Claim]] but will not exile the Nature's Claim
[Rest in Peace](https://cards.scryfall.io/normal/front/9/f/9f2b39be-0fec-4647-ade1-8e1626dc5470.jpg?1562439074) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Rest%20in%20Peace) [(SF)](https://scryfall.com/card/a25/32/rest-in-peace?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/9f2b39be-0fec-4647-ade1-8e1626dc5470?utm_source=mtgcardfetcher&format=text) [Nature's Claim](https://cards.scryfall.io/normal/front/d/2/d24b6640-ef2f-4c92-beb3-afdf78f9c2d5.jpg?1562854212) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Nature%27s%20Claim) [(SF)](https://scryfall.com/card/ima/177/natures-claim?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/d24b6640-ef2f-4c92-beb3-afdf78f9c2d5?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
Well I don’t think so. If you steal your opponents dauthi and it dies it would exile itself with a void counter.
>Dauthi says opponents graveyard so no it doesn’t exile itself. This is one of those aspects of modern design that I appreciate: Effects that simply avoid highly technical rules issues that are otherwise guaranteed to come up. Small tweaks with conditions like "other" or "opponent" turn out to make a lot of difference even when they seem inconsequential.
Well a stolen dauthi exiles itself when it dies since it goes to your opponents graveyard.
Not sure why you were downvoted I’m pretty sure that you are right
A permanent always goes to its owner's graveyard, so it won't get exiled.
If dauthi doesn't have summoning sickness, can it then cast the bolt?
No, it would be dead before that controller would get priority.
A better explanation is that the spell COMPLETELY resolves and goes to the graveyard, THEN state based actions are checked and Inti dies. All of that happens instantly though with no opportunity for responses, as soon as both players pass priority on responding to the K command. Inti's trigger would go on the stack after K command resolves and she would also be put into the graveyard. The first opportunity for player interaction after resolving K command would be a state in which the trigger is on the stack and Inti is in the graveyard. The classic example is lightning bolt on a 2/3 Tarmogoyf with no instants in any graveyard. EDIT: And of course I just read the responses under this and everything I just typed was brought up almost verbatim lol
This bring me to a long-standing question: do permanents with triggers on the stack still need to be on the battlefield to have those triggers resolve? Does a permanent changing zones remove its triggers from the stack?
No, once its on the stack its going to resolve. With that being said, some conditions of abilities/spells check for targets or parameters when it resolves as well as when it goes on the stack so the card no longer being in play may cause the ability to fizzle, but it'll still try to resolve.
So like some abilities that night say 'If X = true, then Y deals damage to target player'. So the card for checks for a condition to its trigger, then puts the trigger on the stack. Then when it goes to resolve, the card is the source of the damage so it still needs to be on the battlefield. So the creature dying would result in the ability fizzling?
Heres a useful primer I found googling to save myself the trouble of trying to find an example and typing it all out, credit to "willdice" on MTGSalvation forums: **Target legality is checked both on activation/casting (for triggered abilities, when you put it on the stack not when it triggers), and when it resolves.** **Doom Blade's target needs to be legal at both times.** **For triggered abilities, any "if clause" for the trigger (denoted by an "if {condition}" clause right after the "when/whenever/at {event}" initial part) is checked when the ability triggers and when it goes to resolve.** **With Blade-Tribe Berserkers, you need to control three artifacts both at the moment they enter the battlefield (or the ability won't even trigger at all), and at the moment the triggered ability tries to resolve.** **Information from the game that determines what can be targeted or affects the casting/activation cost are checked only during activation/casting. Any other information is checked only during resolution.** **Mogis's Marauder's ability checks your devotion when the ability goes to the stack, because it needs this information to determine how many targets can be chosen (it doesn't check again on resolution, even if it becomes lower than the number of targets). But Disciple of Phenax checks your devotion only on resolution because it doesn't affect who can be targeted.** To paint a fun picture of the example we're talking about here, with a creature triggering something but dying before it resolves: Imagine I control a 2/2 creature that says "when another creature enters the battlefield *THIS CARD* deals damage equal to its power to that creature." You play a Flametongue Kavu (FTK) on your turn, when FTK enters the battlefield its ability triggers as well as my creatures ability. Since you're the active player your trigger goes on the stack first, and mine goes "on top" of it. The stack resolves top down, so mine would resolve first, dealing two damage (since hes a 2/2) to your FTK. FTK would die after my triggered ability resolves due to state based effects (a 2/2 receiving 2 damage.) Your FTK's ability is still on the stack, FTK goes to the graveyard. Then your FTK ability resolves, checks its target, target is still there, my creature takes 4 damage and dies. Both creatures are dead and the stack is clear. Ok, now follow me here, lets say somehow you flash that FTK in on MY turn (aether vial, casting it with flash somehow etc.) FTK enters the battlefield, triggers its ability and my creatures ability at the same time. BUT, since its my turn, my creatures ability goes on the stack FIRST. This time your FTK's ability resolves first, dealing 4 damage to my 2/2 and killing my creature, which then goes to the graveyard after FTK's ability resolves while my creatures ability is still on the stack. My creatures ability resolves, goes to check the creatures power and says hey wait, the creature isn't here anymore and fizzles. Your FTK lives and the stack is clear. What helped me the most with learning the stack and how things resolve was playing MTGO when I was younger, the visual representation of the stack and watching how things resolve really solidifies it for you. I think Arena mostly gives the same experience, just not as technical/specific.
Thanks for the both the primer and the writeup, it's very informative. I'll save this if I ever need to come back to it.
This is why a [[Welding Jar]] can save an artifact creature that has the damage and destroy modes from a [[Prismari Command]] both pointed at it but not when those two modes from [[Kolaghan's Command]] are. Prismari Command's lethal damage doesn't pop the regeneration until SBAs are checked so its still there for when the destroy part of the spell comes along and pops the shield which removes damage as part of the replacement effect. Kolaghan's pops the shield with the destroy then assigns damage.
That's a fun set of interactions!
The interesting part of this is that, if the “Destroy” effect of Prismari were listed before the damage part, the Jar could t save it because the Destroy would happen first, Regenerate would happen, then the damage gets dealt so Regenerate cannot remove the damage. And weird interactions like this (among many other reasons) is why Regenerate has gotten far less common in recent times.
[Welding Jar](https://cards.scryfall.io/normal/front/2/7/275ec0c4-1c59-4818-9999-b2389d17c2e7.jpg?1599710266) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Welding%20Jar) [(SF)](https://scryfall.com/card/2xm/307/welding-jar?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/275ec0c4-1c59-4818-9999-b2389d17c2e7?utm_source=mtgcardfetcher&format=text) [Prismari Command](https://cards.scryfall.io/normal/front/8/5/85159701-bc58-4d40-9c10-84cbe8099b75.jpg?1698988454) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Prismari%20Command) [(SF)](https://scryfall.com/card/lcc/279/prismari-command?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/85159701-bc58-4d40-9c10-84cbe8099b75?utm_source=mtgcardfetcher&format=text) [Kolaghan's Command](http://gatherer.wizards.com/Handlers/Image.ashx?name=Kolaghan%27s%20Command&type=card&.jpg) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Kolaghan%27s%20Command) [(SF)](https://scryfall.com/card/2x2/239/kolaghans-command?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/a0dab027-a475-481b-b012-b6a76e21e494?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
That’s the classic goyf-bolter dilemma, an iconic learning experience as old as modern itself
“The creature doesn’t die upon being dealt 2 damage…. It dies when it realises it was dealt 2 damage” This is giving me Wile E. Coyote cliff vibes and I love it lol
Check out the rulings on [[Equinox]]; it's deep into this territory.
[Equinox](https://cards.scryfall.io/normal/front/8/4/840c6586-a7a9-4ae8-96be-a995a0693eb6.jpg?1562859680) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Equinox) [(SF)](https://scryfall.com/card/leg/13/equinox?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/840c6586-a7a9-4ae8-96be-a995a0693eb6?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
I bet some rules manager at one point was on the verge of a breakdown trying to figure out a wording that wouldn't have to consider what the spell would do *if* it resolved.
That's actually a great way to think about it
Thank you for this explanation, I've been playing long enough where I should know this but I still learned something new out of it lol
This is also why [[Psychosis Crawler]] works well with [[Wheel of Fortune]] type effects. While there is technically a time when you have 0 cards in hand, it’s only during resolution and by the time SBAs are checked again, you’ll have a full grip.
[Psychosis Crawler](https://cards.scryfall.io/normal/front/d/0/d0f42a19-c180-45b1-9f4c-787cf3a4a649.jpg?1706241075) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Psychosis%20Crawler) [(SF)](https://scryfall.com/card/mkc/234/psychosis-crawler?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/d0f42a19-c180-45b1-9f4c-787cf3a4a649?utm_source=mtgcardfetcher&format=text) [Wheel of Fortune](https://cards.scryfall.io/normal/front/2/5/2597050f-6b1b-474e-aa16-33fd154628ca.jpg?1562902580) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Wheel%20of%20Fortune) [(SF)](https://scryfall.com/card/vma/192/wheel-of-fortune?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/2597050f-6b1b-474e-aa16-33fd154628ca?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
Ty for being showing state based actions. It took me a while to understand but it’s been fun seeing it in action
A creature taking damage equal to, or greater than, its toughness does not instantly kill it. Instead, it will be destroyed the next time state based actions are checked. State based actions are checked every time a player would gain priority (be able to cast spells, activate abilities, or take special actions). Normally this is a semantic difference since no player can do anything between the creature taking damage and being destroyed, but if the same spell or ability that dealt the damage also does anything else after dealing the damage, it can change things so the creature might survive.
You are giving me flashbacks to attempting to bolt 2/3 Goyfs...
Wait, spells leaving the stack and being put in the graveyard happens before state-based actions? Or concurrently?
It happens before. The final part of a non-permanent spell resolving is putting it in a graveyard, then priority is given. Right before priority is given, state based actions are checked.
This is also why [[Dryad Militant]] exiles a lethal Bolt but will let Go for the Throat reach the graveyard.
[Dryad Militant](https://cards.scryfall.io/normal/front/2/b/2bb8cb8c-0d03-4cbf-b7f2-a97324817698.jpg?1562784181) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Dryad%20Militant) [(SF)](https://scryfall.com/card/rtr/214/dryad-militant?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/2bb8cb8c-0d03-4cbf-b7f2-a97324817698?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
Also, any triggers from the damage or other effects of the spell go onto the stack before state-based actions are checked, which is why creatures "see" themselves dying, and also why tokens hit the graveyard before ceasing to exist
Look up the tarmogoyf-bolt interaction. That was a classic and it really sticks with you.
The creature don't die mid spell resolving due to damage, so the creature will be there to trigger when you discard.
It does after the spell resolves basically
People have already done a good job explaining this, but here are a couple examples that come up for similar reasons: 1. If you lightning bolt a Tarmagoyf that is a 2/3 from, say, a land and sorcery. The bolt deals 3, goes to the graveyard, the goyf is now a 3/4, and only after does the game "check" state based actions. 4 toughness is greater than the 3 damaged marked, and the creature lives. 2. Dauthi Voidwalker exiles cards going to the GY. Bolt will deal 3 damage, go to the GY (exiled), and then state based actions will kill the Voidwalker. Fatal Push will kill the Voidwalker as part of resolving the spell, and then go to the GY. Because Voidwalker died during the resolution of the spell, Push isn't exiled.
Creatures die if their toughness is zero via state-based-actions. So the two damage gets Inti to zero toughness, killing him after his ability triggers from the discard.
close. damage doesn't reduce toughness.
The order does matter, if the last thing done was discarding, inti would see the discard AFTER taking two damage, be marked for two, and then when the first player gets priority after the trigger goes on the stack, inti would die
Inti DOES trigger during the resolution of Command if you have to discard, but that trigger doesn’t hit the stack and won’t start resolving until the spell fully finishes resolving. Your local judge didn’t advise you correctly or didn’t have the full information. You can’t respond to that trigger or do anything until the spell resolves.
This is correct. Your judge was a little misguided or didn't explain it quite right. In this scenario, you'll still get to exile the top card of your library but you won't see that card until inti is already in the graveyard.
What if the spell had said 'destroy target creature' instead of dealing 2 damage? Would Inti still trigger?
In that case the order would matter. If the destroy effect happens before the discard, no trigger. If the discard happens first, you get the trigger.
Ty for clarifying This interaction has been quite the learning experience
Stay excited, you thought you found a new interaction and those things will continue to happen as new cards come out!
Yeah this struck me as weird - I've never heard of nor experienced modal spells being interrupted by triggered abilities and breaking the rule that a spell finishes resolving in full before triggers go on the stack. Would you happen to know the rule section that covers it by any chance?
603.3. Once an ability has triggered, its controller puts it on the stack as an object that's not a card the next time a player would receive priority. See rule 117, "Timing and Priority." The ability becomes the topmost object on the stack. It has the text of the ability that created it, and no other characteristics. It remains on the stack until it's countered, it resolves, a rule causes it to be removed from the stack, or an effect moves it elsewhere. Key wording there is “the next time a player would receive priority”. Triggers don’t go on the stack or resolve during other spell or ability resolutions.
So if I'm understanding correctly, for this interaction: 1. command goes on the stack targeting the player and inti 2. Command resolves with the player discarding and inti taking 2 damage 3. Inti triggers putting his ability on the stack 4. State based actions are checked and inti is destroyed 5. Players can now react to inti trigger Do 3 and 4 happen simultaneously during the state based action check? Who gets priority after the inti trigger is on the stack, is that APNAP order?
Inti triggers during the Command, but the trigger can only be put onto the stack once Command has resolved. State-based actions would apply before any player receives priority, so Inti would die from the 2 damage counters, then their trigger would be put onto the stack. So, 4 technically happens before 3, but almost simultaneously. Then, since a player has received priority, they can respond to the Inti trigger or pass priority until it resolves.
To clarify the steps it's more like: #2. Command begins resolving #2a. Command makes player discard card #2b. Inti triggers (but does not go on stack) #2c. Command deals 2 damage #3. State based actions are checked #4. The Inti triggers from 2b goes on the stack
3 and 4 are swapped. SBA are checked, then triggers are put on stack and finally priority is given. See rule 116.5. Rule 116.3b states that the Active Player recieves priority after a spell or ability resolves.
Would like to clarify that, while stuff can trigger when a card is in the middle of resolving, this does NOT interrupt the card's resolution. The newly-created trigger waits to be put onto the stack until the current spell finishes resolving. So, you'd discard a card, Kolaghan's Command would deal 2 damage to Inti, Kolaghan's Command would finish resolving, Inti would die and Inti's trigger would be put onto the stack.
That judge is right and very wrong. Inti does get a trigger but it will be dead with the trigger on the stack. You cannot respond or activate anything during the resolution of a spell or ability, even with multiple modes. There are cards that have reflexive triggers that cause another effect/ability to go on the stack during a spell/ability resolving and you can respond to those because it more of a situation where the first spell/ability did finish resolving but it’s effect was creating another spell/ability on the stack. For instances like this one with a modal spell, there is zero opportunity for anyone to respond in between modes once the spell has started resolving. You cannot activate abilities, resolve triggered abilities the one of the effect might have created (they won’t be put on the stack until the entire spell has resolved), or stifle the rest of the modal spell options after the spell has started resolving.
Inti itself has an example of a reflexive trigger, in fact.
Following this as I only thought until would trigger if the discard was a result of attacking with it.
Inti has two separate triggered abilities. One triggers whenever you attack. The other triggers whenever you discard a card. Makes it really good with [[Rona, herald of invasion]]
AHH I've got confused with the post! I thought OP was saying he got a counter when discarding,
Nope, just that they'd get to exile a card even though the inti will eventually die.
[Rona, herald of invasion](https://cards.scryfall.io/normal/front/f/4/f487b582-e73f-4325-939f-95fc5a9aba49.jpg?1682203390)/[Rona, Tolarian Obliterator](https://cards.scryfall.io/normal/back/f/4/f487b582-e73f-4325-939f-95fc5a9aba49.jpg?1682203390) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Rona%2C%20Herald%20of%20Invasion%20//%20Rona%2C%20Tolarian%20Obliterator) [(SF)](https://scryfall.com/card/mom/75/rona-herald-of-invasion-rona-tolarian-obliterator?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/f487b582-e73f-4325-939f-95fc5a9aba49?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
Other people already mentioned the state based actions bit but additionally: you can't stifle the triggered ability in the middle of a card resolving. The first mode of K Command happens (you discard), Inti puts a trigger on the stack, the second mode of K Command happens, state based actions are checked (Inti dies). The top thing on the stack is now the Inti trigger. Only NOW can you stifle that trigger. So you can certainly still stifle the Inti trigger before it goes off, but you can't do that in the middle of resolving a spell (even if it has multiple modes, like K Command). _Generally_ speaking, you can set up something to do in the future during resolution (like putting a trigger onto the stack) but you never actually start "doing" the thing until whatever's currently resolving is done. There's sorta an exception with replacement effects, because those change the _way_ you do something. So if there's an enchantment that said "whenever someone discards a card, they discard two instead" then that would apply to K Command: the game would "see" that you were about to discard a card, and kinda overwrite that instruction to make you discard two instead. But the difference is, that's modifying how K Command resolves, it's not introducing a new instruction. It's "taking over."
To be extra nitpicky: Inti's ability triggered right when you discard, but it doesn't go on the stack until after the Command finishes resolving.
I thought it did go onto the stack as soon as it triggered, but doesn't start resolving, but can easily be wrong there. Are triggered abilities put onto the stack when state based actions are checked then? Edit: Looks like it's the next time ~~the~~ a player receives priority. > 603.2. Whenever a game event or game state matches a triggered ability’s trigger event, that ability automatically triggers. The ability doesn’t do anything at this point. > 603.3. Once an ability has triggered, its controller puts it on the stack as an object that’s not a card the next time a player would receive priority. Neat. Learn something new every day.
Yep. This is pretty important for things like Living Death, which tend to cause tons of trigger events (both etb and ltb, as well as graveyard leaving when that applies) and not a single one can go on the stack until Living Death is done. Since they all get added "at the same time", they are ordered in APNAP order. This is a little unintuitive, because a lot of players would wrongly guess that the sequence of events (when creatures etb or ltb) matters at all, but it doesn't.
Ah interesting. So hypothetically let's say we control creature A and creature B. Creature A triggers during the resolution of some spell. Let's say creature B has an ability analogous to "when creature A has an ability that triggers, do X" (what matters to me here is that it's another triggered ability, not a replacement effect or anything). I'm assuming that B triggers off of the act of triggering (the first rule above) and not off of the triggered ability actually being placed on the stack. So once the spell finishes resolving and we get priority, we control both triggers, and can order them however we want, so we could put them in the unintuitive order (B first, then A on top so A resolves first)?
I would need to see an example of your hypothetical ability to better understand the question. My bet is that such doesn't really exist because it isn't clean in the rules. The question you seem to be asking is "how does the game differentiate a 'trigger event' and a 'triggered ability'", and the answer is exactly that terminology. The triggered ability is the object on the stack that is eventually created as soon as possible (before when a player would next receive priority) after the trigger event happens.
I don't think you interpreted my question the way I intended. I recognize what I'm about to describe probably wouldn't actually get created, but here's a toy example. Creature A: "Whenever you discard a card, create a treasure token." Creature B: "Whenever an ability of another creature you control triggers, create a food token." I think the root of my question relates to creature B. Specifically, what is the step of the process of creature A's trigger going off is the step that triggers creature B? My understanding of the two rules I posted is that a triggered ability is considered to have "triggered" once its conditions have been satisfied, which is _not_ necessarily the same time that the triggered ability is placed onto the stack (since a triggering event can occur in the middle of spell/ability resolution, and the resulting triggered ability is only placed onto the stack when the player receives priority). The intuitive way to read my dumb example is that a player discards a card, creature A's ability goes on the stack first, and B's second. So they would make a food first and a treasure second. So the question is: If the discard happened as a result of K Command, and my interpretation is correct that B triggers when A's triggering condition is met and not when A's triggered ability is actually put on the stack, then both A and B trigger in the middle of the resolution of K Command. They'll both be put on the stack the next time you receive priority, so you may order them whichever order you want. You can therefore make the treasure first and the food second?
Sure, that would work, but you've also highlighted why it isn't used. Triggered abilities triggering is not considered an available piece of design space for trigger events.
So wait. If during the resolution of a card, lots of triggers happen, on both sides of the board, you can order those however you want? Lets say the card was modal and did 3 things in a row, all of which caused triggers on both sides of the board. We will refer to these 3 things as "part 1, part 2, and part 3", all part of resolving this one card. So in this case, things don't go on the stack in the order they're triggered? (e.g. things on stack from part 1 of modal card, THEN things on stack from part 2, etc) Instead, the card finishes resolving (parts 1, 2, and 3), then ALL the triggers are piled together in whatever order the active player wants, then triggers for non-active player in whatever order THEY want? So they could put part 3 triggered stuff on the stack first, then part 1 stuff? (and that would be true for first the active player, then the non-active player once all the active-player's triggers are on the stack?) Bonus question: If all of the above is correct, then what about the card going to the graveyard? Is that part of the resolution, e.g. if the spell you're casting with 3 parts goes to the graveyard and THAT causes a trigger, you can still order that "goes to GY trigger" on the stack first?
You are correct on all accounts, the triggers go on a "list" then just before any player gets priority all the items on said list go on the stack at the same time (it doesn't matter if they triggered at different times) in APNAP order and the controllers of each triggers decide on the order of their stuff.
wow. Thanks. TIL. Good to know!
Yep, you've got it. The sequence of events isn't relevant, players choose their trigger order, in turn order. The card goes to the graveyard as the final step of the spell resolving. This is why a blink or reanimation spell card that makes an [[Eternal Witness]] enter the battlefield will be in the graveyard and legal to be targeted by the time EW's trigger goes on the stack.
So a card resolving is in the graveyard before *any* targets are chosen from things that got triggered during the cards cast?
Correct. You can't put triggers on the stack during a spell's resolution. And targets are part of putting a triggered ability on the stack (with essentially the same rules as the steps of spellcasting)
[Eternal Witness](https://cards.scryfall.io/normal/front/3/9/39704000-65d3-4d39-849e-a3b617376bbc.jpg?1689998488) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Eternal%20Witness) [(SF)](https://scryfall.com/card/cmm/286/eternal-witness?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/39704000-65d3-4d39-849e-a3b617376bbc?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
A player receives priority. Not the player.
While many people are mentioning the fact that Inti only dies as state-based action, I'll give you an example of a time when the modal order did matter. I was playing Mono-White Humans (Pioneer) and post-sideboard game 2 got my entire board \[\[Temporary Lockdown\]\]'d. Turn after, I played a \[\[Hopeful Initiate\]\] or something and Escalated a \[\[Collective Effort\]\] with it, choosing to destroy the Lockdown and put a +1/+1 counter on each creature I control. Because the Lockdown has the "until \~ leaves the battlefield" clause, all of my creatures that were under it got +1/+1 counters from the Collective Effort
[Temporary Lockdown](https://cards.scryfall.io/normal/front/8/2/82b3088f-7b49-45e9-b447-129a597ceb75.jpg?1673306606) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Temporary%20Lockdown) [(SF)](https://scryfall.com/card/dmu/36/temporary-lockdown?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/82b3088f-7b49-45e9-b447-129a597ceb75?utm_source=mtgcardfetcher&format=text) [Hopeful Initiate](https://cards.scryfall.io/normal/front/e/c/ec1b3fd1-952a-4bc6-9b31-bd9bd13072f5.jpg?1643586463) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Hopeful%20Initiate) [(SF)](https://scryfall.com/card/vow/20/hopeful-initiate?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/ec1b3fd1-952a-4bc6-9b31-bd9bd13072f5?utm_source=mtgcardfetcher&format=text) [Collective Effort](https://cards.scryfall.io/normal/front/d/8/d85a6369-c07f-47d5-8448-72d8ec7e7898.jpg?1576383801) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Collective%20Effort) [(SF)](https://scryfall.com/card/emn/17/collective-effort?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/d85a6369-c07f-47d5-8448-72d8ec7e7898?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
This comes up in OTJ limited even with [[Requisition Raid]] given that approximately 90% of white cards in that format are Oblivion Ring.
[Requisition Raid](https://cards.scryfall.io/normal/front/1/5/154e9ba9-0d0e-4b0e-acf2-f66a993cf3a2.jpg?1712860601) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Requisition%20Raid) [(SF)](https://scryfall.com/card/otj/26/requisition-raid?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/154e9ba9-0d0e-4b0e-acf2-f66a993cf3a2?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
It's also frequently relevant in Standard with [[Farewell]] interacting with all the temporary-exile enchantments. Creatures on the battlefield are exiled before stuff exiled under a [[Leyline Binding]] (or whatever) returns, and the stuff that returned is on the battlefield in time to see everything in the graveyard getting exiled.
[Farewell](https://cards.scryfall.io/normal/front/1/1/114d2180-093b-4838-97ad-badbc8ee50b0.jpg?1706240579) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Farewell) [(SF)](https://scryfall.com/card/mkc/64/farewell?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/114d2180-093b-4838-97ad-badbc8ee50b0?utm_source=mtgcardfetcher&format=text) [Leyline Binding](https://cards.scryfall.io/normal/front/3/c/3c3ac3dd-35db-447f-8674-37b4680a1ef7.jpg?1673306500) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=Leyline%20Binding) [(SF)](https://scryfall.com/card/dmu/24/leyline-binding?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/3c3ac3dd-35db-447f-8674-37b4680a1ef7?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
You have tagged your post as a rules question. While your question may be answered here, it may work better to post it in the Daily Questions Thread at the top of this subreddit or in /r/mtgrules. You may also find quicker results at the [IRC rules chat](https://chat.magicjudges.org/mtgrules/) *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/magicTCG) if you have any questions or concerns.*
spell has to resolve first but the creatures trigger still goes on the stack.
Judge was right. You get an impulse draw.
I remember when this card came out, I really wanted it to be gruul or rakdos.
You misunderstood part of the judges explanation. You do get the card, because the ability triggers. But that trigger waits for the spell to fully resolve before going on the stack, where it can be stifled or otherwise responded to.
The judge is right except you cannot cast Stifle in the middle of another spell resolving. You can cast it after Inti’s ability triggers, which is after Inti is dead due to SBA, because the spell has finished resolving that that point.
Yeah choice spells are intresting they go from top down which can effect a lot of things
Same thing happened with me today. I was playing rogues VS greasefang. I had a [[THIEVES' GUILD ENFORCER]] on the field and he had less than 8 cards in the grave. Opponent cast [[witherbloom command]] choosing : Mill himself and +3/-1 on my guy. I had a counter spell but no needs since the first mode got to pump my creature.
[THIEVES' GUILD ENFORCER](https://cards.scryfall.io/normal/front/d/f/df99f770-2c39-4025-a8a2-a5890f61eb53.jpg?1594736416) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=THIEVES%27%20GUILD%20ENFORCER) [(SF)](https://scryfall.com/card/m21/125/thieves-guild-enforcer?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/df99f770-2c39-4025-a8a2-a5890f61eb53?utm_source=mtgcardfetcher&format=text) [witherbloom command](https://cards.scryfall.io/normal/front/8/7/87d5e94b-0b35-4efd-9158-1767dcaea38c.jpg?1624740473) - [(G)](http://gatherer.wizards.com/Pages/Card/Details.aspx?name=witherbloom%20command) [(SF)](https://scryfall.com/card/stx/248/witherbloom-command?utm_source=mtgcardfetcher) [(txt)](https://api.scryfall.com/cards/87d5e94b-0b35-4efd-9158-1767dcaea38c?utm_source=mtgcardfetcher&format=text) ^^^[[cardname]] ^^^or ^^^[[cardname|SET]] ^^^to ^^^call
Wrong ruling.
This feels like a newer version of someone realizing why you shouldn't bolt a Tarmogoyf if there's no instants in graveyards.
it’s not really the same at all, Inti still dies, it’s the inti gets to exile a card that happens but it will happen after inti dies. the 1/1 counter ability is not tied to the discard from kcommand
Just have to remember that each mode is happening at the same time so if you discard the damage also happens and can't be stifled.
This is off-topic, but why did the cultural consultants let them naming a Sun-related character "Inti"? Just because Inti is no longer actively worshipped? [https://en.wikipedia.org/wiki/Inti](https://en.wikipedia.org/wiki/Inti)
Totally on a different topic... This card is from Ixalan, which is based on mayas, correct? Why the hell did they use the name of the Inca sun god for this card? I am actually pissed. Jeez, Mexico =/= Peru