Expand component support and the ChatCode API

[FranKusmiruk]

Description

Since Spigot/Paper is starting to use components in more and more places, we need to add support to use it. Right now, we only support components in chat messages, but this is also supported in the following:

• item names & lore
• entity names
• action bars
• Inventories Add chat format support for inventories #5841
• titles
• scoreboard objectives

And over all, we should standardize a way to pass around components in a way addon developers are able to use them as well, it's only possible to access them internally as of now. The best way to do this would be expanding the ChatCode API to allow chat codes be parsed in any string, this way we can also introduce things such as <nl> for new lines in Skript.

[APickledWalrus]

With my work in #3098, I’d be happy to continue working in this part of the plugin and tackle parts of this.
EDIT: Just noticed the "core task" tag haha.

[Moderocky]

I think this would be a good opportunity to also add support for some of the other component types, such as translations and keybinds. It might be worth just adding them all :)

Note that there are now options for other things in the "hover event" (tooltip) such as items and entities, so this could be added as well. Minecraft has support for a few other things here (such as NBT), but I'm not sure how many of them made it into the chat component API yet, and they might be better suited to addons anyway.

If other component types were to be implemented (translations, etc.) how would you see the pattern working?

[FranKusmiruk]

With my work in #3098, I’d be happy to continue working in this part of the plugin and tackle parts of this.
EDIT: Just noticed the "core task" tag haha.

I should've been more clear with the core task is more of a warning that implies the feature or whatever is being worked on needs of a considerable amount of planning and clear design choices before going to the implementation, and that requires some understanding of Skript to be done hence why it is labeled as such. We still appreciate any kind of input, and almost all discussion is done at #skript-dev in Skript-chat so you're more than welcome to tell us your idea on the matter.

I think this would be a good opportunity to also add support for some of the other component types, such as translations and keybinds. It might be worth just adding them all :)

I was planning on adding those features as well, will edit the main issue accordingly.

Note that there are now options for other things in the "hover event" (tooltip) such as items and entities, so this could be added as well. Minecraft has support for a few other things here (such as NBT), but I'm not sure how many of them made it into the chat component API yet, and they might be better suited to addons anyway.

If the implementation of those features is solid enough at the moment (it has always been available but the component API didn't have proper support for it), we should allow the usage of them as well. The only issue I see is the fact that items/entities are things that may be only able to be converted to a component at runtime, we'll have to figure out a way to create the hover event at runtime (right now all components are created at parse-time) and that'll require some modifications to the current API as well.

If other component types were to be implemented (translations, etc.) how would you see the pattern working?

The current pattern is working pretty well, but we or addon developer may introduce some other advanced features such as the ones provided by the library MiniMessage, which is something to think about when designing this.

[legofreak1999]

I can't seem to find the #skript-dev channel. But this propably won't help since its paper but here u can find a little list if something got missed in the progress. Paper issue

[FranKusmiruk]

With Adventure being part of Paper now, we may as well just use MiniMessage instead of our chatcode API, it's still open for discussion though