2476
Rules Questions / Re: What is the "lose track" rule?
« on: January 27, 2012, 06:54:09 am »
I want to take a new crack at explaining the "lose track" rule, as I understand it, because I see that people are misapplying it (which isn't that strange since there's been a lot of debate and confusion).
Every instruction that tells you to move a card, tells you to move it from some place to some other place. Often the place to move it from is implicit, but it's there.
If not instructed where to move the card from and to, the default is:
The card's current location is often implicitly given. Golem talks about revealing cards from your deck, so when it tells you to play them it means from your deck to your play area. A card that talks about itself in its play-instruction, expects that it's in the play area. So Embargo and Mining Village mean to move themselves from the play area to Trash.
We can also have cases where an ability (on a card) says to move a card somewhere, and then to move it again. The second move implicitly tries to move the card from where the first move put it. This is the case with Throne Room + Mining Village. TR plays MV, moving it from your hand to the play area. Then it plays MV again, moving it from the play area to the play area. If it's not in the play area (such as if it was moved to Trash in the meantime), the move fails. (Since a card can't be trashed by moving it from Trash to Trash, MV can't Trash itself again.)
To also include the TR + MV + Possession case: TR plays MV, moving it to the play area. MV moves itself from the play area to Trash. Possession's when-trash ability moves MV to set-aside area. TR plays MV again, failing to move it first just like in the previous case. MV moves itself from the play area to Trash, but since it's not in the play area, this move fails. (So also in this case TR can't trash itself again, but for different reasons.)
Important: This rule only means that sometimes a card can't be moved. It never stops a card from being played (i.e. its intructions resolved).
Every instruction that tells you to move a card, tells you to move it from some place to some other place. Often the place to move it from is implicit, but it's there.
If not instructed where to move the card from and to, the default is:
- Gaining a card: Move it from Supply to discard
- Discarding a card: Move it from your hand to discard
- Trashing a card: Move it from instructed location to Trash
- Playing a card: Move it from your hand to the play area
The card's current location is often implicitly given. Golem talks about revealing cards from your deck, so when it tells you to play them it means from your deck to your play area. A card that talks about itself in its play-instruction, expects that it's in the play area. So Embargo and Mining Village mean to move themselves from the play area to Trash.
We can also have cases where an ability (on a card) says to move a card somewhere, and then to move it again. The second move implicitly tries to move the card from where the first move put it. This is the case with Throne Room + Mining Village. TR plays MV, moving it from your hand to the play area. Then it plays MV again, moving it from the play area to the play area. If it's not in the play area (such as if it was moved to Trash in the meantime), the move fails. (Since a card can't be trashed by moving it from Trash to Trash, MV can't Trash itself again.)
To also include the TR + MV + Possession case: TR plays MV, moving it to the play area. MV moves itself from the play area to Trash. Possession's when-trash ability moves MV to set-aside area. TR plays MV again, failing to move it first just like in the previous case. MV moves itself from the play area to Trash, but since it's not in the play area, this move fails. (So also in this case TR can't trash itself again, but for different reasons.)
Important: This rule only means that sometimes a card can't be moved. It never stops a card from being played (i.e. its intructions resolved).