-
Notifications
You must be signed in to change notification settings - Fork 12
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 changed in 2019-11-21 patch #19
Comments
I changed the code to work for both the old and new log versions. This should return a card object, but returns a string: Seems like a potential bug in the python-mtga. For now I am double checking if the instance is correct and issue a warning. |
I switched to Python 3 and latest python-mtga and the id 70361 works fine now:
|
Looks mostly good to me. One small issue I found: the keyword matching matches prefixes, so if there were two responses in the log for (say) |
The 2019-11-21 patch to the client has changed the log file format so that the whole JSON response is on one line, rather than containing newlines:
(response clipped for clarity). This breaks the logfile parsing... it should actually make the parsing easier as we can throw away that clunky brace counting.
I'll try and come up with a patch in the next couple of days if you don't get one in first :-)
The text was updated successfully, but these errors were encountered: