I was on moddermore looking at a modpack and see this one's in the list. I checked out the Modrinth page and I'm not sure what sorcery is afoot, not do I understand said sorcery.

I'm working on my own modpack, so I think I'm the intended audience for this mod (based on some other issues here on Github), but I'm not clear on what this does, what value it adds, or if/how such a general statement of "we can extract all settings from all mods" even works.

So far, all the mods in my modpack only have server side settings that I want to set, so it's just config files on the server, so maybe that's why I don't understand what this mod does.

what is the typical use case for this mod ?

this mod helps modpack developers provide default options and configs for their modpacks. managing configs becomes an issue when a user tries to update the modpack, since, by default, it overwrites all of their config files (even those that they changed themselves). for example: you decided to change a keybinding, but after updating the modpack, your options have been overwritten. this mod prevents that by adding a config file ONLY if the user doesn't have one already.

Thanks it's really help for me! This mod is in my modpack list

I stumbled upon here with the same question : what is the typical use case for this mod ?

I saw interesting people use it so I'm wondering

what is the typical use case for this mod ?

this mod helps modpack developers provide default options and configs for their modpacks. managing configs becomes an issue when a user tries to update the modpack, since, by default, it overwrites all of their config files (even those that they changed themselves). for example: you decided to change a keybinding, but after updating the modpack, your options have been overwritten. this mod prevents that by adding a config file ONLY if the user doesn't have one already.