Author Topic: Lampstand vs strife  (Read 1228 times)

TheHobbit13

  • Guest
  • Trade Count: (0)
Lampstand vs strife
« on: December 15, 2014, 03:19:46 PM »
0
This question came up at nationals but I would like to get a second opinion.  The question is can strife withdraw all heroes in the main battle before a side battle resolves ( lamp is up). If yes an explanation of how this is different then darius decree in an all good side battle.

browarod

  • Guest
  • Trade Count: (0)
Re: Lampstand vs strife
« Reply #1 on: December 15, 2014, 03:32:54 PM »
0
I had always assumed that Strife only withdrew Heroes in the current battle (so if there was a side battle it wouldn't affect Heroes in the main battle). Looking now at the definition of "withdraw" it simply says that the targets must be in the field of battle so I guess I've been assuming it incorrectly, lol.

The definition of "not in battle" states that 'Cards "not in battle" are cards found in:
Territories
Set-aside areas
Lands of Redemption.'

Therefore, I would assume Lampstand cannot and does not restrict Strife (since Withdraw by default targets cards that are in the field of battle) and Strife would withdraw all Heroes (but one) in battle.

If the main battle is set aside, however, (such as with Ambush the City) then Strife would NOT be able to withdraw Heroes in the main battle as they are not currently in battle. Lampstand would protect them as well but in this case it would be moot because Strife can't target anything in set aside anyway.

I'm not sure what the Darius' Decree situation you mentioned is, though....
« Last Edit: December 15, 2014, 03:38:51 PM by browarod »

Offline Redoubter

  • Trade Count: (+3)
  • Hero Member
  • *****
  • Posts: 4910
    • -
    • Northeast Region
Re: Lampstand vs strife
« Reply #2 on: December 15, 2014, 03:34:16 PM »
0
Yes, Strife ("Withdraw all but one hero.") can withdraw all heroes in the Field of Battle except for one, regardless of what battle they are in.  The reason is that the default targeting for withdraw is "Field of Battle" instead of the normal "in battle" (which refers to only the active battle).

Quote from: The REG
Default Conditions
 Withdrawn characters return to their owner's territory.
 Targets must be in the field of battle.

Lampstand ("Protect all cards not in battle from evil Dominants (grim-reaper icon cards).") protects all cards that are "not in battle" which is a specific list of locations:

Quote from: The REG
Not in Battle
Several Redemption® cards contain special abilities that refer to cards that are “not in battle”. Cards"not in battle" are cards found in (1) territories, (2) set aside areas, and (3) Lands of Redemption.

Note that "Field of Battle" is not included in any form, so NOTHING that is in any battle is protected by Lampstand.  Strife is not stopped at all because those cards are not protected.

By contrast, Darius' Decree ("Opponents may not play good Enhancements from hand, unless an Evil Character is in battle. You may discard this card to discard all Heroes in set-aside areas.") uses the phrase "in battle."  Therefore, it only applies to the active battle.  Even if there is an evil character "in the Field of Battle" it is still not "in battle" for the purposes of Darius' Decree if there is a side battle of only heroes.  Therefore, in an active side battle with no evil character in it (even if there is one in a different battle), opponents are restricted from playing good enhancements.

TheHobbit13

  • Guest
  • Trade Count: (0)
Re: Lampstand vs strife
« Reply #3 on: December 15, 2014, 03:46:49 PM »
0
But "in battle" refers to the present battle. Therefore not in battle refers to all cards not in the present battle.  Are the two heroes in the original battle a part of the present side battle?  No, so they are not in battle.  If they are not in battle for dd then they are not in battle for lampstand.  I think these have to be ruled the same way. Also the fact that strife can target cards in the field of battle is true but not really relevant because protection stops targeting.

browarod

  • Guest
  • Trade Count: (0)
Re: Lampstand vs strife
« Reply #4 on: December 15, 2014, 03:49:59 PM »
0
"Not in battle" has a specific definition for what it represents, it does not change to mean "not in the present battle" in this situation. "Not in battle" always and in every situation means cards in territories, set aside areas, and lands of redemption. "In battle" has a specific definition for what it represents, it does not change in this situation. "In battle" always and in every situation means cards in the current, active battle.

Lampstand and Darius' Decree use different wording, therefore there is no reason to rule them the same way.

Prior to them establishing a specific definition of "not in battle" (it used to just mean cards that didn't qualify as "in battle") you would have been correct. However, since it now has a definition, that definition applies in all cases.

TheHobbit13

  • Guest
  • Trade Count: (0)
Re: Lampstand vs strife
« Reply #5 on: December 15, 2014, 04:03:29 PM »
0
I am assuming either a card is not in battle or it is. Let's revisit the dd ruling.  The definition of not in battle according to  Reg means that the characters in the original battle are what? Not in battle and Not not in battle?  Either way I don't think the definition of not in battle takes side battle into account.  Also it's odd to say not in battle and in battle are two independent terms. Just as odd as it is to say in play and not in play are independent.

browarod

  • Guest
  • Trade Count: (0)
Re: Lampstand vs strife
« Reply #6 on: December 15, 2014, 04:13:30 PM »
0
I do agree that it is odd (I was against the definition when they put it in place), and they created that definition to limit Lampstand's power (otherwise it stopped Mayhem, would have stopped Vain Philosophy, lots of other cards, etc). Cards that are in a suspended battle are in the field of battle but not in the current battle. "In battle" is shorthand for "in the current battle."

So yes, technically cards in a suspended battle are not "in battle" and not "not in battle", as awkward as that sounds.

Offline Redoubter

  • Trade Count: (+3)
  • Hero Member
  • *****
  • Posts: 4910
    • -
    • Northeast Region
Re: Lampstand vs strife
« Reply #7 on: December 15, 2014, 04:33:42 PM »
0
The ruling is definitely as I stated, though I understand your confusion.

The phrase "not in battle" is a reference to ONLY cards in Territories, Set-Aside, and Land of Redemption.  That is the rule, and it was put in place due to the way certain cards interact (not to nerf Lampstand actually, it was more to do with cards like the orignal Angry Mob IIRC).  It does not refer to hands, decks, discard piles, or any card in any battle (that is, in the Field of Battle).

Cards that are not in the current battle still do not fit the criteria, because they are not in one of the three exclusive locations held within the definition of 'not in battle'.

Browarod is correct, cards can be not in battle but not "not in battle" because they do not fit the definition.

Do not think of "not in battle" as a literal phrase, it is a keyword like many other things, and has a specific definition.

TheHobbit13

  • Guest
  • Trade Count: (0)
Re: Lampstand vs strife
« Reply #8 on: December 15, 2014, 08:54:22 PM »
0
I mean it's w/e. If that's the definition then that's fine. I really doubt they were thinking of side battle cards when they made it.  As long as it's the consensus I will play that way.  :)

Offline Redoubter

  • Trade Count: (+3)
  • Hero Member
  • *****
  • Posts: 4910
    • -
    • Northeast Region
Re: Lampstand vs strife
« Reply #9 on: December 15, 2014, 09:17:44 PM »
0
I mean it's w/e. If that's the definition then that's fine. I really doubt they were thinking of side battle cards when they made it.  As long as it's the consensus I will play that way.  :)

FWIW, when this was initially discussed, it seemed that the default targeting of Strife and the implications may not have been designed as such.  It seems that it was not intentional that it ended up being able to target Field of Battle, there just weren't restrictions placed on it when printed.

And no, based on reactions in that thread, side battles weren't thought of, but it's a fun strategy ;)

 


SimplePortal 2.3.3 © 2008-2010, SimplePortal