Skip to content
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

No module named 'protocol80188' - Unpacking replay failed. #111

Closed
Kaszanas opened this issue Sep 5, 2020 · 4 comments
Closed

No module named 'protocol80188' - Unpacking replay failed. #111

Kaszanas opened this issue Sep 5, 2020 · 4 comments

Comments

@Kaszanas
Copy link

Kaszanas commented Sep 5, 2020

While testing replay parsing with s2protocol according to the documentation (https://github.com/Blizzard/s2protocol/blob/master/docs/tutorial_API.rst) using the following code:

import s2protocol
import logging
import mpyq
from s2protocol import versions
from settings import LOGGING_FORMAT

logging.basicConfig(level=logging.DEBUG, format=LOGGING_FORMAT)
archive = mpyq.MPQArchive('MyLegitPathToReplay')

contents = archive.header['user_data_header']['content']
logging.info(contents)

header = versions.latest().decode_replay_header(contents)
logging.info(header)

base_build = header['m_version']['m_baseBuild']
logging.info(base_build)

protocol = versions.build(base_build)

I was met with following error:

Exception has occurred: ImportError
No module named 'protocol80188'
  File "D:\Projects\SC2\testing_s2protocol.py", line 19, in <module>
    protocol = versions.build(base_build)

If anyone is willing to provide more information as to how to resolve the following problem I would appreciate that greatly.

@amartin916
Copy link
Contributor

Copy and past the previous protocol file and rename it to protocol80188 and you will be good to go

@Kaszanas
Copy link
Author

Kaszanas commented Sep 5, 2020

@amartin916 Thank You very much for such a quick response this seems to be connected with issue: #110
Are You sure that nothing changed internally between those versions?
It might be a good idea to introduce a Pull Request for that.

I will try this solution and inform You about the progress

@amartin916
Copy link
Contributor

they wouldn't accept the pull request, its an semi automated job that adds the protocol files and the next time they run it, it will be added. I don't ever poke my contacts at blizzards for protocol files that are duplicates of the previous version. And yes I'm 99.99% sure its a duplicate of the previous version, I have processed ~200k replays from this patch with no issues reported to me.

@Kaszanas
Copy link
Author

Kaszanas commented Sep 5, 2020

Thank You very much for the assistance @amartin916 :)
Indeed it seems to be working correctly at this point.
I am closing this issue.

@Kaszanas Kaszanas closed this as completed Sep 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants