v2.4
v2.4, friendlier setup and self updating config
Hi everyone, this is a fairly chunky update for SimpleCosmetics Enhanced. Pasting the highlights below so you know what is changing.
Commands cleanup
The /cosmeticsreload command is gone. Everything lives under /cosmetics only now, with proper subcommands: menu, clear, reload, update, version and help. Tab completion is also there, and admin only subcommands are hidden from non admin players. The CommandAliases list in your config.yml will finally register at startup, as it should have from the beginning.
Config gets smarter
The config will auto update itself using boosted-yaml from now on. So whenever a new key is added in a future release, it gets merged into your file properly, without wiping your edits or your comments. Each key has a short comment above it so you actually know what you are touching.
Few new options to be aware of:
TrailsMenu.ROWS: pick anywhere from 1 to 6 rows for the menu. Default is 4, so that the remove trail button at slot 31 still fits.BStats.Enabled: if you want to opt out of the anonymous metrics, just set this to false.Update.Enabled: this toggle was sitting dead in the config earlier. Now it actually controls the SpigotMC version check, as it should.
config.yml.example and readme.txt will both drop into the plugin folder on first start, for reference.
Permissions fix
simplecosmetics.use now defaults to true. So non op players can open the trails menu out of the box, no LuckPerms wiring needed for the basic case.
Compatibility
Supports 1.18 to 1.20.4 (Java 17). Runs on Spigot, Paper, Purpur and Pufferfish. Also fixed a long standing IncompatibleClassChangeError on inventory clicks by switching from the Paper API to the Spigot API. The /cosmetics update subcommand was also using the wrong SpigotMC resource id earlier, that is fixed too.
Other bits
There is a small ASCII banner on startup and shutdown now, with version and credits. bStats integration is wired (plugin id 31908), and as mentioned, you can disable it from the config itself if you prefer.
That is mostly it for 2.4. Drop the jar into your /plugins folder, restart the server, and please make sure the server is online on first start so that the library loader can fetch boosted-yaml from Maven Central.
Cheers,
zArrowTan