Client passes normal damage priority during first strike if first strike creatures removed before damage
This report is in relation to passing priority after first strike damage after the first strike creatures are removed.
The client is Mac OS X.
This happened during the final match of the draft on 9/1 at 12:57 am. I've attached the log files which I've just exported about 15 hours after the match. It occurred during my attack phase on turn 5.
How to reproduce:
- Active player (AP) attacks with multiple creatures, including one with first strike. AP has interaction available with a legal target and mana to cast it. Non-active player (NAP) also has removal they can cast to remove the creature with first strike.
- NAP assigns blocks and passes priority to AP.
- At this point, the client correctly shows the active player they can pass priority before first-strike damage. The active player does so.
- The non-active player receives priority before first-strike damage. NAP casts their removal on the first-strike creature before it does damage. The AP will now have no attacking creatures with first-strike.
- The client returns priority to the active player. At this point, the client says, "Pass to first strike damage."
- When clicking the button to pass priority, the client goes directly to normal damage, does not give either player priority, and creatures exchange damage.
What should happen:
What should happen is that in step 6, when the AP clicks to pass priority to first-strike damage, no damage should happen since there are no creatures with first-strike and the client should instead proceed to give the active player priority before normal combat damage.
Thank you for your help. Please let me know if there is anything else I can provide.
Tony#18444
shared this idea
-
Tony#18444
commented
Thank you for your response. I completely agree that this is how combat should proceed.
Given that, I would think that in step 5 above when priority was passed back to me after my creature was destroyed, the client should display "Pass to damage" instead of "Pass to first strike damage."
-
Rezzahan#77802
commented
The second combat damage step is only created if a creature with first strike or double strike is in combat as the first combat damage step begins. NAP removed the only creature with such an ability, so no additional combat step happens.
510.4. If at least one attacking or blocking creature has first strike (see rule 702.7) or double strike (see
rule 702.4) as the combat damage step begins, the only creatures that assign combat damage in that
step are those with first strike or double strike. After that step, instead of proceeding to the end of
combat step, the phase gets a second combat damage step. The only creatures that assign combat
damage in that step are the remaining attackers and blockers that had neither first strike nor double
strike as the first combat damage step began, as well as the remaining attackers and blockers that
currently have double strike. After that step, the phase proceeds to the end of combat step.