devtrackers.gg
Sorry about that! There was an error that made Jump-In unavailable, but it should be back now.
Sorry about that! There was an error that made Jump-In unavailable, but it should be back now.
Feb 6, 19:00 UTC
Completed - The scheduled maintenance has been completed.
Feb 6, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 6, 00:08 UTC
Scheduled - @MTG_Arena maintenance will occur to deploy the 2024.34.0 game update, containing the Murders at Karlov Manor card set.
📥 Download required.
🔄 Restart required.
⏲️ ~3 hour estimated deployment.
📝 Patch notes soon after.
We're tracking a couple players in this stuck state today (including our head of production!). We're investigating, and expect to get this solved soon. You shouldn't need to do anything here; we think we can identify all the affected players.
Hi Jay, I realize you cant talk about upcoming changes to Timeless , but if combo becomes to prevalent/consistent in Timeless what is more likely: cards like Force of negation or new restrictions?
Philosophically, we would always rather see more cards available for unrestricted play in Timeless. Practically, we can implement a restriction much more quickly than we can add new cards to the game.
If there was a problem developing slowly, we would probably look for venues to insert counter cards. If a problem sprang up quickly and needed immediate reaction (dominating the meta, ruining diversity, etc.), we would almost certainly need to restrict something to control it.
How's that disclaimer go? Certain information set forth in this post contains “forward-looking information”, including “future-oriented format information” and “format outlook”, under applicable securities laws (collectively referred to herein as forward-looking statements). Except for statements of historical fact, the information contained herein constitutes forward-looking statements. These statements are not guarantees of future performance and undue reliance should not be placed on th...
Read moreThanks for bringing the metagame challenges back as they were great. Are there plans for any upcoming restriction announcement for Timeless? Also are the STX, MOM, WOE packs going to allow the banned cards to be opened with the patch release of MKM. Or will there be an announcement about when that is to happen?
Timeless: We don't normally forecast upcoming ban or restriction announcements (or lack thereof). I will say, though, that we're finding the Timeless metagame to be generally balanced and diverse so far.
Backlist packs (like STX, MOM, and WOE) will not get their collation adjusted for MKM, but we expect that to come with Arena's next major release, MKM's Alchemy drop. We'll certainly announce it in the patch notes when it changes
It would be interesting to see how popular historic is after timeless introduction. I for one immediately deleted all my historic decks and haven't played the format ever since.
The combination of no fetchlands, which means pretty bad manabases, and the fact that the threats are way stronger than answers makes the format pretty unfun, gameplay wise.
Not to mention a bunch of cards are still nerfed to unplayable for no good reason.
Both Historic and Timeless have their fans. We love both formats equally, but Historic remains (by far) the more-played format.
So the set is coming out tomorrow, but we still don't even have any information about prebans in Historic. Or have they just abandoned the format entirely, given that two combo decks have been making the format miserable for months and nothing has been done about that?
We intended to have Historic pre-bans called out in this article, but the blurb got lost somewhere. We're trying to find it. (Edit: Article is now updated)
In any case, it's what you probably expected: Show and Tell is banned in Historic. No other pre-bans or pre-restrictions.
Does this work for previous sets or only Karlov Manor?
Only for Murders at Karlov Manor
Sorry for the error! We just fixed things, and you should now be able to redeem up to 5 prerelease codes
It's a bug that only happens on certain battlefields; we're working on a fix
This is a graphical error caused by our last update, which changed a bunch of graphics internals. We should have a fix for this out to players soon.
Its caused by the new engine update, they are working on fixing it.
We are aware that this change caused a number of issues, mostly visual, for players, and we're working quickly to get those addressed. We don't have a specific date for each item, but you should see some fixes starting with next week's release of Murders at Karlov Manor. Please continue reporting bugs through our bugs & feedback site.
Came here to say this; you're exactly right. We don't have a fix for this one in-hand yet, but we're aware and actively working on it
Jan 30, 22:00 UTC
Completed - The scheduled maintenance has been completed.
Jan 30, 19:01 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 30, 18:20 UTC
Scheduled - @MTG_Arena maintenance will occur to deploy the 2024.33.72 hotfix on the following platforms: Windows, macOS, Android. This update contains fixes to keep Sparky from getting too excited.
📥 Small download required.
🔄 Restart required.
⏲️ ~3 hour estimated deployment.
Not sure if you've seen this, but thought I'd pass it on
Yup, that's on our list!
Oh dear, multi-shader interactions sound combinatorically nightmarish and really hard to unit/integration test to boot.
I wonder if this is a job for ML, at least in the long run? Train image classifiers on various UI elements (arrows, mana symbols/card text, approximately how various cosmetics ought to look...), then record known-good confidence values for a wide range of gamestates across different battlefields and cosmetic combos; to run tests, load up those gamestates, fuzz across a wide variety of battlefield/cosmetic combos, send a screenshot from each to the classifier, and investigate further if it's not confident enough that it saw the desired UI element. Obviously not going to catch everything, but seems like a good first line of defense?
We're actually working on building out full-cardpool visual diffing tools to catch at least the basic (i.e. non-combinatorial) level of this problem. It caught many, many bugs with this renderer change that we were able to fix before release, and is something we'll continue to build on, likely in some of the ways you describe
Read moreAs someone who's worked with Unity before, upgrading to a new Unity version is absolute hell. My guess from the bugs I've been seeing is that something changed about the render pipeline that's breaking their shaders or something. (I've been seeing two classes of problem: transparent things either being the size of their whole texture, or being almost invisible (targeting and attacking arrows); or things rendering in front of things they should be behind.) It's kind of impossible to upgrade your Unity version without a bunch of stuff breaking, and frankly we're lucky they managed to keep it to visual stuff.
With the sheer number of cosmetics and cards with unique animations, it would take massive amounts of resources to find all the visual bugs, so I can understand why they'd choose to let bug reports take the lead. That said, the fact that targets and which creatures are attacking what planeswalkers are really hard to see is kind of inexcusable, they should've playtested enoug...
Ding ding ding! 'twas URP. (And many of the missing visuals do seem to be about at least multi-shader interactions, with some looking card/driver specific, which is Much Fun.)
None of it is inherently tied to fixing Sparky, but the fix to Sparky was waiting behind it in the release pipeline.
I just dont understand how this happens
are the cards not just images?
how is just the text missing?
No, the cards are much more complex than "just images". Images wouldn't localize, dynamically update pinline colors as colors (or basic land types) are added, adjust to show gain/loss of legendary, etc.
Whenever i play bo3 and want to see the last game state during sideboarding all i get is a black screen. Am i the only one?
Playing on steam client and tried to verify integrity files but no luck there.
We are aware and investigating this. I was talking to engineers about it an hour ago, in fact.
This is one of the issues we are prioritizing fixing
Jan 29, 19:00 UTC
Completed - The scheduled maintenance has been completed.
Jan 29, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 26, 23:45 UTC
Scheduled - @MTG_Arena maintenance will occur to deploy the 2024.33.71 game update, on the following platform: iOS. Due to a back-end system update, players on impacted platforms should expect a large download once maintenance has concluded.
📥 Large download required.
🔄 Restart required.
⏲️ ~3 hour estimated deployment.