Trick and treat freeze [Fixed]

There goes the possible perfect score in Trick and Treat.

Is it even worth trying to recuperate the prize from support? I recorded a small video, but I wonder if that even helps.

The freeze seemed to have something to do with pressing on the UI at the wrong time, but who knows why these freezes still plagues this app.

Oh good! It’s not just me. I also experienced a freeze on my first match which left a pretty bad taste in my mouth.

I have reported it using the in-game support but it won’t hurt to add it here too.

Sorry this happened to you @Tremayne it feels pretty rotten.

It seems that Black Treats are causing freezes for a lot of people @Magic_PQ_Support_Team

I know that I complain about “too many ties for first place” and, while this certainly will help with that issue, I’m not sure it’s the most elegant solution.

@Sarah - sorry to hear that. I’m also in contact with support.

I do wish Webcore would stop finding old bits of Oktagon code and just throwing them back into the game assuming that they work properly.

@Janosik - don’t know if that is correct but you made me laugh.

Also had a freeze after the opponent triggered a black treat. They had a Hollow Scavenger and Tolsimir, Midnight’s Light in their graveyard (I killed them in that order) so black treat should have brought back the Scavenger but the game just stopped with the spinning gold dust orb.

It definitely feels as if some of us were unlucky and got Black Tricks instead of treats.

Which is such a shame because I thought it was really good that they had brackets of 100 players and that’s been overshadowed by all of the soft locks.

A+ for the idea. D- for the execution.

This behaviour was such a bummer!
To update you folks, the team has been looking into it. Even if this particular event doesn’t come back until next year, we may end up learning more general stuff by studying it, right?

I urge all of you who had problems with the event to reach out to Customer Support if you haven’t already.

Oh, and I’m moving this thread to the Bugs section.