Factorio Forums

My idea is pretty simple. It is based on most computer's ability to boot a computer using the last settings of a BIOS that were successful in the case where a bootup fails, the user may ask the computer to load using the settings that were used the last time the computer was able to boot successfully.

In times where a user has successfully loaded all mods in their desired setup, and changes a config option that breaks everything, they must now, disable, then delete the mod, and then later reinstall it or find the file that contains the mod settings and manually edit it (assuming they know where to locate and edit it).
The simple inclusion of a file that is stored upon successful load of the game (modsettings.lastsuccess.json) can enable a user to simple load the last used settings for their game when a change in those settings results in a crash-cycle.

Can you provide an example case where a mod breaks Factorio due changed settings?

Sounds like a rare case based on bad mod code.

That's why we have the disable mod option on launch now. can you remember/imagine how much of a pain it was if you installed a broken mod, to have to manually find the mod on your system and delete it? (or at least edit modsettings.json to not load it)