Better Text Displays

- Made sure SkBee will no longer throw a warning in console regarding how the text displays are spawned. - Overall, the script should parse more quickly now.

This version of Better Text Displays will still work with most version of SkBee, however the updated /textdisplay list command requires the latest version (v2.18.1) to properly display the components in the hover event. Changes: · The /textdisplay list command will now list all currently registered displays in the chat. · Each item in the list can be hovered over and clicked. · Hovering will show some information regarding the display (at the moment, this is just the lines that the display has). · Clicking will suggest the command to remove the display.

Changes: · Made some small changes to give better feedback to the user when using the commands. There are now error messages for most, if not all, use cases of the command. · The /textdisplay list command now provides more information but is still not fully equipped. Will wait for SkBee update to make this change. Removed: · In v1.2, there was a system in place to save the UUIDs of all the currently registered text displays. I'm fairly sure this was completely unnecessary, as the UUIDs are saved now, as opposed to the entities themselves. This should result in a better parse time.

Rewrote the entirety of the script so that its more efficient, has more features, is easier to understand and use, and can persist through a server restart. Changes: · The command to create a text display has changed quite a bit. No longer do you have to write all of this nonsense /textdisplay with id yourID with text yourText. · It now follows the this syntax: /textdisplay <create / remove / addline / setline / list> <id> <text> · In v1.1, I tried making the entities persist through a server restart but failed as I only spent a minute or two thinking of ways to achieve this. In this version, they are now able to. · You can now create copies of already created text displays by using /textdisplay create <id of textdisplay to copy>. I'm not sure how intuitive this is though, so might add a copy argument to the command to do this instead. · Adding and setting lines of already created text displays is also something that is now possible. This is done by using the commands /textdisplay addline <id> <newLine> and /textdisplay setline <id> <line to set> <newLine> respectively. · Mini messages can now be used, as well as just the vanilla "&x" color codes, but not in the same line. This means you can now make the text <rainbow>, alongside the other mini message features. · You can still list the displays like before, but an update which will make this look nicer and be more useful will be coming whenever SkBee fixes the hover event syntax. Things that are not yet implemented but I plan on adding fairly soon: · The /textdisplay list command. As stated above, it'll work but it'll be cooler soon. · Better error messages for when you don't use the command correctly, or if you try to create a copy of a text display that doesn't exist, that kind of thing.

Made the id of the text display that is provided in the command unformatted, just as a safety measure.