Something really angering happened in a ranked match involving War Cry. War Cry states: Target immediately discards all Block cards in hand. Cantrip. Heres the battle log, i just took out the name and filled in the class & team instead. This starts off with the enemy warrior playing his War Cry. Enemy Warrior renders My Mage defenseless My Mage discarded Pushback Parry. My Mage blocked with Defender's Block. War Cry was cancelled. My Priest discarded Defender's Block. What the hell. Either Defender's Block prevents the War Cry attack or not, but this is inacceptable. In one cantrip move, the guy got to bypass all defenses spread over two characters. And immediatly follows it up with: Enemy Warrior moved. Enemy Warrior strikes nimbly at my mage. Enemy Warrior doubles the damage with a ferocious follow-up! And dead he is. Card Hunter gives you a very hard time to stand up against high damage high range step attacks, and i just need Defenders Block to be reliable. I don't know how the block-from-afar mechanics are realized, but it is not a block card in the targets hand. It is supposed to actually block anything that targets an ally closeby. You can tell me that the 'immediately' in War Crys description is the keyword here, but if we accept that nothing can intercept the discard, then for gods sake let the defenders block alone.
It's not a bug although it could be either way. Defender's block is supposed to protect allies. Question is whether or not should blocks try to block War Cry. Edit: A post has been deleted before this one.
If the target was the Mage, why is the Priest affected? I understand that the Priest's block has the Mage in its scope, but the Priest was not the target.
So what does that mean? That a defender's block or a cause fumble in play behave as if they were a block in every characters hand? Even so, Defender's block wasn't discarded as result of War Cry, it reacted to it and did its function as a block, but without actually canceling the discard of the mages parry. So i feel that there has to be done something about the order on this reactions checklist. If its easier to declare Warcry unblockable, im ok with that.
Yeah, because War Cry discards "immediately" it does so before checking for blocks, but it's still an attack so after that step, the game says next step - check for blocks. This is usually irrelevant because all the blocks have been discarded, however as your priest wasn't cleared out by War Cry, it's block actually then triggered for the attack. So it went: 1) Mage forced to discard all blocks 2) War Cry "attacks" 3) Game checks for blocks 4) Priest blocks the War Cry attack 5) War Cry is at this point canceled and does not complete the rest of it's effects (which in War Cry's case there are no more effects to be done). Simply making War Cry unblockable would remove checking for blocks and make it: 1) Mage forced to discard all blocks 2) War Cry "attacks" 3) War Cry completes its action I would recommend making a thread on the suggestion page about it.
I know its function. Let me explain what I interpreted from the OP. "My Mage blocked with Defender's Block" made me think this was the successful block. "My Priest discarded Defender's Block" made me think that then, since Defender's Block can block attacks for allies, that it was discarded because of that fact. It seems in a subsequent post the actual successful block was the Priest's. My interpretation of the events was incorrect. Thus my question is no longer relevant. What I was getting at though, was that if the Mage's Block successfully stops War Cry, other allied AoE blocks shouldn't be affected.
I gotta admit im not sure i copied the log correctly... like i said, i changed the names against the class... maybe i mixed it up. Gonna keep an eye open 'who' actually blocks corresponding to the log.
I think you did actually copy it correctly. It appears there may be a text bug as well on who defender's block is attributed to in the game log.
I want to mention in this context that Melting Armor triggers an allies def block as well - so you lose armor and the def block in one go, which i find bothersome as well.
This is a separate case and actually makes sense. The idea of Melt Armor is to have armor cards discarded before blocks (as it functions before blocks, for all blocks) and it can double as a block remover (hence less range than Dissolve Armor which has about the same effect). So I still wouldn't have it changed.
Just make area blocks like Cause Fumble and Defenders Block trigger first when defending a team mate. That can't be that hard to tweak into the mechanics. They either work, or fail, and then the attack resolves as normal. Simples.
The problem is that cards with the Immediately keyword trigger before blocks, and that's an intended mechanic (i.e. War Cry is supposed to make all blocks on that target character get discarded). If you don't get the context, the fix on War Cry is done already (War Cry already has the Unblockable keyword) and Robauke's citing how the way Melt Armor works is similar to how War Cry used to work.
