Idea for removing "orphan" config files

[American2050]

So, this is something I had in my head since I started making ModPacks.

 

For some reason, just now I realize that this is something that Forge could implement easily (I believe)

 

What I'm talking about is a way for Forge to know once a mod is removed from an instance of a ModPack, on the next launch, when Forge notice this changes, it can delete the config files from that mod.

 

In my head it would be something like... I, mod maker, have to inform Forge what files I'm going to create, been in the config folder, or somewhere else. Forge can take that and save that information somewhere.

On the next launch of the instance, if Forge see that my mod is not there anymore Forge takes action and delete those files.

 

This obviously been a configurable behavior, as ModPack makers usually have to disable and then re-enable mods when testing so in some cases we would need this behavior to be turned off.

 

Well, hope this is something that can be considered for the future

[LexManos]

Forge does not directly manage all the config files for mods, So we have no idea what is a used config and what is not.

On top of that its fairly common practice for Mod pack creators to create one 'master config set' and use it for all their packs.

So the users can modify the modpack if they wish.

Basically, no, there is no 'easy' way to do this. And the configs take little disc space so it's not a real issue.