-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log file format broken by latest MTGA update #33
Comments
Seems like whole PlayerInventory section is gone from the log. So far we cannot do much until an equivallent is being logged by Arena. |
Yeah, that was my initial conclusion after looking at the log files I had last night - I hoped I was missing something but apparently not :-( I think I can reconstruct some of the functionality (e.g. the |
Small progress update: I haven't made any real progress on log file parsing, but have updated my fork of python-mtga to handle the changes in the latest Arena update (Wizards made a bunch of previously mandatory fields optional so we couldn't load the card database...) |
Has there been any progress or did the change break this project? |
I've looked at it, but don't believe the inventory is in the log :-( so yes, this does fundamentally break this major part of the project. AetherHub do manage to get the inventory somehow, but I don't know how they do it. |
@pak21 Untapped.gg seems to also get the card inventory somehow. I wonder how they do it. |
Any progress on this? |
@lanmaster53 Not from me I'm afraid, I've stopped playing Arena so this isn't on my priority list any more. |
If you've got any notes on what you've done to this point, I don't mind digging some more. All of the other agents are doing it somehow. They must be using a different log. I cannot find any evidence of collection cards in that log. |
Wizards broke the file format parsing again :-(
I will investigate, but due to Real Life I won't have a chance to look at it properly until Monday 2021-08-30. This has broken a number of the trackers as well, so it's not just us...
The text was updated successfully, but these errors were encountered: