Bungee logging is extremely verbose and clutters up console output about resourcepacksplugins HOT 3 CLOSED

There already is a config option ;) Just set it to false and fewer messages will be logged. (You can also define any log-level that you want)

from resourcepacksplugins.

Even with debug: false a good amount of the startup messages are still present, most of which are useless to the vast majority of people, especially in the console output.

18:24:33 [INFO] [BungeeResourcepacks] Registering ResourcePackSendPacket...
18:24:33 [INFO] [BungeeResourcepacks] BungeeCord 1.9.4+ (404) detected!
18:24:33 [INFO] [BungeeResourcepacks] Found mapping for 1.8+
18:24:33 [INFO] [BungeeResourcepacks] Found mapping for 1.9+
18:24:33 [INFO] [BungeeResourcepacks] Found mapping for 1.12+
18:24:33 [INFO] [BungeeResourcepacks] Found mapping for 1.12.1+
18:24:33 [INFO] [BungeeResourcepacks] Found mapping for 1.13+
18:24:33 [INFO] [BungeeResourcepacks] Loading config!
18:24:33 [INFO] [BungeeResourcepacks] Debug level: FINE
18:24:33 [INFO] [BungeeResourcepacks] Found locale en!
18:24:33 [INFO] [BungeeResourcepacks] Loading packs:
18:24:33 [INFO] [BungeeResourcepacks] minecraft - https://<snip>.zip - <snip>
18:24:33 [INFO] [BungeeResourcepacks] Empty pack - http://cdn.moep.tv/files/Empty.zip - 01517226212d27586ea0c5d6aff1aa5492dd2484

Most or all of that output should be FINE in my opinion- or at least follow the value set in the configuration

from resourcepacksplugins.

Well it's only possible to respect the debug setting once the config is loaded so that would have to change for half of these messages.

For the rest that refer to the config I don't really see them as such a big issue: Outputting some information about how a software is configured is done in lots of different cases and helps ensure that it's configured correctly and also that you have historical log-data about the setup that was used.

from resourcepacksplugins.