Draft of CoE Digest #204 Q3 - Heedless Revelry: how it works - Open until March 18th

Locked
User avatar
Manuel
Council Chairman
Posts: 456
Joined: Thu Aug 10, 2006 11:31 am

In order to contribute to this thread please follow these rules:

1) The thread will be open until March 18th.
2) There will be a maximum of one reply per forum user, and that reply cannot be edited. We want to actively avoid starting "flame wars", so please speak your peace, let others speak their peace, and that's it.
3) After the review period, the RC will carefully consider everyone's contributions, revise the draft as appropriate, and then the Digest will be published and official.
How does Heedless Revelry actually work when revealed as an on-guard card?

To answer this question, we start with the second part of the card’s text:
Alternatively, may be revealed as an on-guard card on a company after the successful play of an item, ally, or faction. Tap all untapped non-Ringwraith, non-Wizard characters in the company.
Errata and a clarification for Heedless Revelry were issued in CRF 13:
Card Erratum: Change «after the successful play» to «in response to the play[.]»*

Does not interfere with the playing of the card it is revealed in response to.
*presumably this period should be outside of the quotation marks

Therefore, the second paragraph of the card should actually read:
Alternatively, may be revealed as an on-guard card on a company in response to the play of an item, ally, or faction. Tap all untapped non-Ringwraith, non-Wizard characters in the company.
In practice, this means that Heedless Revelry can be revealed in response to a player declaring that a character in the company is being tapped (as an active condition) to play an item, ally, or faction. Furthermore, per this CRF rule:
A revealed on-guard card retroactively takes effect as though it were both declared and resolved immediately prior to the chain of effects during which it was revealed.
Heedless Revelry is treated like any normal on-guard card, i.e. declared and resolved immediately prior to the chain of effects during which it was revealed. This means that, when it is revealed, its second effect immediately taps all non-Wizard, non-Ringwraith characters in the company and the resource player doesn’t have the option to respond because Heedless Revelry has already been declared and resolved prior to the current chain of effects.

Most importantly (and only slightly paradoxically), the character who tapped to play the item/ally/faction is not affected by Heedless Revelry because the character was already tapped as an active condition of declaring the resource being played, and thus, that active condition is still met even after Heedless Revelry resolves and the resource being played can still resolve as normal, including any relevant influence checks and so forth. This follows the CRF clarification cited above:
Does not interfere with the playing of the card it is revealed in response to.
As a final note, revealing Heedless Revelry does not prevent an additional minor item being played by a Wizard/Ringwraith since those characters would remain untapped, but all other characters would be tapped prior to the resolution of the initial resource and prior to when the additional minor item could then be played.
www.meccg.com
User avatar
Konrad Klar
Rules Wizard
Posts: 4361
Joined: Sun Feb 04, 2007 9:35 am
Location: Wałbrzych, Poland

Nitpicking:
In practice, this means that Heedless Revelry can be revealed in response to a player declaring that a character in the company is being tapped (as an active condition) to play an item, ally, or faction.
In response to a player declaring that a character in the company plays an item, ally, or faction.
Tapping to action is part of declaration.

Besides I agree.
We will not speak of such things even in the morning of the Shire.
User avatar
Manuel
Council Chairman
Posts: 456
Joined: Thu Aug 10, 2006 11:31 am

Thanks everyone for your contributions. The RC will study them carefully and come up with a final digest soon.
www.meccg.com
Locked

Return to “Drafts”