rec.games.trading-cards.jyhad

Strike: Combat Ends ruling - unbalancing and illogical?

2 messages from 2 participants · 20 March 1995 – 21 March 1995
original thread on Google Groups

L. Scott Johnson

The Design Team ruled (11/9/94) that if the acting minion in a combat plays a strike: combat ends, then the blocking minion gets no strike, not even the opportunity to play a strike card. The precludes even playing another strike: combat ends. Why? Nowhere in the rules does it suggest that one strike could remove the remainder of the Choose strike phase, even before the chosen strike resolves. Section 15.3: Combat Ends: Considered a strike, this ends combat immediately (before any damage is dealt or any strike's effects take place). Note that combat ends is not affected by Dodge and even cancels strikes with first strike. The effect of the above rule is: *when the strike resolves* combat is over, cancelling any effects (already resolved) of a first strike, and nullifying the (pending) effects of the opposing minion's strike. Now, this usually doen't matter either way. But, when you are up against a "Majestic Bleed" deck, the acting minion suddenly has a big advantage. Since the "... this vampire may pay 1 to untap" clause of majesty is not part of the strike (IMHO), both minions should be capable of playing superior Majesties (and/or Earth Melds) to untap. This would remain true to the original (and the updated) rules, while mantaining some small measure of balance for the blocking minion (who should usually have the advantage). This is not MtG, there are no interrupt effects. I don't know why Majesty would be an exception. L. Scott

CurtAdams

sjoh...@math.scarolina.edu (L. Scott Johnson) writes: >The Design Team ruled (11/9/94) that if the acting minion in a combat >plays a strike: combat ends, then the blocking minion gets no strike, >not even the opportunity to play a strike card. The precludes even >playing another strike: combat ends. >Why? Nowhere in the rules does it suggest that one strike could remove the >remainder of the Choose strike phase, even before the chosen strike resolves. Probably to enable Combat Ends vs. a Rotschrecking Gangrel. Or maybe they just didn't think about it. It might have been because of resolution problems if the opponent First Strikes. >Section 15.3: > Combat Ends: Considered a strike, this ends combat immediately (before >any damage is dealt or any strike's effects take place). Note that combat >ends is not affected by Dodge and even cancels strikes with first strike. >The effect of the above rule is: *when the strike resolves* combat is over, >cancelling any effects (already resolved) of a first strike, and nullifying >the (pending) effects of the opposing minion's strike. >Now, this usually doen't matter either way. But, when you are up against >a "Majestic Bleed" deck, the acting minion suddenly has a big advantage. A *MAJOR* problem. Incidentally, I think that "combat ends" is generally too good a card. It's enormously superior to a dodge and always available at normal skill. P.S. Did you have a run-in with Majestic Bleed? Curt Adams (curt...@aol.com)