Page 1 of 1

[fixed/closed]Mox Diamond prevents casting, no storm count

PostPosted: 05 May 2014, 18:49
by Nexhro
Describe the Bug:
This previously reported bug still (or again?) exists in Apr14.

Hitting "cancel" when Mox Diamond asks to discard a land results in instants, sorceries and enchantments being uncastable until a land is played or the next turn starts. Creatures and artifacts can still be cast in that scenario.

I also noticed that it doesn't go onto the stack unless you discard a land and hence doesn't count as a cast spell if you choose not to discard. Probably too minor an issue to justify changing its code, but I thought I'd bring it up anyways.

Which card did behave improperly ?
Mox Diamond

Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
April 17 2014, duel

What exactly should be the correct behavior/interaction ?
Not discarding a land to Mox Diamond doesn't prevent further spells from being cast.

Mox Diamond goes onto the stack before the choice regarding the discarding of a land is made (which happens upon resolution) and thus counts as a cast spell even if the player chooses not to discard.

Are any other cards possibly affected by this bug ?
-

Re: Mox Diamond prevents casting, no storm count

PostPosted: 05 May 2014, 20:27
by Korath
Still, not again; it's the same problem that suspending cards used to have. Rewrote these replacement effects to work as replacement effects in 744fe8d, instead of happening at announcement (as with Mox Diamond) or as an enter-the-battlefield trigger (as with the Kjeldoran Outpost cycle in Alliances and Lotus Vale).

Re: [fixed]Mox Diamond prevents casting, no storm count

PostPosted: 06 May 2014, 05:56
by BAgate
I hate these complicated bugs. I only tested it with creatures and artifacts and those worked fine. Grrr...