Magic The Gathering: Arena Dev Tracker

Huh. You must have been missed somehow. Contacting customer support is right. If you have the avatar, you should have the title

Hey Folks - Thanks for the reports. The event has been disabled, and players who participated will receive reimbursement via the player inbox shortly.

We added "The Untouchable" and "The Mind Sculptor" for winners of the appropriate decathlons and "The Champion" for anyone who has won an Arena Championship.

These aren't the right things to build achievements around, but we felt they certainly deserved titles

Ooh, that's not how that should be. I'm passing this on to our engineering & QA teams to get fixed

Improving the search there is on our list, agreed!

This is something we're talking about and working through. Doing this right ends up being more complex than one would like, but it's something we're interested in doing.

Getting to tabletop parity for legacy or modern are not currently priorities. Adding fun cards to Timeless, for its own sake, is something we're interested in. I would say somewhere between slow and top priority.

Yeah, that was legit me. Not sure why I'm not flair'ed on Discord, but I'm not on there nearly as often as Dave & Ian. (I tend to do most of my player talking here.)

I'd say Tom here knows what he's talking about, but, as a mime, he clearly can't be talking. So, he knows what he's vaguely gesturing about?

Building an AI that could play arbitrary decks competently would be a massive challenge, and building one that could play them well is borderline impossible ("I'll need a research team and five years" kind of space).

Sparky's main job is to help newer players get comfortable with the motions and process of playing Magic. But there's simply no substitute for other players if you want a smart, interesting opponent

(Sparky's side job is getting beat down by Hydras with a billion counters on them, and she does great at that one.)

Hey, thanks for this report! We agree about this being a problem, and with the DFT Alchemy release we've updated how we handle battlefields on mobile, and they should now be stacking and behaving on mobile a lot more like they do on desktop. I'm very interested to hear if this has solved your particular problem here.

This looks like a rare bug we've seen (and are trying to track down) where it basically just shows you the wrong screen. In the cases we've seen, it's still counted and processed as a win on the back end (event courses update properly, daily/weekly wins awarded, etc.), but the wrong screen is shown on the client.

We apologize for the bug, and we're trying to hunt it down

Pretty close! We used to have one string that was "CARDNAME can't block", and we would replace CARDNAME with, well, the name of the card. When the templating changed, we now had two strings "This creature can't block" and "This token can't block". And, on each card, we had to swap to the proper one.

For cards that had this string both for themselves and for a token, (like this one and Consuming Blob), the process that updated the reference for the token got overly aggressive, and replaced both the string talking about the card and the one talking about the token.

Thanks for the report, and we'll get this fixed up soon

A fun story from the early days of Arena: We were getting Arena ready for its public debut, which would feature a Merfolk deck squaring off against Dinosaurs, both from Ixalan. We were playing some demo matches with the decks and looking to make sure everything was working properly.

In one match, a player cast [[Savage Stomp]] targeting the opponent's [[Siren Stormtamer]]. Just for fun, the opponent decided to sac the Stormtamer to counter the Savage Stomp. That all went fine, but, surprisingly, the Savage Stomp'ing creature got the +1/+1 counter. Which it shouldn't have, because Savage Stomp was countered. Our Rule team thought this was a bug. Off a quick check, the rules manager for Magic agreed it was a bug. So the engineers went looking for the bug, and, well...

You see, Savage Stomp was never countered. Siren Stormtamer can only counter a spell or ability targeting a creature you control. Once the Stormtamer was sac'ed, the Savage Stomp wasn't targeting a creat...

This error usually happens when there's a very subtle or strange legality problem, and it sometimes indicates a problem in our systems. Could you post the decklist that's doing this?

Longer version: We validate legality in three places (just to be sure), on the client as you build a deck (to be helpful and provide a good UI), on the services as you enter matchmaking (to ensure it's proper for the queue, and because you can't ever trust the client), and then on the actual game rules engine as it gets passed the two decks to use for the game (because the GRE has its own way of looking at the world). This type of error usually means that the client thought the deck was legal, but the matchmaking queue rejected it. That usually comes from other an unusual problem with the deck or a bug with how one of those systems is calculating legality.

Hmm, that certainly shouldn't be happening. I thought we fixed all of these "Brawl deck ending up with a sideboard" bugs, but clearly not. Thanks for the great report; very clear and helpful!

As of DSK Alchemy, the selection made with Nashi should be hidden