Updating a disabled mod that has new dependencies should disable the new dependencies automatically

[pentaquark]

If you have a disabled mod installed, and you update the mod, sometimes it'll happen that the mod has new dependencies that get installed when it's updated. In this case, the mod's new dependencies will be enabled even though the mod itself is disabled.

As a concrete example, Muluna recently added a dependency on the "Valves" mod. I have Muluna disabled, but when Muluna was updated, the Valves mod (and its dependency) was installed automatically and enabled by default, and I had to disable it manually. It would be nice if instead, the Valves mod (and its dependency) had been disabled automatically.

[boskid]

If you go to "Other settings", do you have "Automatically enable new mods" turned on? (it is on by default).

[pentaquark]

Yes, that setting was on; I wasn't aware of it before, thanks for mentioning it. I'll try disabling it and see if that helps.

However, having that setting disabled might cause the opposite problem: if the setting is disabled but Muluna had been enabled while it was updated, the newly-installed Valves mod would probably be disabled by default and so would need to be manually enabled for Muluna to work. So it would still be nice if new dependencies inherited their enabled status from the mod that requires them.

[eugenekay]

Related: 133668