Wow, did it really take almost a year to code this?
Of course not! I've just been dragged over to some real life experiences... you know how it is.
But behold! The Database configuration backend functionality is now in (as is compatibility with Spigot 1.14 and 1.15 - sorry for this delay)!
Here's the changelog:
Version 1.9.0
=============
New major version
Breaking Change:
- due to many problems trying to compile AdminAnything in Java 7 in my current IDE, this plugin is from this point on only compatible with Java 8+, meaning I'm dropping support for Minecraft versions 1.6 and earlier. Sorry guys, however it seems like the whole world now moved on to Java 8 in the meanwhile

Fixed:
- compatibility with Spigot versions 1.14.4 and 1.15.1
- all AA commands work for commands without parameters again
- the initial blocking update check for AdminAnything was replaced by one that does not pause the server until AA gets response back from Spigot
- default listing options for /aa_listcommands in the config file are no longer ignored
- /aa_pluginperms now lists descriptions from the internal permissions file correctly (without an initial "=" sign)
Added:
- AA configuration now supports MySQL databases. This means that you can share your AA config among multiple servers without the need to manually rewrite all config.yml files and do an /aa_reload on each of these servers afterwards.
File-based configuration is still supported, so you can choose which one to use.
- Some rules that apply for DB-backends when upgrading your AA version:
- plugin's config.yml file now only contains a single option: configBackend (set to "file" for file-based, "db" for db-based configs)
- plugin's normal (file-based) configuration file is renamed to config-file.yml
- if you want to use db-based configuration, set configBackend in the config.yml file to db and update your config-db.yml file with your connection settings
- db-based config is basically a YAML file representation in the database, so you're free to edit it there and all instances of AdminAnything will pick it up every sync_check_interval_seconds seconds (option in config-db.yml)
- all existing configs are automatically inserted into the database upon first run with db-based configuration enabled
- you can update your config-db.yml and config.yml and simply do /aa_reload for all this to work, there's no need to restart your server
Well, that's all folks. Enjoy
