The card itself is supposed to be high damage, at the risk of pretty much losing your deck. However I just played against a shaman, that for some reason decided to use this thing, and I proceeded to wipe his deck in 2 turns with spare parts and 1-2 drops, But as soon as he hit 0 cards, whenever I played more cards, he didn't start taking damage. Fatigue states that whenever a player "tries" to draw a card, they will take fatigue damage. I thought maybe it just would work on the next turn, so I did it on my next turn again, and still nothing.
Just seems odd that this card completely negates the fatigue factor when the enemy is using the risk against the player. Not sure if it's a bug or what, but just doesn't seem right...
Ahhhh, ok, well that makes sense. For some reason in my mind it would have worked the same way because the cards came straight from the deck into the discard pile. But I guess that clears it up.
There is no bug. Fatigue damage is only taken when you try to draw a card but have no cards left. Based on the wording of Fel Reaver, there would be no fatigue damage because it only says to "discard" the top 3 cards rather than to "draw and then discard" them.
A good analogy to this is Tracking. It says to "look" at the top three cards of your deck, "draw" one and then "discard" the rest. It has been established that you don't take fatigue damage if you have less than three cards left, because trying to look at your top three cards is not the same as trying to draw those three cards.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
The card itself is supposed to be high damage, at the risk of pretty much losing your deck. However I just played against a shaman, that for some reason decided to use this thing, and I proceeded to wipe his deck in 2 turns with spare parts and 1-2 drops, But as soon as he hit 0 cards, whenever I played more cards, he didn't start taking damage. Fatigue states that whenever a player "tries" to draw a card, they will take fatigue damage. I thought maybe it just would work on the next turn, so I did it on my next turn again, and still nothing.
Just seems odd that this card completely negates the fatigue factor when the enemy is using the risk against the player. Not sure if it's a bug or what, but just doesn't seem right...
Not a bug! The discard mechanic itself does not cause fatigue damage. It's only when drawing cards on his turn that fatigue damage would occur.
Ahhhh, ok, well that makes sense. For some reason in my mind it would have worked the same way because the cards came straight from the deck into the discard pile. But I guess that clears it up.
It only discards the top 3 cards. if there are no cards left, there is nothing to discard.
There is no bug. Fatigue damage is only taken when you try to draw a card but have no cards left. Based on the wording of Fel Reaver, there would be no fatigue damage because it only says to "discard" the top 3 cards rather than to "draw and then discard" them.
A good analogy to this is Tracking. It says to "look" at the top three cards of your deck, "draw" one and then "discard" the rest. It has been established that you don't take fatigue damage if you have less than three cards left, because trying to look at your top three cards is not the same as trying to draw those three cards.