Magic The Gathering: Arena Dev Tracker

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

It is open and inclusive - If X=3, you will get a 1-drop, 2-drop, and 3-drop

Exactly so. The highlights are suppressed when making a hidden choice

This is correct - If X=3 you'll get 1,2,3; at X=5 you would get 1,2,3,4,5; etc.

Or why not some real power, like Force of Nature? I think that was the first card I ever bought as a single. 8/8 AND Trample? No way you could beat it!

I got Lord of the Pit in one of my first sealed decks too! (Also a crappy Scrubland; bah. Who cares about that?)

You should be fine here. We don't have rules against multiple people in a household from playing, just the same person playing multiple times.

We hear this a lot. Many people internally agree. And yet, whenever we've tested it before with Opens, we get more people playing in sealed versions than draft. We'll see if Directs give the same results or if we see something different!

Ease up about 20% there

Thanks for the report, and sorry about that! This is definitely an error, and it prompted our team to do a sweep and find some other, similar cases. We'll get them all fixed up.

Two reasons: Exposure and timing
As others have noted here, when there's a bug that's exploitable, we don't like to give it visibility before we have a fix. More players read our weekly announcements than Reddit, so even if it's been posted several times here, we could still be exposing it to a wider range of players.

Also, these weekly announcements are usually written up ~Thurs of the preceding week (to allow time for review, gathering images/screenshots, web staging, etc.). The timeline for putting together our post-release patch is very compressed, and some of these bugs didn't get fixed until shortly before Tuesday's release. The Cursecloth Wrapping and Dune Drifter bugs were literally fixed after the weekly announcements were published.

We do list all of the fixes in the patch notes: ...

We believe that the bug you're referring to was fully fixed in the same patch that released achievements. It's something we've been working on steadily, but it is unfortunately a mass of dozens of little cases, as opposed to one clear issue.

We think we've fixed them all, though. Are you still seeing this since the DFT release?