fix: synchronize modern movement input and rotation#3949
Open
iiroak wants to merge 12 commits into
Open
Conversation
iiroak
marked this pull request as draft
July 21, 2026 17:06
iiroak
force-pushed
the
fix/grim-movement-sync
branch
from
July 22, 2026 02:23
4e54c84 to
ba569d8
Compare
iiroak
marked this pull request as ready for review
July 22, 2026 05:55
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.
Summary
player_inputcontrol state when it changes on supported versions instead of sending a partial shift-only packet.This complements #3948. Modern prediction servers use
player_inputand packet rotation to simulate each movement tick; using a target yaw that differs from the sent yaw creates a persistent movement offset.Verification
npm run lintSimulationoffsets around.0131.