AliienChatColor 1.5.2

- 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