Heart#97945
My feedback
6 results found
-
69 votes
An error occurred while saving the comment Heart#97945 supported this idea ·
-
3 votes
An error occurred while saving the comment Heart#97945 commented
Not a bug
@DAC169#34537 I'd assume they mean opponent's Ashiok (as Ashiok only exiles opponent's graveyards), and the OP's Case (since that's the most likely scenario
@Sakk cases can only be solved on your turn. So if the opponent activates Ashiok (their turn 99.99% of the time, your case won't solve because it's not YOUR end step
-
111 votes
An error occurred while saving the comment Heart#97945 commented
Which card is it? Do you have an image/screenshot of it?
What set/cost is it?
What effect does it actually do?
-
2 votes
An error occurred while saving the comment Heart#97945 commented
As they said, not a bug. Calamity made two token clones that copied Marauding Sphinx.
-
130 votes
An error occurred while saving the comment Heart#97945 commented
See mja16777216#38339's original post here (regarding Planeswalkers): https://feedback.wizards.com/forums/918667-mtg-arena-bugs-product-suggestions/suggestions/48271433-calamity-galloping-inferno-saddle-triggers
An error occurred while saving the comment Heart#97945 commented
As the title says, Calamity, Galloping Inferno on creates one token copy when attacking a player defending a battle (or attacking a player that controls a Planeswalker, according to mja16777216#38339).
This bug is repeatable easily against Sparky. The bug seems to occur as part of selecting targets for the new tokens. If no additional target is available, it functions as intended.
This was on Arena on Windows.
Heart#97945 supported this idea ·
-
85 votes
An error occurred while saving the comment Heart#97945 commented
I'll add to yours since you seem to be extremely thorough. This bug also occurs when attacking a player that is defending a battle.
Something about the client asking you to pick who the token is attacking is causing it to skip the second token.
Tested this a bunch against Sparky.
Heart#97945 supported this idea ·
I've noticed this too with draft sometimes (usually a negate).
A work around I've found is to drag and drop the card into your deck and it will drop the appropriate one there and you can add to it as normal.