Repository navigation
Fix OpenKore initialization by filtering Gepard control packets - #17
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The relay forwarded
0x4754and0x5395to OpenKore even though its selected RO packet table does not recognize them. OpenKore discarded the receive block containing the0x0AC4login response, preventing player position and entity initialization.Add both Gepard control IDs to the default drop list, document explicit overrides, and add regression coverage for fragmented packets, preserved login/position packets, and encrypted actor offsets. Verified actor recovery retains its existing behavior.
Validation:
bash scripts/test-offline.sh: PASS, 12 scripts.python3 scripts/validate-research.py: PASS.python3 scripts/validate-codex.py: PASS.git diff --check: PASS.