Closed EgilSandfeld closed 3 years ago
My workaround, for now, was to manually move the disabled mod from the old cache to the active mods folder ("community"), refresh MMM and disable that same mod.
Also, you should definitely prompt the user to specify the disabled mods folder themselves, as few have spare space on the main harddrive
Apologies for the delay, it's been a busy week. At the moment, this is expected behavior, the disabled mod folder does not get moved at all (see select_mod_cache
). I do agree that this makes sense to be done automatically. I've added it to my target for v0.5.1.
For the second part, I'm going to leave it for now. I think the default is reasonable, and there's a GUI option to change it if desired.
Expected Behavior
Moving Disabled Mods folder with disabled content in it should move the content to the new location
Actual Behavior
Moving Disabled Mods folder will change directory to the new folder, but keep the disabled mods in the old folder
Steps to Reproduce the Problem
Specifications
v0.4.4
Debug Log Contents