Mixing
+1/+1 counter on a dying creature
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I have an attacking 4/4 creature blocked by an Ajani's Pridemate and a Bishop's Soldier.
Is the attacking order relevant? I.e., does it make a difference to the outcome of the fight whether I attack the Pridemate first or not?
Will the Pridemate die, or will the lifelink of the other creature grant it a +1/+1 counter, ensuring it survives the turn?
Thanks!
magic-the-gathering
asked 1 hour ago
anon
1444
add a comment |Â
up vote
1
down vote
favorite
I have an attacking 4/4 creature blocked by an Ajani's Pridemate and a Bishop's Soldier.
Is the attacking order relevant? I.e., does it make a difference to the outcome of the fight whether I attack the Pridemate first or not?
Will the Pridemate die, or will the lifelink of the other creature grant it a +1/+1 counter, ensuring it survives the turn?
Thanks!
magic-the-gathering
asked 1 hour ago
anon
1444
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have an attacking 4/4 creature blocked by an Ajani's Pridemate and a Bishop's Soldier.
Is the attacking order relevant? I.e., does it make a difference to the outcome of the fight whether I attack the Pridemate first or not?
Will the Pridemate die, or will the lifelink of the other creature grant it a +1/+1 counter, ensuring it survives the turn?
Thanks!
magic-the-gathering
asked 1 hour ago
anon
1444
I have an attacking 4/4 creature blocked by an Ajani's Pridemate and a Bishop's Soldier.
Is the attacking order relevant? I.e., does it make a difference to the outcome of the fight whether I attack the Pridemate first or not?
Will the Pridemate die, or will the lifelink of the other creature grant it a +1/+1 counter, ensuring it survives the turn?
Thanks!
magic-the-gathering
magic-the-gathering
asked 1 hour ago
anon
1444
asked 1 hour ago
anon
1444
asked 1 hour ago
anon
1444
asked 1 hour ago
anon
1444
asked 1 hour ago
anon
1444
1444
add a comment |Â
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
3
down vote
accepted
The order in which you assign damage does not matter here, and the Pridemate will die before it gets the counter from the Bishops Soldier lifegain.
Note that you do not attack individual creatures - you attack players and planeswalkers only. You probably meant the right thing though, namely that you can determine the order in which your attacking creature assigns damage to the blocking creatures. Just remember not to confuse the two things, as it may confuse others also.
508.1b If the defending player controls any planeswalkers, or the game allows the active player to attack multiple other players, the active player announces which player or planeswalker each of the chosen creatures is attacking.
Unless first strike or double strike is involved, all combat damage is dealt simultaneously, so if the attacking creature has enough power to deal lethal damage to all blockers, the order of blockers does not matter,
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 player assigns a creature’s combat damage according to the following rules:
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.
As for your second question: You gain life from Bishop's Soldier as soon as it deals damage, but Pridemate's ability is a triggered ability, so it does not immediately take effect. It only goes on the stack the next time a player would gain priority, i.e. the right to cast spells and activate abilities:
510.3. Third, the active player gets priority. (See rule 116, “Timing and Priority.â€Â)
510.3a Any abilities that triggered on damage being dealt or while state-based actions are performed afterward are put onto the stack before the active player gets priority; the order in which they triggered doesn’t matter. (See rule 603, “Handling Triggered Abilities.â€Â)
Only when Pridemate's ability would come to resolve would it get the +1/+1 counter. However, by that time it's already moved to the graveyard because it received lethal damage.
answered 59 mins ago
Hackworth
23.1k259107
add a comment |Â
up vote
2
down vote
- There is no attacking "first". All damage is done simultaneously.
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 player assigns a creature’s combat damage according to the following rules:
510.1a Each attacking creature and each blocking creature assigns combat damage equal to its power. Creatures that would assign 0 or less damage this way don’t assign combat damage at all.
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.
So what you are thinking of as an "attacking order" is actually just damage assignment order. You need to assign lethal damage to a blocking creature before you can assign more to the other blocker; but this is not an order that damage will be dealt in.
- The Pridemate will die because its ability is a triggered ability. You gain life at the same exact time that all damage is done. This triggers the Pridemate's ability, but that trigger doesn't go on the stack to resolve until state-based actions are checked. The Pridemate will die when state-based actions are checked as a result of having too much damage.
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.
answered 1 hour ago
GendoIkari
38.8k385145
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
The order in which you assign damage does not matter here, and the Pridemate will die before it gets the counter from the Bishops Soldier lifegain.
Note that you do not attack individual creatures - you attack players and planeswalkers only. You probably meant the right thing though, namely that you can determine the order in which your attacking creature assigns damage to the blocking creatures. Just remember not to confuse the two things, as it may confuse others also.
508.1b If the defending player controls any planeswalkers, or the game allows the active player to attack multiple other players, the active player announces which player or planeswalker each of the chosen creatures is attacking.
Unless first strike or double strike is involved, all combat damage is dealt simultaneously, so if the attacking creature has enough power to deal lethal damage to all blockers, the order of blockers does not matter,
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 player assigns a creature’s combat damage according to the following rules:
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.
As for your second question: You gain life from Bishop's Soldier as soon as it deals damage, but Pridemate's ability is a triggered ability, so it does not immediately take effect. It only goes on the stack the next time a player would gain priority, i.e. the right to cast spells and activate abilities:
510.3. Third, the active player gets priority. (See rule 116, “Timing and Priority.â€Â)
510.3a Any abilities that triggered on damage being dealt or while state-based actions are performed afterward are put onto the stack before the active player gets priority; the order in which they triggered doesn’t matter. (See rule 603, “Handling Triggered Abilities.â€Â)
Only when Pridemate's ability would come to resolve would it get the +1/+1 counter. However, by that time it's already moved to the graveyard because it received lethal damage.
answered 59 mins ago
Hackworth
23.1k259107
add a comment |Â
up vote
3
down vote
accepted
The order in which you assign damage does not matter here, and the Pridemate will die before it gets the counter from the Bishops Soldier lifegain.
Note that you do not attack individual creatures - you attack players and planeswalkers only. You probably meant the right thing though, namely that you can determine the order in which your attacking creature assigns damage to the blocking creatures. Just remember not to confuse the two things, as it may confuse others also.
508.1b If the defending player controls any planeswalkers, or the game allows the active player to attack multiple other players, the active player announces which player or planeswalker each of the chosen creatures is attacking.
Unless first strike or double strike is involved, all combat damage is dealt simultaneously, so if the attacking creature has enough power to deal lethal damage to all blockers, the order of blockers does not matter,
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 player assigns a creature’s combat damage according to the following rules:
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.
As for your second question: You gain life from Bishop's Soldier as soon as it deals damage, but Pridemate's ability is a triggered ability, so it does not immediately take effect. It only goes on the stack the next time a player would gain priority, i.e. the right to cast spells and activate abilities:
510.3. Third, the active player gets priority. (See rule 116, “Timing and Priority.â€Â)
510.3a Any abilities that triggered on damage being dealt or while state-based actions are performed afterward are put onto the stack before the active player gets priority; the order in which they triggered doesn’t matter. (See rule 603, “Handling Triggered Abilities.â€Â)
Only when Pridemate's ability would come to resolve would it get the +1/+1 counter. However, by that time it's already moved to the graveyard because it received lethal damage.
answered 59 mins ago
Hackworth
23.1k259107
add a comment |Â
up vote
3
down vote
accepted
up vote
3
down vote
accepted
The order in which you assign damage does not matter here, and the Pridemate will die before it gets the counter from the Bishops Soldier lifegain.
Note that you do not attack individual creatures - you attack players and planeswalkers only. You probably meant the right thing though, namely that you can determine the order in which your attacking creature assigns damage to the blocking creatures. Just remember not to confuse the two things, as it may confuse others also.
508.1b If the defending player controls any planeswalkers, or the game allows the active player to attack multiple other players, the active player announces which player or planeswalker each of the chosen creatures is attacking.
Unless first strike or double strike is involved, all combat damage is dealt simultaneously, so if the attacking creature has enough power to deal lethal damage to all blockers, the order of blockers does not matter,
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 player assigns a creature’s combat damage according to the following rules:
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.
As for your second question: You gain life from Bishop's Soldier as soon as it deals damage, but Pridemate's ability is a triggered ability, so it does not immediately take effect. It only goes on the stack the next time a player would gain priority, i.e. the right to cast spells and activate abilities:
510.3. Third, the active player gets priority. (See rule 116, “Timing and Priority.â€Â)
510.3a Any abilities that triggered on damage being dealt or while state-based actions are performed afterward are put onto the stack before the active player gets priority; the order in which they triggered doesn’t matter. (See rule 603, “Handling Triggered Abilities.â€Â)
Only when Pridemate's ability would come to resolve would it get the +1/+1 counter. However, by that time it's already moved to the graveyard because it received lethal damage.
answered 59 mins ago
Hackworth
23.1k259107
The order in which you assign damage does not matter here, and the Pridemate will die before it gets the counter from the Bishops Soldier lifegain.
Note that you do not attack individual creatures - you attack players and planeswalkers only. You probably meant the right thing though, namely that you can determine the order in which your attacking creature assigns damage to the blocking creatures. Just remember not to confuse the two things, as it may confuse others also.
508.1b If the defending player controls any planeswalkers, or the game allows the active player to attack multiple other players, the active player announces which player or planeswalker each of the chosen creatures is attacking.
Unless first strike or double strike is involved, all combat damage is dealt simultaneously, so if the attacking creature has enough power to deal lethal damage to all blockers, the order of blockers does not matter,
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 player assigns a creature’s combat damage according to the following rules:
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.
As for your second question: You gain life from Bishop's Soldier as soon as it deals damage, but Pridemate's ability is a triggered ability, so it does not immediately take effect. It only goes on the stack the next time a player would gain priority, i.e. the right to cast spells and activate abilities:
510.3. Third, the active player gets priority. (See rule 116, “Timing and Priority.â€Â)
510.3a Any abilities that triggered on damage being dealt or while state-based actions are performed afterward are put onto the stack before the active player gets priority; the order in which they triggered doesn’t matter. (See rule 603, “Handling Triggered Abilities.â€Â)
Only when Pridemate's ability would come to resolve would it get the +1/+1 counter. However, by that time it's already moved to the graveyard because it received lethal damage.
answered 59 mins ago
Hackworth
23.1k259107
edited 53 mins ago
answered 59 mins ago
Hackworth
23.1k259107
answered 59 mins ago
Hackworth
23.1k259107
answered 59 mins ago
Hackworth
23.1k259107
23.1k259107
add a comment |Â
add a comment |Â
up vote
2
down vote
- There is no attacking "first". All damage is done simultaneously.
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 player assigns a creature’s combat damage according to the following rules:
510.1a Each attacking creature and each blocking creature assigns combat damage equal to its power. Creatures that would assign 0 or less damage this way don’t assign combat damage at all.
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.
So what you are thinking of as an "attacking order" is actually just damage assignment order. You need to assign lethal damage to a blocking creature before you can assign more to the other blocker; but this is not an order that damage will be dealt in.
- The Pridemate will die because its ability is a triggered ability. You gain life at the same exact time that all damage is done. This triggers the Pridemate's ability, but that trigger doesn't go on the stack to resolve until state-based actions are checked. The Pridemate will die when state-based actions are checked as a result of having too much damage.
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.
answered 1 hour ago
GendoIkari
38.8k385145
add a comment |Â
up vote
2
down vote
- There is no attacking "first". All damage is done simultaneously.
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 player assigns a creature’s combat damage according to the following rules:
510.1a Each attacking creature and each blocking creature assigns combat damage equal to its power. Creatures that would assign 0 or less damage this way don’t assign combat damage at all.
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.
So what you are thinking of as an "attacking order" is actually just damage assignment order. You need to assign lethal damage to a blocking creature before you can assign more to the other blocker; but this is not an order that damage will be dealt in.
- The Pridemate will die because its ability is a triggered ability. You gain life at the same exact time that all damage is done. This triggers the Pridemate's ability, but that trigger doesn't go on the stack to resolve until state-based actions are checked. The Pridemate will die when state-based actions are checked as a result of having too much damage.
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.
answered 1 hour ago
GendoIkari
38.8k385145
add a comment |Â
up vote
2
down vote
up vote
2
down vote
- There is no attacking "first". All damage is done simultaneously.
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 player assigns a creature’s combat damage according to the following rules:
510.1a Each attacking creature and each blocking creature assigns combat damage equal to its power. Creatures that would assign 0 or less damage this way don’t assign combat damage at all.
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.
So what you are thinking of as an "attacking order" is actually just damage assignment order. You need to assign lethal damage to a blocking creature before you can assign more to the other blocker; but this is not an order that damage will be dealt in.
- The Pridemate will die because its ability is a triggered ability. You gain life at the same exact time that all damage is done. This triggers the Pridemate's ability, but that trigger doesn't go on the stack to resolve until state-based actions are checked. The Pridemate will die when state-based actions are checked as a result of having too much damage.
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.
answered 1 hour ago
GendoIkari
38.8k385145
- There is no attacking "first". All damage is done simultaneously.
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 player assigns a creature’s combat damage according to the following rules:
510.1a Each attacking creature and each blocking creature assigns combat damage equal to its power. Creatures that would assign 0 or less damage this way don’t assign combat damage at all.
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.
So what you are thinking of as an "attacking order" is actually just damage assignment order. You need to assign lethal damage to a blocking creature before you can assign more to the other blocker; but this is not an order that damage will be dealt in.
- The Pridemate will die because its ability is a triggered ability. You gain life at the same exact time that all damage is done. This triggers the Pridemate's ability, but that trigger doesn't go on the stack to resolve until state-based actions are checked. The Pridemate will die when state-based actions are checked as a result of having too much damage.
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.
answered 1 hour ago
GendoIkari
38.8k385145
answered 1 hour ago
GendoIkari
38.8k385145
answered 1 hour ago
GendoIkari
38.8k385145
answered 1 hour ago
GendoIkari
38.8k385145
38.8k385145
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fboardgames.stackexchange.com%2fquestions%2f43682%2f1-1-counter-on-a-dying-creature%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password