Kezz
Kezz
The Adventure API does not have any representation of an "item" and therefore there is no support for such a thing in adventure-platform. 1.7.10+ is supported, but that doesn't mean...
> Major in terms of the next game drop or 1.22? 1.22 yep.
> Will the LegacyComponentSerializer be removed? No. We do not intend to remove support for legacy serialisation, despite it not being recommended for use. In your case, use adventure-platform-bukkit for...
> `LegacyComponentSerializer` Has some valid use cases IMO. Like sign formatting for example. Signs have supported components since 1.8. > Inline sound events do not have keys I'm unsure exactly...
Ignoring the fact that a) constructing CraftSound instances is not supported and b) the code snippet you provided clearly has a key that just isn't being passed along, Adventure does...
Then what you have noticed there is a Paper issue due to the reasons I mentioned above.
> Wouldn't it be the simplest for the platform to change the effective locale from the pointers `Identity.LOCALE`? This isn't a great idea because of a) the confusing nature of...
> Why not do something like Audience#audience(Locale, Audience...) or Audience.Builder#pointer(Identity.LOCALE, Locale.US) then? Yeah I did consider this but in this example both points a and b still apply.
Regardless of the exact wording of the Javadoc, it's abundantly clear that `Identity#LOCALE` points to the Locale the player has set, as it has done consistently for almost four years...
~Currently blocking on on https://github.com/KyoriPowered/adventure/pull/354.~