Mod Synchronization
This issue is with how users need to uncheck then recheck a mod when upgrading their database or whatever. I forget what I intended, but it seems like users expect that the latest mods would be automatically installed. Like upgrade from 2.10 to 2.11, you expect the 2.11 mods are now installed. And I can understand why. The 2.11 mods are the only ones visible, and probably checked. But its the act of clicking the checkmark on that actively installs a mod. Typing this all out now is forcing me to understand the issue.
So I guess I need to make sure that, on database update, installed mods are looked at, and actually installed. I thought thats how it was, but I can easily see myself missing that scenario.
Comments (3)
-
reporter -
reporter Issue
#90was marked as a duplicate of this issue. -
reporter With the July 24, 2024 build I have tried to address this topic by adding the NSOM Mismatch and Update v#.#.0.0 buttons.
So include issues with those as on topic for this thread.
- Log in to comment
I did address this, but forgot to follow up here until now.
Though it might not be addressed in all occasions.