The current license headers are either outdated or missing completely.
While updating those, it would also be wise to discuss who should be in said license headers. Should we use one for com.almightyalpaca and another one for com.kantenkugel? Or just a combined one for both packages?

Additionally, due to me having my preferred code style placing { on same line, and IJ sometimes not remembering that I set a project-specific code style, some files have brackets placed on same line (sorry).

Considering updating the license headers will change most if not all files anyway, this would be the perfect time to also change the code style to use uniform bracket placement (I'd go with next-line bracket, like used by most of com.almightyalpaca's code already)

I'm hosting my own instance of butler on a server. And since I'm planning to make that instance run with docker instead I thought that I might as well make the config accept env vars with a program flag.

The idea is that by running java -Dconfig_type=env -jar Bot.jar it will switch the way it loads any configurations and parse them from the env instead.
The env keys will most likely be prefixed with BUTLER_ (eg BUTLER_BOT_TOKEN=....).

I'm also going to make a wrapper class that can serialize and deserialize the JSON config when the config type is not set to env.

I made this issue to track any ideas and must-haves before starting.

In the example pom.xml that you get when executing !pom.xml on discord both maven-compiler-plugin and maven-shade-plugin are not on the latest version. Could be irritating for new users since it seems like it'd throw an error. And I thought since you already create a new Hastebin file and get the version of the jda everytime the command is called it shouldn't be that much of an effort, but could be very useful.
Thanks in advance! :)

... as title says

I'm a stupid fool