[fixed/closed]Scorched Earth no cancel button, only kills 1
Posted: 22 Nov 2014, 15:04Describe the Bug:
1) The base cost for Scorched Earth is
.
2) Scorched Earth keeps asking for targets until each land on the battlefield has been chosen as a target. There is no cancel button.
3) The targeted lands receive prohibition signs which remain on those lands for the remainder of the game, rendering them untargetable. The prohibition signs remain on them even when Scorched Earth is canceled by clicking on a nonland card when prompted to discard öand cards.
4) Only the last chosen target is destroyed when Scorched Earth resolves.
Which card did behave improperly ?
Scorched Earth
Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
KOT, duel
What exactly should be the correct behavior/interaction ?
The base cost is.
There is a cancel button for choosing targets, so less than the maximum number of targets can be chosen.
Prohibition signs are removed after targets have been chosen.
All targets are destroyed.
Are any other cards possibly affected by this bug ?
-
1) The base cost for Scorched Earth is
.2) Scorched Earth keeps asking for targets until each land on the battlefield has been chosen as a target. There is no cancel button.
3) The targeted lands receive prohibition signs which remain on those lands for the remainder of the game, rendering them untargetable. The prohibition signs remain on them even when Scorched Earth is canceled by clicking on a nonland card when prompted to discard öand cards.
4) Only the last chosen target is destroyed when Scorched Earth resolves.
Which card did behave improperly ?
Scorched Earth
Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
KOT, duel
What exactly should be the correct behavior/interaction ?
The base cost is
.There is a cancel button for choosing targets, so less than the maximum number of targets can be chosen.
Prohibition signs are removed after targets have been chosen.
All targets are destroyed.
Are any other cards possibly affected by this bug ?
-