Repository navigation
fix(minestom): preserve player profiles before entity spawn - #58
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
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.
Players could appear in the lobby tab list while their entities remained invisible. Rank formatting cancelled the original ADD_PLAYER packet during socket queue draining and appended its replacement after an already queued entity spawn.
Preserve the original profile packet and send rank decoration as a separate UPDATE_DISPLAY_NAME. This keeps profile-before-spawn ordering and preserves viewer-specific rank formatting without requeueing ADD_PLAYER.
Validation: the deferred-queue regression failed before the fix for both Java and Bedrock viewers and passes afterward. It checks profile/spawn ordering, a single ADD_PLAYER, and bounded display updates.
./gradlew spotlessApply test buildpasses (247 tests, zero failures). Independent code review found no actionable issues. Live Minecraft client verification remains pending.