Magic The Gathering: Arena Dev Tracker

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?

This should be fixed with this morning's update

This update does not. There are changes we want to make there in response to the feedback, but they didn't make the window for this release

Brawl matchmaking should be fixed in tomorrow's release

That must have been one very mossy hydra. Thankfully, errors like this should be solved in tomorrow's update, and you all should be free to exceed the bounds of a 32-bit signed integer, reality, and Sparky's patience once again

As others have pointed out, this is because you need the "right" version of the card to apply the style to. This is something we want to change about the system, but change it requires a large amount of surgery. We're working on it.

This achievement is currently bugged, and will not trigger in any game mode. We’re working on a fix and should have that available soon.

Once it’s fixed, it will require a matchmade game (not Sparky, not direct/friend challenge)

The backend uses (effectively) arbitrarily large numbers. The client can sometimes have display issues, because it generally assumes the numbers will stay between +/- 2 billion.
This is usually a safe assumption.
Usually.

Thanks for the report! We're looking into this, and we are seeing signs of problems like you describe, with decks matching out-of-band more often than they should.

This is not an intentional change, and we are digging in to see what's going on.

Packs should have just gone out - if you don't see them in an hour or so (from this post time), contact CS

Packs should have just gone out - if you don't see them in an hour or so (from this post time), contact CS

That’s hilarious. Integer overflow problems have integer overflow solutions

This is correct (and you nailed the percentage; well done!)

This is, uh, not intended behavior. Our engineers are on the case. Did you happen to gain an insane amount of life in one game?

It is a thing we like to do when we can. Sometimes we don't have bandwidth (for DSK we were focused on Pioneer Masters instead), and sometimes we'll focus that bandwidth elsewhere (for BLB we did the Courageous Critters instead), but we try to include the face commander cards.

Maybe....