During the coalition event Race to Orazca #5 between 4/20-4/22, there were multiple instances where cycling Vizier of Tumbling Sands with a creature disabled in the battlefield will cause a match freeze. Please review and fix, thanks!
//Edited Title -Brigby
+1
This issue resulted in loss of 2 matches
I’m interested to hear it’s all reenable disabled creature effects. This is why destroying hixus is freezing things too.
Had this issue in Race to Orazka, white node.
Reproduced yesterday in TotP event
Something similar happened to me recently when I destroyed a Hixus with forsake the worldly. The game was stuck in the animation that happens when a support os destroyed by a spell.
+1. This just happened to me twice today. I was in Fateful Showdown event against Territorial Gorger. I can’t remember the other event - but it definitely happens when a creature is disabled by a planeswalker power and you cycle vizier of tumbling sands in order to enable the creature. Game freeze.
PLEASE FIX THIS!!!
I just had the game freeze on me today playing allies. I played kor entaglers, opponent cast vizier and the game froze.
I had this happen with Combat Celebrant against Territorial Gorger in 2 different games.
I ran across this with my newly crafted Hixus. It only happened when a gem match destroyed it though, Vraska destroyed it repeatedly with no freezing. As to why I cast it four times against Vraska, well it helped a bit, and I managed to win in the end. Plus, it was only Training Grounds.
Vizier did this to me late during this past coalition event. AI cast it and my match instantly froze. It cost me a top 25 spot. It’s kinda ridiculous that this card has been known to cause freezing since at least OP’s post, and it still hasn’t been fixed.
Just checked and the bug is still there.
Reproduced with Combat celebrant trigger against Cast Out - game froze when CC’s exert reached 0 and was supposed to enable the creature under Cast Out.
Update: This should be fixed in the upcoming 2.7.1 build