If I attack with a {advent of the wurm} with {boon satyr} on it, which makes it a 9/7, and an opponent blocks with a {experiment one} with 3 +1 +1 counters on it which makes it a 4/4 and also blocks with a {fleecemane lion}. If he removes the counters from {experiment one} to regenerate, won't my advent live and both his die and the rest trample over?
Quote from: Blazingblevins on August 08, 2014, 01:49:19 AM
If I attack with a {advent of the wurm} with {boon satyr} on it, which makes it a 9/7, and an opponent blocks with a {experiment one} with 3 +1 +1 counters on it which makes it a 4/4 and also blocks with a {fleecemane lion}. If he removes the counters from {experiment one} to regenerate, won't my advent live and both his die and the rest trample over?
From the comprehensive rules:
510.1. First, the active player announces how each attacking creature assigns its combat damage, then the defending player announces how each blocking creature assigns its combat damage. This turn-based action doesn't use the stack.
510.2. Second, all combat damage that's been assigned is dealt simultaneously. This turn-based action doesn't use the stack. No player has the chance to cast spells or activate abilities between the time combat damage is assigned and the time it's dealt.
If he doesn't use the regenerative ability before damage is assigned, he will not have a chance to regenerate his creature before it dies.
Well what happens if he blocks then, says regen before I assign? Or in my case he blocked, then waited for me to assign.
And then he regenerated after damage was assigned
If he blocks and pays for regeneration before damage, your wurm lives, lion dies, he takes 4 due to trample.
If he waits for damage and try's to regen afterwards, it's too late, everything dies, and he takes 2 due to trample.
Ok. Thanks
just you know, after you assign damage, he still has a chance to regen and stuff. then you go to damage. just make sure you take steps slow so he has a chance to respond
Quote from: particle on August 08, 2014, 11:38:02 AM
just you know, after you assign damage, he still has a chance to regen and stuff. then you go to damage. just make sure you take steps slow so he has a chance to respond
There is a difference between damage assignment and assign damage. Damage assignment occurs after blockers are declared and only indicates the order you will assign damage to his creatures. After damage assignment, players will receive priority, where you can use regeneration effects. Assigning damage occurs in either first strike or normal damage phases (or both) and involves creatures and players involved actually receiving damage. Once damage has been assigned, state based actions are checked and it is too late to use regeneration effects because the state based actions don't use the stack and so can't be responded to.
Quote from: particle on August 08, 2014, 11:38:02 AM
just you know, after you assign damage, he still has a chance to regen and stuff. then you go to damage. just make sure you take steps slow so he has a chance to respond
This is absolutely false.
Pleeb, you're mixing up Damage Assignment with Damage Assignment Order, which is the order the attacker has to eat through the creatures before hitting the next one -
509 - Declare Blockers Step
509.2. Second, for each attacking creature that's become blocked, the active player announces that creature's damage assignment order, which consists of the creatures blocking it in an order of that player's choice. (During the combat damage step, an attacking creature can't assign combat damage to a creature that's blocking it unless each creature ahead of that blocking creature in its order is assigned lethal damage.) This turn-based action doesn't use the stack.
510 - Combat Damage Step
510.1. First, the active player announces how each attacking creature assigns its combat damage, then the defending player announces how each blocking creature assigns its combat damage. This turn-based action doesn't use the stack. A...
510.2. Second, all combat damage that's been assigned is dealt simultaneously. This turn-based action doesn't use the stack. No player has the chance to cast spells or activate abilities between the time combat damage is assigned and the time it's dealt. This is a change from previous rules
You can cast spells and activate abilities once you know the order that damage will be dealt in, but not after you know exactly how damage is assigned.