You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, I think it would be great if our legacy-to-json converter could accept these colours, using a custom syntax. Something like §#3f9718Green message could do, but if we decide to go this way, it won't be possible to use ChatColor.translateAlternateColorCodes to convert from &-based formatting to §-based, if using this feature.
But it would allow to use arbitrary colours in places where JSON format is accepted while being simple (e.g. in configuration files). With sufficient warnings, it could be really useful.
The text was updated successfully, but these errors were encountered:
Since 20w17a, JSON formatted content accept arbitrary fonts and colours (in hex), like so:
First thing first, we should accept those in
RawText
, with something like this:or:
Also, I think it would be great if our legacy-to-json converter could accept these colours, using a custom syntax. Something like
§#3f9718Green message
could do, but if we decide to go this way, it won't be possible to useChatColor.translateAlternateColorCodes
to convert from&
-based formatting to§
-based, if using this feature.But it would allow to use arbitrary colours in places where JSON format is accepted while being simple (e.g. in configuration files). With sufficient warnings, it could be really useful.
The text was updated successfully, but these errors were encountered: