AliienChatColor 1.8.2

- Added 26.3 support
- Migrated some of the menus and logging logic to the updated AliienCore systems (this won't affect you in any way, it'll just make the code look cleaner for me)

- Added a new "/cc admin debug" command, which can be used to toggle the debug mode. This can be useful for finding what may be causing certain bugs (this required the "aliien.chatcolor.admin.debug" permission)
- Refactored/organised better some chunks of the codebase

- Added menu filters: now players can filter out their colors in the menu by all, owned, locked, purchasable, static (single color), gradient (multiple colors) and favorites (check the wiki for how to add the filter button to your current setup)
- Now players can favorite colors with the "/cc favorite <color>" (requires aliien.chatcolor.favorite permission, which is on by default)
- Now players can unfavorite colors with the "/cc unfavorite <color>" (requires aliien.chatcolor.unfavorite permission, which is on by default)
- IMPORTANT: Due to the new menu filters, I had to recod the way the plugin distributes the colors through the menu: now you have to select which slots you want your colors to go in, and the plugin will distribute them through those slots by the order they are set in the config, as well as automatically use multiple pages if needed. The plugin will automically convert your setup once you put the new jar in and reboot your server, but I'd still manually check "gui.color-slots" in gui.yml just to be sure and adjust if needed
- Added a new "/cc admin clearconfig" command, which is used to clear all the slot and page entries in config.yml since they are not needed/used anymore (the converter I mentioned in the previous point won't do this automatically for backup reasons, so once you are sure that everything is right I recommend you running this)
- Adjust the default colors so they don't come with a "slot" or "page" key
- Fixed that the "/cc hex <hex color code>" stopped having the example auto completions at some point

- Improved plugin performance, especially when players send chat messages.
- Made chat colors load and apply more efficiently.
- Improved how player-selected colors are remembered while they are online.
- Made reloads safer, so the plugin is less likely to behave oddly while configs are being reloaded.
- Improved how the plugin handles players joining and leaving.
- Improved reliability when saving or clearing a player’s selected color.
- Reduced unnecessary repeated work in the background.
- Cleaned up and reorganized internal systems to make future updates easier.
- The plugin is no longer guaranteed to support spitot/I am no longer giving support for it. Supported softwares are paper, folia and any of their forks.

- Fixed an issue with the folia support

- Added "/cc transfer (player) (color ID)", which allows players to transfer chat colors between them
- Added "/cc admin give (player) (color ID)", which allows admins to give players chat colors if they don't already have them (this is just the same as manually giving the permission, but it looks a lot cleaner)
- Added a new list variable in settings.yml where you can select chat colors that you don't want players to be able to transfer
- Changed the default priority of the async chat event from HIGHEST to NORMAL (to ensure more compatibility with other chat plugins by default, but this can still be changed in settings.yml)

- Added MariaDB support
- Removed a dependency/library I wasn't using anymore

- Now you can change the strictness of the contrast checked in settings.yml
- Added 26.2 support

- Added a contrast checker, so when players pick their own color using "/cc hex" they don't pick a color that is way too dark/unreadable (you can toggle this in settings.yml)
- Added AxQuestBoard hook, which can be used as a currency
- Added suffixes for each currency, which can be used with the %suffix% placeholder in GUI names, lores and purchasing messages
- Internal code changes

- Fixed an issue with the plugin not loading up in certain cases (IMPORTANT: IF YOU ARE USING A H2 DATABASE TO STORE THE PLUGIN DATA YOU'LL HAVE TO DELETE IT BEFORE REBOOTING/STARTING YOUR SERVER AFTER UPDATING)

- Now you can change the default value of the %aliienchatcolor_format% placeholder in the settings.yml file (including using colors if you want to)

- Added H2 database support
- Swapped the default database from SQLite to H2 (since it is faster)

- Now if vault does not have any permissions plugin hooked into it purchases won't be run, rather than running the color purchases and failing to give players the respective permission
- If a purchase cannot be handled due to the server lacking a permissions plugin with vault, it will notify all online players with the aliien.chatcolor.admin permission
- Now if you select an invalid storage type the plugin will throw a warning in console and default to SQLite, instead of just defaulting to SQLite
- Removed the aliien.* permission due to it being unecessary/confusing if you are using any other of my plugins (aliien.chatcolor.* is still available)
- Fixed the confirmation-gui.yml file failing to reload
- Other internal edits that won't make any difference to you, but will allow updates to roll out more easily in the future

- Added a confirmation gui for color purchases
- Added a toggleable option in settings.yml to toggle the use of the confirmation menu (I recommend leaving this on)
- Now you can use aliien.* and aliien.chatcolor.* permissions to grant all plugin perms
- Now you can use aliien.chatcolor.admin.* to grant all admin perms
- Recoded the way commands are handled to be a lot cleaner
- Fixed an issue where the plugin would say it'd hook into vault 2 times

Important: vault is now a required dependency if you want to use the new features (if you don't you can still use this update with them disabled and not have vault)

- Added new economy option to make chat colors purchasable through the main menu, which should support 99% of the economy plugins out there, and even custom-made ones (read the documentation for how to use this)
- Optimized the way the plugin handles opening the main menu (it should be a lot faster now)
- Optimized the way the plugin saves active chat colors
- Added %aliienchatcolor_purchasable_<color>% and %aliienchatcolor_is_purchasable_<color>%, returning "True" or "False" if a color is purchasable or not
- Added a toggleable logs file, which logs when a player purchases a chat color into a .txt file
- Changed the default storage option from PDC to SQLITE
- Added a few just-in-case features in case you accidentally misconfigure a chat color
- Fixed a bug where chat colors would be blindly saved into memory even if they were invalid
- Fixed a few GUI row-mismatch edge cases
- Refactored a good chunk of the code

- Fixed a bug that would make the plugin not load in certain cases

- Internal optimization changes.
- Updated dependencies.
- The plugin will now generate an "AliienCore" folder inside your /plugins folder. Please ignore this, as this was done to reduce the plugin's jar size by a lot.

- Added MySQL and SQLite support to save player data (as well as PDC, which is what it was before) - This can be changed in the settings.yml file to whatever option you want
- Added 26.1 support
- Changed how sounds are setup in the settings.yml
- Now you can change the number of rows of the colors menu
- Added an optional messages prefix
- Hooked the plugin into bStats
- Recoded a few things

- Now you can use individual lores to override the global lores option (if you don't want to override, just don't set a specific lore for your items)

- You can now use custom-model-data to set custom model data for all the menu items

- You can now add item flags to the menu items

- Added a new %aliienchatcolor_name% placeholder, which displays the full colored display name of the chat color that the player is using

- Added a new %aliienchatcolor_is_hex% placeholder, which returns True or False if the player is using a custom chat color set with /cc hex or not

- Migrated certain features to my own library

- Rewrote a few small things for organisational reasons