-
-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Legacy decode does not consider options of builder... #1116
Comments
What is the use case for this? Changing these defaults will likely break plugins currently in use. |
@zml2008 As mentioned above, we use it for converting chat colors. If a user types But it is disabled by default, the issue is just that is not checked on deserialize , only in serialize. |
Also the same issue exists with Kyori chat colors But currently it also works without enabling on deserialize. |
Why are you checking the style in the serializer, which is specific to the legacy format? You could just as easily strip formatting from the resulting component after deserializing (which would apply to any formatting option supported in the legacy serializer, not just the RGB colours). As-is, it sounds like you're asking for an incomplete solution that changes behaviour. If more flexibility were added, I think it'd make sense to be done similarly to the JSONOptions flags, where the default options are as-is, but individual options can be toggled to match specific game versions. |
Ahh ok, I see always de-serializer is a feature of this. Would it be fine to add something to the builder one could disable it?
Is that wanted? |
No. Please read what I said about the system that the gson serializer uses. |
Yes I have seen that. I just got a bit confused because Should in this case |
Hello,
I have build a serializes looking like this.
I wanted to use it to translate just ChatColors, but it still docdes stuff like this:
&x&f&f&f&f&f&eYour Text
Which I think should only work when
useUnusualXRepeatedCharacterHexFormat()
was used in the builder.The text was updated successfully, but these errors were encountered: