Improvements to MessageTranslator #3803
Merged
Conversation
This file contains 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
Konicai
added
the
PR: On hold
Konicai
removed
the
PR: On hold
|
Maybe not, for the case of the weird legacy hex format. |
Camotoy
approved these changes
Aug 15, 2023
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.
convertMessagetoconvertJsonMessagewhere the String parameter is strictly a json stringconvertMessageLenientwas deserializing legacy java messages to a Component, then to json, then back to a Component (with the exact same gson serializer). That is no longer, and it no longer usesconvertToJavaMessage.convertToJavaMessagenow uses theBEDROCK_SERIALIZERthat has bedrock-unique colour codes registered to it.Closes #4017