Config not created when there is an existing ID conflict.

[Former user]

When most mods are newly added to an installation, they will create their config file immediately, before any potential ID conflicts cause the installation to not start.

This mod creates empty config files and only seems to populate it's configuration files after a successful start, so any potential conflicts cannot be resolved in this mods configuration files to start. It becomes required to modify the opposition mod's configs to get this one to start, for the first time. At that time, this mods Ids can be changed (except for "extra bees frames" (see other issue)).