I was just playing a game where my opponent was on mono W tokens and had a Mondrak out. The triggers took so long to resolve (with no player input needed) that it ran down two of MY timers… and subsequently skipped through my following turn. I didn’t end up drawing the combo piece I needed, but if I had, this UI behaviour would have been the reason I lost. I was getting ready to cast something (even though it wouldn’t have saved me) but the UI just jumped straight from my draw step to my opponent’s turn.
Whose idea was it to have automated triggers count against a player’s timer?
Anyway, I’m posting this here since the WotC feedback channel requires a login to post.
You must log in or register to comment.
I mean, the Arena UI shouldn’t struggle to handle triggers in the first place. This game needs to have about 80% less animation.
But yeah, time when you technically have priority but can’t actually do anything shouldn’t count against your clock. And the game knows you can’t do anything, because it’s auto-passing for you.
I made a 1 Billion / 1 Billion Marwyn the other day. The game actually crashed. And before it crashed, it burned through my timers AND all my opponent’s timers. I got my game reloaded in time to rejoin seconds before my final timer ran out and I lost the game to timeout. But I did manage to screenshot it.
As a software engineer, I can think of some pretty basic mitigations for this kind of thing (handling any auto resolving stack larger than n cards tall as a single operation would PROBABLY not be that hard). Either WotC doesn’t care, or their architecture team is incompetent.
