force display 0xE0073 as a replacement character#185
Merged
sjrc6 merged 1 commit intoTaterClient:masterfrom Feb 14, 2026
Merged
force display 0xE0073 as a replacement character#185sjrc6 merged 1 commit intoTaterClient:masterfrom
sjrc6 merged 1 commit intoTaterClient:masterfrom
Conversation
b3520d5 to
5415f6e
Compare
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.
I've recently come across a player that visually had no name, did some digging and found out 0xE0073 does not seem to get rendered with Noto Emoji as fallback, this forces that character to be rendered as a replacement character