Permission Signs | RGB | 1.20-26.1

This update supports Minecraft 1.20 and above. The main change is that right-clicking a permission sign will not show the sign edit prompt. Furthermore, all sign-related code has been changed to the new 1.20 sign API.

You can see the full changelog below. The main things to notice is that permission signs now support setting a description to better describe what is bought. The plugin should work without any problems on 1.19.1. Custom strings should no longer be garbled. You are no longer forced to buy a permission if destroying a permission sign in survival. Changes: * Removes the need for sneaking to destroy a permission sign if not in creative. * Adds a description to permission signs, which allows a longer description of the permissions given to the user. * Adds the ability to use underscores as spaces in descriptions, and using \_ to use actual underscores in descriptions. * Prevents double-clicking of permission-signs when holding an item. * Stores some default strings as multi-line YAML for easier readability * Uses UTF-8 for custom language file to prevent broken text for foreign characters. * Reduces priority for protection event to lowest to allow other plugins to do their job first * Updates some dependencies, including building against Spigot 1.19.1. * Clarifies the license as GPL3

This update allows hex color codes to specify RGB colors in strings.yml. More customization is now possible as the sign name, sign cost, sign duration and permission list can be formatted however you want. Want to display cost as currency-cost instead of cost-currency? You can now.

The "code" used for specifying that a permission should be applied to all worlds was specified as "all", but was "any" in the documentation, so this update makes both valid.

This update adds the proper URL for checking for available updates as I couldn't add it without knowing the resource ID.