Closed OlegSmelov closed 9 years ago
Okay, I resolved the various issues that were causing these exceptions. The root issue is now properly written to the log as follows:
Bad pid (13) for event <class 'sc2reader.events.game.CameraEvent'> at 14.07 [13555].
I expect that this is related to the fact that it is a resumed replay. We don't properly use the player "rejoin" events to construct our player listings. Instead we use the initial player details that are never updated on resumed replays. I suppose we could call this a needed enhancement.
Closing this in favor of #91. This sort of enhancement falls under that general set of features.
Parsing this replay fails with the following exception:
GGTracker also fails to parse this replay, so I assume this has nothing to do with my OS/Python version/use case. This game was resumed from replay, so it might change some things internally.
This should fail:
sc2parse
output (not very helpful, cause tracker events):