fix: properly encode unicode codepoints outside BMP #497
+129
−21
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.

The BMP (Basic Multilingual Plane) consists of all Unicode codepoints from U+0000 to U+FFFF. For characters in the BMP, you can encode them with a
\uXXXXescape in both JSON and SNBT. However, characters outside of the BMP are encoded differently. In SNBT, you can use\Uxxxxxxxx(\Ufollowed by 8 hex characters); in JSON, you need to encode them as UTF-16 surrogates. With this change, mecha can now properly encode these characters.Fixes #496.