Factorio Forums

Here is what I did

- developed a new mod "B". It depends on version "1.0.1" of an existing mod "A"
- have a local version of the "A that is "1.0.1" and a fallback to "1.0.0" (mod_a_1.0.0.zip while 1.0.1 lives in a directory)
- release "A" 1.0.1 to the mod portal
- remove the directory that contains the 1.0.1 version of "A".
- start the game. It complains that "mod configuration is invalid, mod B needs 1.0.1 of mod A, but only 1.0.0" installed
- click "manage mods". Choose "update mods". The 1.0.1 release from the portal shows up. Select, click upgrade.

When clicking "confirm", it shows the dialog "The selected mod configuration is not valid. The dependencies for some mods are not met."
Looking at the "Manage Tab", it still shows "A" as 1.0.0 even though I just installed 1.0.1

All that is needed is a restart. But I can not restart because the "confirm" dialog looks at the state of the world *before* upgrade which is illegal and not the state of the world after upgrade.

My hunch is that the "confirm" dialog should not do this check. It should restart the game and have it pop up the early dialog if the configuration is still not valid. When I cancel out of the dialog, the just downloaded mod A 1.0.1 is deleted and I am back to square one.

Only way around is "upgrade A, disable B", then restart. Then "enable B", restart again.

This seems less than ideal.

Thanks for the report.
Fixed for 2.1.
I decided to fix this by removing this dialog altogether on PC(it is still useful on Nintendo Switch).
There are too many edge cases like this that have non-trivial fixes so the dialog was more getting in the way rather than helping.