fix(velocity): restore packet length framing for 1.7 clients - #729
Open
dominicanish wants to merge 1 commit into
Open
dominicanish wants to merge 1 commit into
dominicanish wants to merge 1 commit into
Conversation
Restore the VarInt packet length prefix after ViaRewind replaces Velocity's compression encoder with ForwardMessageToByteEncoder. Without the length prefix, 1.7.x clients receive unframed packets and fail during login with "Bad packet id" errors. Verified by reproducing issue ViaVersion#616 and confirming that adding the packet length framing allows a 1.7.10 client to proceed: ViaVersion#616
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
1 participant
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.
Restore the VarInt packet length prefix after ViaRewind replaces Velocity's compression encoder with ForwardMessageToByteEncoder.
Without the length prefix, 1.7.x clients receive unframed packets and fail during login with "Bad packet id" errors.
Verified by reproducing issue #616 and confirming that adding the packet length framing allows a 1.7.10 client to proceed.