-
Notifications
You must be signed in to change notification settings - Fork 142
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
Error on opening co-op replays in 1.6.0 #126
Comments
Thanks for sharing the detailed report. Just to confirm, you said this wasn't happening on 1.5.0 for you, right? I tried running this same replay on v1.5.0 2ee6974 and got this
Obviously we still need to fix this, but I just want to make sure we're seeing the same regression |
Yes, that's correct, I got the same error when trying to open 5.0.x co-op replays in sc2reader 1.5.0 (though 4.x.x replays worked fine, so I assume it was due to whatever changes in the replay format were introduced by that update). |
Interesting. It looks like Thankfully, the original maintainer wrote a script to do this for us fe2a376 The next step would be to get a .s2gs file, with instructions for that at https://tl.net/forum/starcraft-2/330926-s2gs-file-a-fun-little-mystery-for-us Unfortunately I don't have access to the StarCraft 2 client at this very moment to do this, but I'll give it a shot later when I do |
Potential fix in #129. Does that work for you? |
Yup, that did it, scanned 1,139 co-op replays with no errors. Thanks! |
Using the latest version of sc2reader available on PIP, sc2reader chokes when opening co-op replays that use factions besides the standard multiplayer ones. I did not encounter this error previously on version 1.5.0.
Here is a sample replay.
Here is a simple test script that uses that replay to demonstrate the issue:
It gives me the following error when executed:
The problem seems to be that the "InfT" (Infested Terran) race used on the Miner Evacuation mission is not in the "attributes.json" file (which only has the standard Terran, Zerg, Protoss, and Random), so its presence in the replay file causes a key look-up error.
I looped through all of my co-op replays and found the following non-standard races that cause read errors:
I don't know if this is an exhaustive list, but it's a pool of over 1,000 co-op replays.
I would guess that either adding these races to "attributes.json" or implementing some sort of fallback to prevent a fatal error if a non-standard race can't be identified would fix this issue.
Edit: Using sc2reader 1.6.0, Python 3.8.5, Mac OS 10.14.6.
The text was updated successfully, but these errors were encountered: