Dominion Strategy Forum

Please login or register.

Login with username, password and session length
Pages: [1]

Author Topic: Gain to hand vs Haunted Woods  (Read 327 times)

0 Members and 1 Guest are viewing this topic.

Sidsel

  • Bishop
  • ****
  • Offline Offline
  • Posts: 121
  • Respect: +171
    • View Profile
Gain to hand vs Haunted Woods
« on: November 16, 2017, 11:23:49 am »
0

Lots of 'gain to hand' in Nocturne. So,

do you first gain to hand, then topdeck your hand to the Haunted woods

or

first topdeck what ever you have, then gain the new card to hand?
Logged

Jeebus

  • Saboteur
  • *****
  • Offline Offline
  • Posts: 1416
  • Shuffle iT Username: jeebus
  • Respect: +1017
    • View Profile
Re: Gain to hand vs Haunted Woods
« Reply #1 on: November 16, 2017, 11:53:24 am »
+2

Lots of 'gain to hand' in Nocturne. So,

do you first gain to hand, then topdeck your hand to the Haunted woods

or

first topdeck what ever you have, then gain the new card to hand?

Buying always happens before gaining. This matters for several card interactions, especially with cards from Hinterlands, that's why this rule was first explicitly stated in that rulebook. So first you buy, which only means that you pay by deducting the cost from the coins you have generated; and then you gain, which means that you move the card you bought directly to the place it says (or else your discard pile).

So first you topdeck to Haunted Woods, then you gain.

If Haunted Woods was when-gain instead of when-buy, it would be the other way around. But let's take a real example: Let's say you Transmogrify a card into Grand Castle. Grand Castle has a when-gain that checks the cards in your hand. However, Transmogrify gains the Grand Castle directly into your hand (sometimes called the "no visiting rule" because the card doesn't "visit" the discard pile). So Grand Castle checks your hand after you gained it, and finds itself in your hand.
« Last Edit: November 23, 2017, 01:46:32 pm by Jeebus »
Logged
Pages: [1]
 

Page created in 0.053 seconds with 20 queries.