So, Regeneration / Regenerate is an ability that causes a "shield" on the creature to prevent any damage on it. After the damage is done, this shield is gone. Right? If not then the rest won't make sense.
This means that I can put Regenerate on a creature whenever I want. During a Main phase, after Declaring Attack or Defend.
But what if I put regenerate on a creature and then my opponent plays a spell with: "Target cannot be regenerated"
Does this mean I can't play a regenerate spell on the Stack, or won't Regenerate work at all. (since it was activated BEFORE this spell was played)
It doesn't matter when you activate the regenerate ability, it is a replacement effect that states when the creature dies, instead remove all damage from it and tap it. It doesn't actually regenerate until it dies so any spell that says it can't be regenerated will keep it from regenerating regardless of when the ability was activated.
Remember that the creature does not leave play and come back, so no enter the battlefield abilities will trigger. Also if you sacrifice your own creature in response to them dark banishing it it will regenerate because the banishings' "cannot be regenerated clause" is still on the stack but since the creature did not leave play it does not count as a separate object and will be killed be the banishing anyway.
EDIT: Everyone else is correct that sacrificing does not work with regeneration. That was not really the point, was trying to show how regeneration and the stack works but picked a bad example!
It doesn't matter when you activate the regenerate ability, it is a replacement effect that states when the creature dies, instead remove all damage from it and tap it. It doesn't actually regenerate until it dies so any spell that says it can't be regenerated will keep it from regenerating regardless of when the ability was activated.
.
The bolded bit is incorrect. Regenration only prevents destruction which is specifically defined as lethal damage or effects that state they destroy the target. It has no effect on any other means of sending something to the graveyard from the battlefield like a sacrifice effect or a creature having 0 toughness.
Private Mod Note
():
Rollback Post to RevisionRollBack
Every normal man must be tempted, at times, to spit on his hands, hoist the black flag and start slitting throats.
- H.L Mencken
I Became insane with long Intervals of horrible Sanity
All Religion, my friend is simply evolved out of fraud, fear, greed, imagination and poetry.
- Edgar Allan Poe
After the damage is done, this shield is gone. Right?
Right. A regeneration shield remains on a permanent until it does indeed get used to save the creature, or until the end of turn, whichever comes first.
But what if I put regenerate on a creature and then my opponent plays a spell with: "Target cannot be regenerated"
Does this mean I can't play a regenerate spell on the Stack, or won't Regenerate work at all. (since it was activated BEFORE this spell was played)
You can play it, but it won't be of any use. It doesn't matter if the shield was there before or after the killing spell is cast: a 'cannot be regenerated' clause will make the shield not work.
701.12c (...) Effects that say that a permanent can’t be regenerated don’t prevent [regeneration] abilities from being activated or [regeneration] spells from being cast; rather, they prevent regeneration shields from having any effect.
It doesn't matter when you activate the regenerate ability, it is a replacement effect that states when the creature dies, instead remove all damage from it and tap it. It doesn't actually regenerate until it dies so any spell that says it can't be regenerated will keep it from regenerating regardless of when the ability was activated.
Remember that the creature does not leave play and come back, so no enter the battlefield abilities will trigger. Also if you sacrifice your own creature in response to them dark banishing it it will regenerate because the banishings' "cannot be regenerated clause" is still on the stack but since the creature did not leave play it does not count as a separate object and will be killed be the banishing anyway.
If you sacrifice your creature it won't regenerate because regeneration doesn't stop sacrificing only destruction
Here's a much simplified version:
When effects are in play that say you "can" or "must" do X, and it's met with a card that says "you can't do X", can't always wins.
Here's a much simplified version:
When effects are in play that say you "can" or "must" do X, and it's met with a card that says "you can't do X", can't always wins.
The problem with that is it is only mostly true. The most common but not only exception is defender (which rules text is "this creature cannot attack") vs "this creature may attack as though it didn't have defender".
The Golden Rule of Magic applies here. I'm talking specifically about cards that counteract the effects of other cards. Your "as though" example is a perfect illustration of the Golden Rule- the rules say Defenders can't attack, and if you're using a card with Defender that says "as though it didn't have Defender" (probably via some activated ability), the card wins over the rules.
Edit: try using Healing Salve to save one of your creatures from lethal damage when a red "damage can't be prevented" card is in play, see how well that goes over for you.
Another question.
So, Regeneration / Regenerate is an ability that causes a "shield" on the creature to prevent any damage on it. After the damage is done, this shield is gone. Right? If not then the rest won't make sense.
This means that I can put Regenerate on a creature whenever I want. During a Main phase, after Declaring Attack or Defend.
But what if I put regenerate on a creature and then my opponent plays a spell with: "Target cannot be regenerated"
Does this mean I can't play a regenerate spell on the Stack, or won't Regenerate work at all. (since it was activated BEFORE this spell was played)
Thanks for the help
It doesn't matter when you activate the regenerate ability, it is a replacement effect that states when the creature dies, instead remove all damage from it and tap it. It doesn't actually regenerate until it dies so any spell that says it can't be regenerated will keep it from regenerating regardless of when the ability was activated.
Remember that the creature does not leave play and come back, so no enter the battlefield abilities will trigger. Also if you sacrifice your own creature in response to them dark banishing it it will regenerate because the banishings' "cannot be regenerated clause" is still on the stack but since the creature did not leave play it does not count as a separate object and will be killed be the banishing anyway.
EDIT: Everyone else is correct that sacrificing does not work with regeneration. That was not really the point, was trying to show how regeneration and the stack works but picked a bad example!
Thanks for clearing that up
The bolded bit is incorrect. Regenration only prevents destruction which is specifically defined as lethal damage or effects that state they destroy the target. It has no effect on any other means of sending something to the graveyard from the battlefield like a sacrifice effect or a creature having 0 toughness.
- H.L Mencken
I Became insane with long Intervals of horrible Sanity
All Religion, my friend is simply evolved out of fraud, fear, greed, imagination and poetry.
- Edgar Allan Poe
The Crafters' Rules Guru
Correct. The shield is active until end of turn.
You can play it, but it won't be of any use. It doesn't matter if the shield was there before or after the killing spell is cast: a 'cannot be regenerated' clause will make the shield not work.
701.12c (...) Effects that say that a permanent can’t be regenerated don’t prevent [regeneration] abilities from being activated or [regeneration] spells from being cast; rather, they prevent regeneration shields from having any effect.
RULES OF MAGIC :
http://magic.wizards.com/en/game-info/gameplay/rules-and-formats/rules
When effects are in play that say you "can" or "must" do X, and it's met with a card that says "you can't do X", can't always wins.
The problem with that is it is only mostly true. The most common but not only exception is defender (which rules text is "this creature cannot attack") vs "this creature may attack as though it didn't have defender".
Edit: try using Healing Salve to save one of your creatures from lethal damage when a red "damage can't be prevented" card is in play, see how well that goes over for you.