"I cannot possibly estimate what would lead to acceptable queue times, because I have no data on how many people are looking for a draft at a given time."

Until a few days ago, we didn't have any of that data for player drafts either :)

This is an interesting question, with both queue time & gameplay implications. Queue time questions we can sort out as we get more data, but the gameplay questions are stickier. In short: one of the key virtues of Draft is the variability from pod to pod. The more similarly each pod you're in drafts, the more repetitive the format will feel.

This is something we talk and think about regularly. For now we feel like non-matchmade is the overall better experience, but we'll continue to monitor and discuss here.

Just posted this in another thread, but we’re aware and looking at this. For player draft, we didn’t need these logs for our debugging purposes, but we understand that they’re also used for trackers, and we like the value those bring their users.

We’re looking to get that fixed; no definite timeline to give at this time. We put logs in for our debugging purposes, and in this case we’re getting our info in a different way. But we get that these are useful for trackers, etc. and we want to support that too.

Oh, good point! See my other comment in this thread for more info about why, but the first launch with this update could still be long. Shouldn't be any long updates after that.

Sure thing:
Background: Arena has a ton of different assets to handle all the cards, frames, indicators, VFX, etc. One of the things we need to do is ensure that none of these assets get corrupted, either during download or because of random weirdness with the hard drive. We used to check all the assets for consistency at every startup, but as the asset size continued to grow, this became too costly. Now Arena validates the assets on download, assumes they're good as they reside on-disk, but if it encounters any assets errors during gameplay it will flag itself to startup in "safe mode" next time. This means it will re-scan the assets to make sure none have been corrupted, then re-download any that are. This (as well as several other things) occurs while the client is saying "Checking for Updates".

The bug: In the original IKO release, there was an asset error that could be thrown in certain common circumstances (I think it was viewing a split-card). This didn't cause...

That would probably need some new semantics in the prompting-time version of the noun to mean "or has X in its cost", as that could POTENTIALLY become a 3+ cmc spell. And we'd need to ensure the X-bound logic enforced a MINIMUM X choice. Let alone the autotap concerns... #wotc_staff

Hello Azrael (that is my cat's name too btw),

We have a fix for this issue coming in the next update. Here's what you can do in the meantime.

1. Add another Gyruda to you deck
2. Put that Gyruda in your companion slot
3. Save the deck
4. Reopen it and take out the extra Gyruda from your sideboard

Hopefully, that helps!

Cool concept!

I wish I could share with you all of my mockups for this page. It's one of the places I'd really like to add more functionality to in the future. Good luck with your 100 Day Challenge!

There’s a little emblem-like indicator for Stomp’s lingering effect, yes. Still easy to miss, unfortunately.