Hi,
both minions chose their strike, then you go to strike resolution, so both strikes are combat ends and both can untap.
and per cardtext, the blocking minion takes damage from Riposte
Best regards
That seems a reasonable response, but what about this section of the rulebook:
"Combat Ends: This effect ends combat immediately. This type of strike is always the first to resolve, even before a strike done with first strike (see First Strike), and it ends combat before other strikes or other strike resolution effects are resolved."
This is essentially the reason why I had this question in the first place, since after choosing strikes, strike resolution phase follows, once one combat ends is resolved, the other one shouldn't, no? Meaning, only one of the combat ends should work, the other one would just be a selected strike that does not get resolved.
And for the riposte section, I have read the card, but my main argument as to why it seems weird to me that it would do damage even against combat ends is because it seems to behave very similarly to any other strike.
"The damage is only dealt if the strike was resolved at close range. [LSJ 19970915]" and
"If the strike is dodged, no damage is done. [LSJ 19980526][RTR 20041202]" are the reasons why this seemed confusing. My argument here is: riposte seems to have the same limitations as strikes like Coma, for example, so why should it behave differently here? Coma can be dodged and also doesn't send the opposing minion to torpor after combat ends, so why should riposte behave differently? Is there something specific that points to this?
Text for the card mentioned:
"Name: Coma
[Sabbat:U, SW:U, CE:U, BH:PM3, Third:U, FB:PM1]
Cardtype: Combat
Cost: 3 blood
Discipline: Dementation
[dem] Strike: send the opposing vampire to torpor.
[DEM] As above, and that opposing vampire does not unlock as normal during their next unlock phase.
Artist: Ash Arnett"
> Flores wrote:
> That seems a reasonable response, but what about this section of the rulebook:
>
> "Combat Ends: This effect ends combat immediately. This type of strike is always the first to resolve, even before a strike done with first strike (see First Strike), and it ends combat before other strikes or other strike resolution effects are resolved."
>
> This is essentially the reason why I had this question in the first place, since after choosing strikes, strike resolution phase follows, once one combat ends is resolved, the other one shouldn't, no? Meaning, only one of the combat ends should work, the other one would just be a selected strike that does not get resolved.
>
When combat ends immediately it means one skips to the "End of Round" step of combat immediately without any further resolution of effects that are yet to resolve.
Strike resolution is simultaneous for the strikes that resolve at the same speed/timing window.
Order of strike resolution
X) Strike Dodge - Always resolves (defensive strike even if combined with an offensive effect) and protects the minion against effects from the opposing strike, the order is irrelevant
1) Strike Combat Ends - First strike to resolve (defensive even if combined with an offensive effect) together with other S: CE
2) First Strike - First offensive strike to resolve together with other First strikes
3) Normal Strike - Last to resolve together with other normal strikes
> Flores wrote:
> And for the riposte section, I have read the card, but my main argument as to why it seems weird to me that it would do damage even against combat ends is because it seems to behave very similarly to any other strike.
> "The damage is only dealt if the strike was resolved at close range. [LSJ 19970915]" and
> "If the strike is dodged, no damage is done. [LSJ 19980526][RTR 20041202]" are the reasons why this seemed confusing. My argument here is: riposte seems to have the same limitations as strikes like Coma, for example, so why should it behave differently here? Coma can be dodged and also doesn't send the opposing minion to torpor after combat ends, so why should riposte behave differently? Is there something specific that points to this?
>
See reason above. Coma is a normal strike and thereby not the same as Riposte
> Flores wrote:
> That seems a reasonable response, but what about this section of the rulebook:
>
> "Combat Ends: This effect ends combat immediately. This type of strike is always the first to resolve, even before a strike done with first strike (see First Strike), and it ends combat before other strikes or other strike resolution effects are resolved."
>
> This is essentially the reason why I had this question in the first place, since after choosing strikes, strike resolution phase follows, once one combat ends is resolved, the other one shouldn't, no?
>
From the rulebook: "Resolve Strike: The effects of the strikes from both minions are resolved simultaneously."
If both players play a strike:combat ends, there's no reason why one would resolve before the other since they resolve "simultaneously".
"This type of strike is always the first to resolve,..." and both strikes are of this type.
Prince of Paris, France
Ratings Coordinator, Rules Director