Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[ackmondual]

The designer diary mentions that it was always a 1-shot thing, even if not originally an event card....

Inheritance: Another one that was initially a one-shot Kingdom card. The big thing to muck with here was what exactly you could put the counter on. At one point Treasures worked; I tried letting it go on VP cards. VP cards were too automatic, and then it was simpler not to allow Treasures. There was also the question of when exactly the Estates were yours; some versions didn't work for when-buy abilities.

As you're allowed to assign the other player tokens (barring any restrictions like Seaway), would it have been that bad to remove the once per game clause from this?  I'm thinking if you do, then simply return the card set aside on the Inheritance token, and swap in the new card that you want to be the Inheritance

[Commodore Chuckles]

The main thing is, why would you ever want to do it more than once? Unless what you're suggesting is like Prince, where when you play the Estate, you first play one card, then play another, in any order.

[teamlyle]

You could possess another player and then buy Inheritance for them, assigning it to a bad card so they can't ever make their Estates what they want.

[LastFootnote]

Inheritance is once-per-game to prevent rules questions, not for balance reasons. I mean, if switching Inheritance targets had been this awesome thing we were constantly doing, then maybe it would have been worth the rules wackiness, but as it stands "once per game" is far simpler.

Like, say I inherit Lighthouse, then when I have a bunch of Estates in play I switch it to Dungeon. It creates questions. These questions have answers, but it's much simpler not to have the questions in the first place.

[ackmondual]

Inheritance is once-per-game to prevent rules questions, not for balance reasons. I mean, if switching Inheritance targets had been this awesome thing we were constantly doing, then maybe it would have been worth the rules wackiness, but as it stands "once per game" is far simpler.

Like, say I inherit Lighthouse, then when I have a bunch of Estates in play I switch it to Dungeon. It creates questions. These questions have answers, but it's much simpler not to have the questions in the first place.

I'd discard those Estates from play, but I'm sure the full iceberg reveals a list of other scenarios that would need to be contended with.

[markusin]

Inheritance is once-per-game to prevent rules questions, not for balance reasons. I mean, if switching Inheritance targets had been this awesome thing we were constantly doing, then maybe it would have been worth the rules wackiness, but as it stands "once per game" is far simpler.

Like, say I inherit Lighthouse, then when I have a bunch of Estates in play I switch it to Dungeon. It creates questions. These questions have answers, but it's much simpler not to have the questions in the first place.

I'd discard those Estates from play, but I'm sure the full iceberg reveals a list of other scenarios that would need to be contended with.

Uh, I wouldn't? Even if the second inherited card wasn't a duration, I'd think the Estates stay in play, for similar reasons as to why a Wharf played with Procession of trashed with Bonfire should give me card draw next turn.

So yeah, rules questions.