Repository navigation
Skip lookup of player names longer than 16 characters - #2328
Merged
Merged
Conversation
me4502
approved these changes
Nov 10, 2026
Member
|
Thanks for the PR! :) |
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.
Passing a name longer than 16 characters to region member/owner commands (e.g.
/rg addowner <region> <long-name>) causes Paper's profile service to throwIllegalArgumentException: Name cannot be longer than 16 charactersfromBukkit.createProfile, printing a stack trace instead of a user-facing error.Such names can never belong to a valid player, so
DomainInputResolvernow skips the profile lookup for them. They remain in the unresolved list and the command reports "Unable to resolve the names ..." as it does for any other unknown player.