Closed jaghaimo closed 3 years ago
This arises when upgrading/replacing through the mod ID collision code, as opposed to the folder name collision code.
I believe my reasoning for this was that the original folder (aka the folder being deleted) might be named by a specific version - like "magiclib_2.1.6" or similar. Unpacking magiclib v2.1.7 into that folder might then be misleading.
However, this does also clobber custom folder names or folder names that don't match the mod ID too. I'm not sure which behaviour is preferable.
Perhaps both? An option in settings to chose which naming convention to use (e.g. boolean - preserve folder names, default off).
And if you feel generous - a select box with:
ModManager should respect the names of the folders when updating a mod. Instead, it deletes an existing folder and creates mod-default one.
Reproduce
Organise your mods by renaming their default folders, for example:
Upgrade LazyLib -
001 LazyLib
is replaced withLazyLib.2.6
. Expected:001 LazyLib
is preserved as mod folder, contents updates.