[duplicate] Parallax Wave infinite swamp dysentery
Posted: 01 Apr 2022, 22:23Describe the Bug:
The opponent begins the turn, enters upkeep and starts to process a Parallax Wave which is out of counters and due to be sacrificed.
There are two consecutive messages for "Fast effects .. Trigger Parallax Wave?"
And then things get weird. A new message, "Fast effects .. Trigger Wall of Omens?" appears. Neither side had a Wall of Omens in play, but one has now appeared in play on my side. It is still the AI's upkeep.
The previous message is replaced by "Fast effects .. Trigger Courser of Kruphix?" I did already have a Courser of Kruphix in play. And this latest fast effects message enters an infinite loop. Each time I click 'done', the Courser poops out a Swamp. Of which my deck contains none. And the message reappears. Rinse and repeat, presumably forever.
Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Holidays 2021 ad1a6f8 - gauntlet
What exactly should be the correct behavior/interaction?
That poor centaur.
Are any other cards possibly affected by this bug?
The opponent begins the turn, enters upkeep and starts to process a Parallax Wave which is out of counters and due to be sacrificed.
There are two consecutive messages for "Fast effects .. Trigger Parallax Wave?"
And then things get weird. A new message, "Fast effects .. Trigger Wall of Omens?" appears. Neither side had a Wall of Omens in play, but one has now appeared in play on my side. It is still the AI's upkeep.
The previous message is replaced by "Fast effects .. Trigger Courser of Kruphix?" I did already have a Courser of Kruphix in play. And this latest fast effects message enters an infinite loop. Each time I click 'done', the Courser poops out a Swamp. Of which my deck contains none. And the message reappears. Rinse and repeat, presumably forever.
Which update are you using? (date, name)Which type? (duel, gauntlet, sealed deck)
Holidays 2021 ad1a6f8 - gauntlet
What exactly should be the correct behavior/interaction?
That poor centaur.
Are any other cards possibly affected by this bug?