Magic The Gathering: Arena Dev Tracker

Yes, we like tags better than folders too; that's the direction we want to go in the future.

We've mocked up some compact mode ideas in the past, with smaller deck boxes, but I agree a list view (with tags and stats!) would be a lot more exciting, for me. But that's an entirely new page, so it's a lot harder to get the work scheduled.

Dropdowns should be easy, I'll see what I can do.

Hello!

I've been trying to add deck builder improvements as I can, so it's nice to see what people are interested in.

Deck status: We've got some features in the pipeline around "Wish List" decks as you call it, so I think we're on the same page there. We currently don't have any plans for a higher tier of favorite. Although I can envision how it might work from a UX perspective, I don't expect it to be a priority for us any time in the near future.

Deck number: I'm not a server programmer, however, I'm pretty sure it has nothing to do with storage but with server bandwidth. The game is server-authoritative, which means we don't store any information on the client. So every time you ask for your decks we have to send you all of them. I think the current number of decks is designed not to take down our services if people are making lots of requests. (more basically, if people ask for too much data at once we end up DDOS'ing ourselves) On top of that, our de...

Chandra avatar here; can confirm.

A few cards here and there regress. For Amonkhet block, around five cards got minor problems as a result of being untested for two-ish years of development. Not too bad for machine-generated code I think! #wotc_staff

Yeah, I think the toggle's days are numbered.

It was initially designed to clean up the UI for new players. It's hard enough to decide which queue you want to play in as a new player, but 2x-ing every queue makes the decision even harder. Also, BO3 is MUCH more skills testing, another reason not to send new players there (other than game length).

That all said, none of us particularly like how it works right now, and there is a good design in the pipeline about how to fix that part of the UI. I can't commit to a timeline, but it is one of my priorities to get fixed as soon as I am able to schedule the resources.

It's a trade-off. Like any limited-time event in any venue, a shorter timeframe can draw people in because it feels more special. Also, more people are playing at once instead of being spread out - queue health is always something we have in mind for specialty events.

As for closing entries, we just want to make sure that anyone entering has enough time to play the games they need. Even if you could enter 5 minutes before the event ended, you wouldn't be able to actually get the prizes.