MTGO Crashing on using Wedding Announcement
Cast Wedding announcement in MTGO sealed and mtgo immediately crashed. It crashed 2 more times on reopening. The weird thing is it clearly crashed my opponents client as well, because they ended up timing out and gave me the win.
Spoke to some other players and it happened to another player with wedding announcement as well. Note I successfully used the card before so I'm not sure exactly what caused it, but it was played turn 3 this time.
Instinctive#21903
shared this idea
-
Jayce#20664
commented
Just cast it an had crash
-
MavZero87#11105
commented
Just cast Wedding Announcement in a draft, client crashed and match was reported 0-0-1(?), currently showing in my league as 1-1, after previously 1-0.
-
BenDelat#13320
commented
Just happened to me during a draft, i thought it was going to give me a loss, but after i logged back in was given a win. am i required to sideboard it after i know what it does, kind of a strong card to be on the sideboard.
-
GomesFTW#02093
commented
I had this happen to me on Thursday during release day and I just chalked it up to a server issue since the client was lagging a bit. Seeing this post now makes me realize what happened, and I lost a match that I was certainly not going to lose because I timed out and when I rejoined, the match had ended. I didn't take a screenshot unfortunately.
-
Foxantes#37584
commented
Just happened twice to me (I cast announcement and won the game after crash). In round 3 I avoided casting the card
-
Grincho#83314
commented
I just saw this happen, seems to be same issue that was going on with Grolnok
-
FluffyCyanide#50841
commented
I have replicated this bug twice. This bug is ripe for abuse as Wedding Annoucement essentially auto wins the match for the player who casts it.
-
Kevlar0808#86368
commented
The same thing happened to me. Wizards was very, very quick to rectify it (thanks!) when I used the chat feature for Customer Service. The game crashed after my opponent played Wedding Announcement, right when the trigger went on the stack at the End Step.
