Feauture Request: Configure & Save Options per mod

[deekej]

Hello! :) Thank you for your awesome work, as a programmer I really appreciate the effort behind it!

One thing I would like to propose is a change how configuration is stored / reloaded in the Batch Installer.

I was experimenting with different mods (before I commit to a playthrough with them), and many times I had to add additional mod later to my Batch Installer Group... And even though the mod might be standalone (not affecting any other mods in the batch group), I still have to manually apply the same mod options when reinstalling the batch. Which in some cases can take quite a lot of time.

It would be great to be able to configure each mod in the Batch Installer individually - one by one - and when new mod is added, the batch mod installation would use the previously saved configuration without the need to set all the options again... :)

Would it be possible to implement this or similar functionality?

[Mgamerz]

As is, this is done to ensure options are valid. If a mod changes, a mod downstream on install may change and the options would be wrong.

I don't know off the top of my head if invalidation of saved options does all of them, or just starting at the changed ones. It's something that would be useful.

Changing an existing mod or adding a new one not at the end would still invalidate downstream since saved options may be correct for automatic options but no longer for manual ones.

I can look into it for the next feature release, but that probably won't be for a while.

[deekej]

I see, thanks for the info. :) Maybe a mod version could be stored alongside the saved options information? When checking if saved options could be used, then the version could be compared...

[Mgamerz]

That wouldn't really solve the issue. The moddesc hash is saved right now, as a mod changing should include the version changing, which will change the hash. This also covers if available options (made by the dev) changing (requiring moddesc changes), but the version doesn't for some reason.

A mod changing could change the things other mods depend on. When I return to working actively on mod manager I will look at how the current system works and see if it can only invalidate downstream mods rather than the whole thing. This way if you add a mod to the end it won't invalidate all of the list (though that mod would have to be standalone.)