I updated from a prior version and I just tried to get in and it crashed and sent me back to home screen as well
Are you stuck in a loop of crashes, or were you able to get in properly after the one?
I updated from a prior version and I just tried to get in and it crashed and sent me back to home screen as well
Are you stuck in a loop of crashes, or were you able to get in properly after the one?
Apparently it's engine level stuff with Unity according to WotC_Ian in discord.
True Facts. This is not the Sparky fix, which we're still working to deliver. Getting this release out was part of what's blocking that, but there's one other thing we need to resolve.
We're seeing this in our post-release data (though we didn't see it in our testing). Can you give me any details on your phone model or Android version? Did you update from the prior version or was this a fresh install?
Thanks for confirming that. Whenever I run into someone who blatantly ropes I report them.
Follow-up question. Most of the time I also record my matches. If provided a link, would a WotC employee check the video as well or is the log file sufficient enough?
Log file is fine. We can pull the data on the match if we need it (how many times your opponent roped, etc.), which is easier & faster than reviewing a video
This is a pretty big waste of your time though considering WOTC has stated that they don't take actions based on these reports
I don't think we've ever said that, and if someone did they were wrong. The main way we penalize this behavior is through automated detection & banning (it's easy for a computer/script to identify players acting like OP describes), but we do use conduct reports as well
Royal assasin is one of my fav cards. Along with [[avatar of woe]]
I have a Royal Assassin sitting right behind me, framed alongside some other favorites from those early days (an Icy Manipulator and a Hippy)
Jan 17, 18:10 UTC
Completed - The scheduled maintenance has been completed.
Jan 17, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 17, 15:53 UTC
Scheduled - @MTG_Arena scheduled maintenance will occur to deploy the 2024.33.65 game update. This is a backend system update, and no downtime or player impact is expected though may occur.
⏲️ Full deployment estimated at ~3 hours.
🛠️ No downtime is expected.
Gamble, Show and Tell, Ghostly Prison, Fabricate and Victimize are definitely coming.
Crashing Footfalls might not come to Arena since it has a unique mechanic that doesnt exist on Arena.EDIT: ALL OF THEM ARE COMING
Yes, all Special Guests are coming to Arena. As usual, there may be some cards that are pre-banned or pre-restricted in different formats, based on power level.
Jan 16, 19:30 UTC
Completed - The scheduled maintenance has been completed.
Jan 16, 16:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 16, 14:10 UTC
Scheduled - @MTG_Arena maintenance will occur to deploy the 2024.33.60 game update.
📥 Small download required.
🔄 Restart required.
⏲️ ~3 hour estimated deployment.
📝 Patch notes soon after.
Hi all,
Seeing some questions around this so wanted to provide guidance:
Jan 9, 19:30 UTC
Completed - The scheduled maintenance has been completed.
Jan 9, 16:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 8, 22:06 UTC
Scheduled - @MTG_Arena scheduled maintenance will occur to deploy the 2024.33.50 game update. As part of this maintenance, players will be unable to perform monetary transactions for approximately one hour (8:30 - 9:30 am PT).
No other impact is expected, and players should still be able to spend gold/gems to enter events, etc.
⏲️ Full deployment estimated at ~3 hours.
🛠️ Store downtime is expected.
How do these responses interact with gameplay? Is there a slider that self adjusts in-game so you play different player/deck type or difficulty? Or are the polls evaluated on your end and then changes made with a patch?
The latter one - Your answers (or skipping) won't have any direct impact on your play experience, but we use them to do things like understand how much different players like different types Mid-Week Magic events, etc.
Hi Jay, sorry to reach out like this but I tried the Arena accounts on Twitter and didn't get a response.
In the Profile -> Set Collection screen, the release date for original Ixalan is incorrectly set to September 29, 2018 instead of 2017. As a result, this puts it between M19 and GRN instead of at the very bottom where it should be, since it was first set to "offically" be on Arena. I know it doesn't really affect anything, but it still bugs me whenever I see it. Can you or someone on the team address this?
I'll pass that on, thanks!
Hi Jay! Can you confirm that packs no longer consider Bolt/Ragavan/Necropotence/etc to be banned? I saw a Discord message to that effect but wanted to confirm. Sitting on a few WOE packs and I'd like the best chance to pull Necropotence!
Backlist packs (like STX, MOM, WOE, etc.) should be getting their collation adjusted with MKM's release. Fetchlands currently appear as normal in KTK packs.
You'll want to sit on those WOE packs a little bit longer :)
33.10 was a services-only update, yes. No new client to download
So basically they stored some deck attributes as cards as a quick fix because their deck model doesn't have dedicated properties for those attributes. Just like they store alchemy cards as A-card name because their card model doesn't support versioning. Seems very much like a tech debt to me.
The specialize thing is a bit of a hack, agreed. A- for Alchemy cards was carefully considered, though. It would have been easy to add versioning to our data model, but think of all the different places you encounter Magic decklists - random websites, screenshots, simple text files, etc. There's no way to add versioning support to all of those, so we wanted a solution that was backwards compatible with all the ways Magic decklists get used. Leveraging a change to the name there seemed like the cleanest approach, given the full constraint set.
Dec 14, 23:30 UTC
Completed - The scheduled maintenance has been completed.
Dec 14, 19:30 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Dec 14, 19:13 UTC
Scheduled - @MTG_Arena scheduled maintenance will occur to deploy the 2023.33.10 hotfix.
⏲️ Full deployment estimated at ~4 hours.
🛠️ No downtime is expected.
💻 Restart recommended.
📝 Patch notes available soon after.
very much looking forward to your article next week on what happened and how it was fixed
Short version, since (given holidays) I'm not sure when/if we'll get a longer article out:
With the KTK/Timeless release we added support for the restricted list. As part of this, we added a new chunk of logic to our deck validation code to look over each card in the deck, check whether it was restricted, and, if so, check that it met the count restrictions.
While doing this check, the code makes the seemingly simple assumption that everything in your deck is a card. Now, this sounds silly - what else would you put in your deck that's not a card? But, internally, we have a lot of data that looks & acts like a card, but isn't really a card. Tokens are an obvious example, but there are also things like the spell portion of an Adventure card, or something like Ribbons (from Amonkhet's Cut // Ribbons), or the back side of a traditional double-faced card, etc. There are lots of these, but they shouldn't ever be part of a deck directly. You don't put Stomp in your ...
Read moreMac - It's still acting up. It takes 2-3 tries to connect. I manage to get one game in then ... https://ibb.co/VCdZzD3 (image)
Never had this issue before. Been playing consistently for the past few months.
This sounds like a separate issue from the one we fixed, which was a fully consistent lockout (would never connect no matter how many tries).
Is it possible that there is something wrong with the internet connection on your Mac?
Is there an ETA for fixing Direct Challenge too? I haven't been able to play with my friends for an eternity, which is the only reason I play(ed) at all.
We've got a hopeful fix for DC issues in this release as well! We've had trouble repro'ing the issue, and though we've gotten some issues to repro now, we're not sure we're seeing exactly what players are. We've fixed at least one bug that could cause the problem you describe, so give it another shot and let us know how it goes.