Currently the "plugins" folder (/config/bepinex/plugins/) containing the BepInEx mod DLLs is maintained as a sub folder of the "config" folder (/config/bepinex/).
I had a case, where a mod was doing a regex search through the whole BepInEx tree (config/plugins/...) for a translation config file, which is held inside the mods plugin folder. This mod did find the same file twice, since it can resolve it inside the docker's copied plugins folder (/data/bepinex/BepInEx/plugins/ ) and once inside the config folder (/config/bepinex/plugins/), since the sym link includes the plugins again, since they are held in this above mentioned sub folder structure I am asking to get changed.
I also asked the mod author to maybe do some error handling inside his mod, if the file is found twice, but also this specific detail of the current way how the docker solution is set up does contribute to such unwanted behavior. Would be great if the configs and plugins would be separated and not one being a subfolder of the other.
Currently the "plugins" folder (/config/bepinex/plugins/) containing the BepInEx mod DLLs is maintained as a sub folder of the "config" folder (/config/bepinex/).
I had a case, where a mod was doing a regex search through the whole BepInEx tree (config/plugins/...) for a translation config file, which is held inside the mods plugin folder. This mod did find the same file twice, since it can resolve it inside the docker's copied plugins folder (/data/bepinex/BepInEx/plugins/ ) and once inside the config folder (/config/bepinex/plugins/), since the sym link includes the plugins again, since they are held in this above mentioned sub folder structure I am asking to get changed.
I also asked the mod author to maybe do some error handling inside his mod, if the file is found twice, but also this specific detail of the current way how the docker solution is set up does contribute to such unwanted behavior. Would be great if the configs and plugins would be separated and not one being a subfolder of the other.