[fixed/closed]Spell Burst & Urza's Lands
Describe the Bug:
Casting Spell Burst with or without buyback allows you to counter any spell for the incorrect value of X. I believe the Tron lands (Urza's Tower etc) are messing with its ability to track whether or not you can pay for X, thus allowing you a discount.
When I counter a spell (such as Wurmcoil Engine in the save) I am prompted to pay U, and then to pay 1, after I am prompted to use buyback or not. Selecting buyback allows me to pay 3 and then the spell resolves, countering the target spell. It basically allowed me to pay X=1 instead of X=6.
If I do not select buy back, I simply pay 1U total and the spell is countered.
This only works with a set of Tron lands in play, so I assume there is some error in how much mana the spell thinks I can pay for X. (See save)
Which card did behave improperly ?
Spell Burst
Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
JiN v1
What exactly should be the correct behavior/interaction ?
Spell Burst
Are any other cards possibly affected by this bug ?
NA
Casting Spell Burst with or without buyback allows you to counter any spell for the incorrect value of X. I believe the Tron lands (Urza's Tower etc) are messing with its ability to track whether or not you can pay for X, thus allowing you a discount.
When I counter a spell (such as Wurmcoil Engine in the save) I am prompted to pay U, and then to pay 1, after I am prompted to use buyback or not. Selecting buyback allows me to pay 3 and then the spell resolves, countering the target spell. It basically allowed me to pay X=1 instead of X=6.
If I do not select buy back, I simply pay 1U total and the spell is countered.
This only works with a set of Tron lands in play, so I assume there is some error in how much mana the spell thinks I can pay for X. (See save)
Which card did behave improperly ?
Spell Burst
Which update are you using?(date,name)Which type(Duel,Gauntlet,Sealed Deck)
JiN v1
What exactly should be the correct behavior/interaction ?
Spell Burst
Are any other cards possibly affected by this bug ?
NA