Magic The Gathering: Arena Dev Tracker

Firstly, that warning is automatically generated because it makes the target lose all abilities. Remember that code for MtG: Arena is generated via parsing the card text. Virtually nothing is hand-coded for exclusively for a single card.

Secondly, Arena usually starts implementing a set weeks after the set is "locked in" because the printing pipeline is longer than digital's. We give feedback about what's likely to be easy or hard to do during the design process, but it's set pretty much in stone before we start committing code. I look forward to the day when Play Design can iterate on a set in Arena, but that's still petty far out. #wotc_staff

Correct, these events are one time entries where losses don't hurt you.

#WotCStaff

You may pick which effect puts it into exile. Remember to disable "automatically pick replacements" in your game options. #wotc_staff

Philosophically, Direct Challenge is "kitchen table" Magic. We don't limit sets or have banned lists there, so you and your friend can play whatever you both want. (Exception: Tournament Match follows Traditional Standard.)

We had to add another option to support play with a commander in Direct Challenge, and decided to call that "Friendly Brawl".

Brawl events of course follow the normal format definition of Brawl and use Standard sets only.

#WotCStaff

False. When Historic ranked is around it will allow completion of dailies & weeklies just like Standard ranked.

Yes, same for those as well

Should be fixed as well.

Oddly, we get more games played on Wednesday than Saturday. Wednesday’s the second-highest volume day, which is one of the reasons we chose it. The goal is to have Brawl available as lots of people are playing, so we can get the best data (as per the reasoning cited above).

We’re working on that flavor of the issue as well. Same status, targeting a fix for Oct.

One-time fee. Wins count towards the rewards, losses are ignored.

Not losing the counter is a known bug, a fix will come in this month's major update. #wotc_staff

Welp... You've exposed a bug. :P Sparky depends on the predictive autotapping to determine whether it can cast something or not, and it seems like the predictive autotapper doesn't take into account casting tax. Thanks for letting us know!

Appreciate your feedback on the game mode names.

Everything that is Standard is labeled Standard. Modes that are focused on Historic we plan to label Historic.

Traditional means means that it matches tabletop Magic, especially that it is Best of 3, while Best of 1 is the default.

Play and Bot Match say neither Standard nor Historic, since both kinds of decks are welcome. (These modes are also part of the NPE, where players are far more likely to not know format terminology names.)

We do sometimes take some liberties with specialty mode names. Standard Metagame Challenge for instance doesn't say Traditional because we want to help sell the theme of that event (The risk of elimination is high, but there are great rewards if you aren't!) and there is limited characters available to use in the event name.

Agree the sorting needs work, this is something we want to address.

#WotCStaff

It will return after ELD has had some time as a standalone set first. :)

#WotCStaff

Awww. Thanks for the kind words and understanding where we are coming from. I will say the "and the rest of the team" part is really where the work came from. Even a small release takes a lot of mobilization. I just looked and numbers and pointed at people and code. Also, a special shout out to Megan O'Malley, who realized she had an HD3000 at home and carted the thing in at significant personal inconvenience so that we could get working on it immediately.

Try now :D

We've identify and implemented a mitigation for that chip and others like it. It's just a matter of getting it to you. Stay tuned.

Thanks for the illustrative report! Oddly we don't get a crash in the dev environment, but the GRE also wasn't successfully getting the token to be created (it thought it couldn't attach to anything, so it failed to finalize being created). I've fixed it for the next GRE patch, which is a couple weeks out I think. #wotc_staff

Thanks! This is 100% right :)