It'd be helpful to see the folder structure change so that pre-load plugins folders aren't read twice by some mods accessing the /config/bepinex folder to read their configurations.
Right now, mods that read the folder at runtime because of the symlink in /opt/valheim will often find their own dlls in the child folder of /config/bepinex. This causes issues as seen here: https://github.com/lloesche/valheim-server-docker/issues/614
It'd be better if the folder structure separated out preloaded plugins from the /config/bepinex configuration. The way I see it possible might be to have configuration files live "one level" down.
Example
/config/bepinex/config -> configuration files/config/bepinex/plugins -> preloaded mod plugins
/opt/valheim location for symbolic link points to new location of plugin configuration files that does not have plugins as a child directory
Hopefully this change is considered to help address current and future issues.
It'd be helpful to see the folder structure change so that pre-load plugins folders aren't read twice by some mods accessing the /config/bepinex folder to read their configurations.
Right now, mods that read the folder at runtime because of the symlink in /opt/valheim will often find their own dlls in the child folder of /config/bepinex. This causes issues as seen here: https://github.com/lloesche/valheim-server-docker/issues/614
It'd be better if the folder structure separated out preloaded plugins from the /config/bepinex configuration. The way I see it possible might be to have configuration files live "one level" down.
Example
/config/bepinex/config -> configuration files
/config/bepinex/plugins -> preloaded mod plugins
/opt/valheim location for symbolic link points to new location of plugin configuration files that does not have plugins as a child directoryHopefully this change is considered to help address current and future issues.