Add REMOVE_OLD_CONFIGS

[GameBurrow]

Enhancement Type

Improve an existing feature

Describe the enhancement

It would be awesome if you could implement env var REMOVE_OLD_CONFIGS.

Aim is to delete/cleanup all files in config folder on server boot before it downloads the modpack.

Why do I need this?

Because some mod authors have designed their mod configs badly and have put client and server configurations in single file. Due to that, so that every modpack update wouldn't override client's custom settings, I've moved some of those settings to defaultoptions configs (which are only copied using some specific mods when the file doesn't already exist).

[itzg]

Thanks for posting this. By itself it seems like a reasonable feature. Combined with the modpack automation it could be problematic since the automation ensures all files are present and will reprocess the modpack if any are absent.

Have you tried this yet to see if the conflicting config files can be excluded in the first place?

https://docker-minecraft-server.readthedocs.io/en/latest/types-and-platforms/mod-platforms/auto-curseforge/#excluding-overrides-files

[GameBurrow]

Have you tried this yet to see if the conflicting config files can be excluded in the first place?

https://docker-minecraft-server.readthedocs.io/en/latest/types-and-platforms/mod-platforms/auto-curseforge/#excluding-overrides-files

No I didn't as I'm using Packwiz method. Thankly since I'm running it in k8s I implemented using initContainer to remove the data/config folder before it starts at the moment as workaround.

[itzg]

Ah, packwiz is a whole different matter since it's their automation. I'm actually not sure if it does angle integrity checks like my CurseForge and Modrinth automation does.

I'm glad to hear about the robust workaround.

I'll keep this issue queued up.