Cactus Game Design Message Boards

That's defining how ignore works

Which is how "game rule" is defined. 

at first I thought the answer was A. But upon YMTs observation on multiple abilities I think the answer is C.

What about the 16 card hand limit..  Could I only search for 16-x heroes (x is the number of cards currently in hand)?

As a member of K.I.S.S., I vote 'D'.

The original ruling for the hand limit was that you would stop at 16, regardless of SAs. It seems logical that the same would happen here. First, every hero not currently in battle would be added to battle. Then, you would add the duplicates to your hand until you reached 16. The rest would stay in deck.

I believe the order would be up to the owner of the deck, much like placing under draw pile can be in any order. If you have a card that searches for Jacob, you do not have to pick the first Jacob you see and then stop looking at your deck. You just have to make sure you take out only what you were allowed to search for.

I somehow missed the banding wording the first time I read it. YMT is correct, dupes would go to hand up to 16 your choice and the rest would stay in deck.

Now, I've always played that the card is completely revealed, but I've seen people only reveal it enough to show that it satisfies the requirements.  (i.e., showing that it's red brigade enhancement with A Soldiers Prayer)

Thanks for your input, Tim.  That's the same conclusion that Jordan and I came to during a game.  Neither of us were 100% confident we were correct though at the time so I posted this.

with RDT

Hey,

A player may not target a character with a special ability that allows you to pick the target If I play a card like Creation of the World that targets all Gen. Heroes, it targets all copies of Jacob - This very same situation is actually laid out in the rulebook, using Valley of Dry Bones and Moses.

There's a difference between controlling multiple copies of a character in your territory/set-aside area and multiple copies of the same character being in battle.  It is possible to end up with two copies of Moses in your territory (which is what Valley of Dry Bones would cause).  It is NEVER possible to have two copies of the same character in battle.

I don't agree with either of Tim's statements.

Having two different defaults for the same special ability is unnecessarily confusing.

Neither of my statements actually had to do with defaults, so I'm a little confused by your comment.  Could you try to clarify for me?

Tschow,

Tim "Sir Nobody" Maly

Quote from: SirNobody on April 26, 2011, 11:50:53 PM

There's a difference between controlling multiple copies of a character in your territory/set-aside area and multiple copies of the same character being in battle.  It is possible to end up with two copies of Moses in your territory (which is what Valley of Dry Bones would cause).  It is NEVER possible to have two copies of the same character in battle.

I'm confused as to why we have a seemingly meaningless distinction between these two, when both Valley of Dry Bones and Creation of the World do essentially the same thing.

Exactly.  Qualifying your targeting based on the destination of said targets is like putting the cart before the horse.   

Hey,

Quote from: SirNobody on April 26, 2011, 11:50:53 PM

There's a difference between controlling multiple copies of a character in your territory/set-aside area and multiple copies of the same character being in battle.  It is possible to end up with two copies of Moses in your territory (which is what Valley of Dry Bones would cause).  It is NEVER possible to have two copies of the same character in battle.

I'm confused as to why we have a seemingly meaningless distinction between these two, when both Valley of Dry Bones and Creation of the World do essentially the same thing.

There are two sides to the duplicate characters rule.  The more commonly implemented one is the rule that restricts me from having more than one copy of a unique character that I control.  The less common side is that two copies of the same unique character cannot be in the same battle at the same time.

The second side stems from the idea that you can't block a converted Goliath with a non-converted Goliath, and doesn't have anything to do with control of the character so it is necessary in addition to the first side.  (It's not necessary in that the game would explode without it but rather that the duplicate characters rule as it has been since it's inception would be significantly different without it.)

Creation of the World creates the unique situation where both sides of the rule apply at the same time.  The second side is more restrictive, so it's effect ends up being applied.

If you're really asking why the duplicate characters rule is what it is...I can't help you with that (I'm pretty sure I was against it when it came out but that rule slightly predated my involvement in such discussions).

Tschow,

Tim "Sir Nobody" Maly