fix: wrap SetReader with fullReader to fix large packet read issues #615
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
When
SetReaderis called (e.g., after enabling encryption), the new reader was not wrapped withfullReader. This caused incomplete reads for large packets because a singleRead()call may return fewer bytes than requested.Problem
The
Decoderuses afullReaderwrapper to ensure complete reads viaio.ReadFull:However,
SetReaderdid not wrap the new reader:When encryption is enabled,
SetReaderis called with acipher.StreamReader, losing thefullReaderprotection. This causes large packets to be read incompletely, resulting in connection drops.Fix
Wrap the reader with
fullReaderinSetReader():Testing
Tested with Syncmatica mod which sends large plugin messages (~100KB+) for schematic sharing. Before the fix, players were disconnected immediately after attempting to share schematics. After the fix, schematic sharing works correctly.
Related Issues
Likely related to #587 (large modpack disconnection issues)