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

v183+ GMS incorrect outbound opcode #20

Open
BobNigers opened this issue Mar 3, 2017 · 4 comments
Open

v183+ GMS incorrect outbound opcode #20

BobNigers opened this issue Mar 3, 2017 · 4 comments

Comments

@BobNigers
Copy link

This issue has been happening since v183.1.

Unable to see the correct outbound opcode.
The packet structure seems fine.
The opcode changes each time upon channel change.
It seems to affect only the outbound opcodes that are used for the channels.
The login outbound opcodes are proper and don't change.

@diamondo25
Copy link
Owner

Yes, Nexon has implemented an opcode crypto. I am currently unable to help with this issue, as it would require some major changes to the codebase, possibly adding realtime packet handling (would help with logging things like drops in realtime, too!).

@BobNigers
Copy link
Author

can you provide code for opcode crypto like from ida?

@diamondo25
Copy link
Owner

Nope, because its obfuscated.

@gigibader
Copy link

Now that a v188 Unvirtualized Client has been released will this issue be fixed?

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

3 participants