freya02

Hey, perhaps you could use the 2nd button to open the file being edited (if not ignored by VCS) This *could* lead to 404 errors if the file was not...

I may also suggest changing the `convertKey` method to use `key.toString().toLowerCase(Locale.ROOT)` to convert the non-null key, instead of the char loop. Benefits include better performance (measured a 2 times increase...

You can actually automate this on Windows by compiling a resource script using `rc.exe` and using `cvtres.exe` to convert the output file into an linkable object, you then only have...

I don't really see how this is a valid use case tbh

Why not have the options right on the first time ? you could do this with an intermediate list

Well honestly i've been able to do without it Also you can use the native localization support in JDA instead of doing it when building commands, look in LocalizationFunction

The "default" description is the one you set on #setDescription, for any other languages (i.e other than english) you put them in the resource bundle by the way there's ResourceBundleLocalizationFunction

You are probably still using the old JDA version. Make sure you removed the old JDA version before using the Jitpack build.

This may also permit refactoring of `awaitStatus` using the new monitors

Good chances it won't be added until it's documented