You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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!).
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.
The text was updated successfully, but these errors were encountered: