Feature Request: Better Mod Conflict Detection and Diagnostics
Hello!
I would like to suggest improving the way The Sims 4 handles mod-related errors.
When a game update makes a mod incompatible, a broken or outdated mod can sometimes prevent the game from launching without giving the player any useful information about what caused the problem.
For players with hundreds or thousands of installed mods, troubleshooting this manually can take hours. They often have to remove their Mods folder and use the 50/50 method to identify the problematic file.
It would be extremely helpful if the game could have a diagnostic system that:
detects when a startup problem is likely related to mods,
identifies potentially incompatible .ts4script or package files when possible,
provides the name of the suspected mod/file,
offers an option to temporarily disable the suspected mod,
or launches a diagnostic mode with mods disabled.
For example:
“The game could not start successfully. A modified file may be causing a conflict. Suspected file: ExampleMod.ts4script. Please check for an updated version or temporarily disable this mod.”
I understand that the game may not always be able to determine exactly which mod is responsible. Even providing a likely cause or identifying suspicious files would save players a huge amount of time when troubleshooting after game updates.
This would make managing mods significantly easier and reduce the need for players to manually troubleshoot hundreds or thousands of files.
Thank you!