We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
My 5-year-old daughter asked to play Starcraft! So we create an account for her and do the Spawning Pool thing.
Here's the replay: http://drop.sc/341365/d
Sadly it can't be parsed due to some nasty issue with unexpected pids, which I believe is the same as the issues discussed here: Blizzard/s2protocol#8
Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/Users/david/Dropbox/Programming/esdb/esdb/vendor/ggpyjobs/src/sc2reader/sc2reader/factories.py", line 66, in load_replay return self.load(Replay, source, options, **new_options) File "/Users/david/Dropbox/Programming/esdb/esdb/vendor/ggpyjobs/src/sc2reader/sc2reader/factories.py", line 135, in load return self._load(cls, resource, filename=filename, options=options) File "/Users/david/Dropbox/Programming/esdb/esdb/vendor/ggpyjobs/src/sc2reader/sc2reader/factories.py", line 145, in _load obj = cls(resource, filename=filename, factory=self, **options) File "/Users/david/Dropbox/Programming/esdb/esdb/vendor/ggpyjobs/src/sc2reader/sc2reader/resources.py", line 308, in __init__ event.load_context(self) File "/Users/david/Dropbox/Programming/esdb/esdb/vendor/ggpyjobs/src/sc2reader/sc2reader/events/tracker.py", line 181, in load_context self.player = replay.player[self.pid] KeyError: 4
The text was updated successfully, but these errors were encountered:
Closing as a duplicate of #131.
Sorry, something went wrong.
No branches or pull requests
My 5-year-old daughter asked to play Starcraft! So we create an account for her and do the Spawning Pool thing.
Here's the replay: http://drop.sc/341365/d
Sadly it can't be parsed due to some nasty issue with unexpected pids, which I believe is the same as the issues discussed here: Blizzard/s2protocol#8
The text was updated successfully, but these errors were encountered: