Fix display/custom name for entities#8381
Merged
APickledWalrus merged 2 commits intoSkriptLang:dev/patchfrom Jan 21, 2026
Merged
Fix display/custom name for entities#8381APickledWalrus merged 2 commits intoSkriptLang:dev/patchfrom
APickledWalrus merged 2 commits intoSkriptLang:dev/patchfrom
Conversation
APickledWalrus
approved these changes
Jan 16, 2026
Efnilite
approved these changes
Jan 17, 2026
erenkarakal
approved these changes
Jan 21, 2026
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
4 participants
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.
Problem
display name of entitywas returning the CommandSender#getName() value, which is not the same as the Nameable#getCustomName() value previously returned without type properties.Solution
Ensures display/custom name use getCustomName
Testing Completed
manual verification
Supporting Information
Completes: none
Related: none
AI assistance: none