If I have a Plague Spitter, Prodigal Sorcerer or any other Tim creature, and the creature's ability is on the stack, is it then too late to profit by giving that creature lifelink or deathtouch in response, before the Tim ability resolves?
ie. In response to Plague Spitter's upkeep trigger, I cast Necrobite on it. Necrobite resolves, but since the Spitter's ability was already on the stack, I think that the damage it deals is non-deathtouch damage. Correct?
Thanks.
Private Mod Note
():
Rollback Post to RevisionRollBack
Master of inaccurate, non-thought-out baseless and naive statements.
I like baby fowl.
112.7a Once activated or triggered, an ability exists on the stack independently of its source. Destruction or removal of the source after that time won't affect the ability. Note that some abilities cause a source to do something (for example, "Prodigal Sorcerer deals 1 damage to target creature or player") rather than the ability doing anything directly. In these cases, any activated or triggered ability that references information about the source because the effect needs to be divided checks that information when the ability is put onto the stack. Otherwise, it will check that information when it resolves. In both instances, if the source is no longer in the zone it's expected to be in at that time, its last known information is used. The source can still perform the action even though it no longer exists.
So, if I'm reading that right, it DOES work to give the Tim creature deathtouch or lifelink, EVEN AFTER its ability is on the stack. If it can, the game checks the source of the damage as the ability resolves.
Also if I'm reading this right, it would even work if I...
1) Put the Tim ability on the stack,
2) Gave the creature Deathtouch or Lifelink,
3) Sacrificed, destroyed or bounced the creature.
4) The Tim ability then resolves, and since the "last known information" of the creature was to have deathtouch or lifelink, the damage is deathtouch or lifelink damage.
Private Mod Note
():
Rollback Post to RevisionRollBack
Master of inaccurate, non-thought-out baseless and naive statements.
I like baby fowl.
That's correct, you did find the answer and the relevant rule yourself.
Private Mod Note
():
Rollback Post to RevisionRollBack
I'm a former judge (lapsed), who keeps up to date on rules and policy. Keep in mind that judges' answers aren't necessarily more valid than those of people who aren't judges; what matters is we can quote the rules to back up our answers. When in doubt, ask for such quotes.
Also if I'm reading this right, it would even work if I...
1) Put the Tim ability on the stack,
2) Gave the creature Deathtouch or Lifelink,
3) Sacrificed, destroyed or bounced the creature.
4) The Tim ability then resolves, and since the "last known information" of the creature was to have deathtouch or lifelink, the damage is deathtouch or lifelink damage.
Only if you let 2) resolve before moving on to 3).
An important thing to notice, that noone has mentioned yet though: Deathtouch only works with COMBAT Damage. These abilities just deal Damage, not combat damage.
I'm on mobile right now, so please excuse me when i just say: see rule 119.2 and 702.2b for the relevant damage/deathtouch rules
An important thing to notice, that noone has mentioned yet though: Deathtouch only works with COMBAT Damage. These abilities just deal Damage, not combat damage.
I'm on mobile right now, so please excuse me when i just say: see rule 119.2 and 702.2b for the relevant damage/deathtouch rules
Deathtouch affects all damage, not just combat damage, by a source with that ability. C.R. 702.2b is not the entire meaning of deathtouch and merely modifies what combat damage means when deathtouch is involved. A creature with greater than 0 toughness that was dealt damage (not just combat damage) by a source with deathtouch will be destroyed as a state-based action (C.R. 704.5h; see also C.R. 702.2c).
Offtopic: Learned something again. When i check the comprehensive rules, read all rules that contain the keyword, not just the shiny one holding up a sign that says deathtouch, misinterpreting it and shamefully crashing headfirst into the wall.
ie. In response to Plague Spitter's upkeep trigger, I cast Necrobite on it. Necrobite resolves, but since the Spitter's ability was already on the stack, I think that the damage it deals is non-deathtouch damage. Correct?
Thanks.
I like baby fowl.
112.7a Once activated or triggered, an ability exists on the stack independently of its source. Destruction or removal of the source after that time won't affect the ability. Note that some abilities cause a source to do something (for example, "Prodigal Sorcerer deals 1 damage to target creature or player") rather than the ability doing anything directly. In these cases, any activated or triggered ability that references information about the source because the effect needs to be divided checks that information when the ability is put onto the stack. Otherwise, it will check that information when it resolves. In both instances, if the source is no longer in the zone it's expected to be in at that time, its last known information is used. The source can still perform the action even though it no longer exists.
So, if I'm reading that right, it DOES work to give the Tim creature deathtouch or lifelink, EVEN AFTER its ability is on the stack. If it can, the game checks the source of the damage as the ability resolves.
Also if I'm reading this right, it would even work if I...
1) Put the Tim ability on the stack,
2) Gave the creature Deathtouch or Lifelink,
3) Sacrificed, destroyed or bounced the creature.
4) The Tim ability then resolves, and since the "last known information" of the creature was to have deathtouch or lifelink, the damage is deathtouch or lifelink damage.
I like baby fowl.
Only if you let 2) resolve before moving on to 3).
An important thing to notice, that noone has mentioned yet though: Deathtouch only works with COMBAT Damage. These abilities just deal Damage, not combat damage.I'm on mobile right now, so please excuse me when i just say: see rule 119.2 and 702.2b for the relevant damage/deathtouch rules
Edit:
I stand corrected by #7
Deathtouch affects all damage, not just combat damage, by a source with that ability. C.R. 702.2b is not the entire meaning of deathtouch and merely modifies what combat damage means when deathtouch is involved. A creature with greater than 0 toughness that was dealt damage (not just combat damage) by a source with deathtouch will be destroyed as a state-based action (C.R. 704.5h; see also C.R. 702.2c).
Offtopic: Learned something again. When i check the comprehensive rules, read all rules that contain the keyword, not just the shiny one holding up a sign that says deathtouch, misinterpreting it and shamefully crashing headfirst into the wall.