Search results
3 mar 2018 · Here's my project, Mod Conflict Detector for The Sims 4. It's a powerful GUI tool for detecting and solving mod conflicts in the game. Allows you to get rid of trouble-making mods, empty mods, mods for another games, or technically-not-even-mods, that got in the Mods folder by mistake.
I have to move the indicated files out of my mods folder before I run the scanner (fortunately I only have one such mod...which is fine, the program just doesn't like it). You will also see the loading error if you try to run the scanner while the game is running...don't do that.
I think there's only one way this could have happened, so this should be fixed now in 0.1.3. If that doesn't fix your issue let me know more details about the exception. I overlooked the fact that two packages could have precisely identical file modification timestamps if one is a copy of the other.
Two things to try. Sims 4 tray importer might find it for you. Better exceptions by twisted mexi might find it for you. If all else fails, pull half and test. Switch halves and test again.
I used the DmitryMalfatto's Mod conflict detector to find out which package files conflicted and put them in separate folders. Each folder had between 2 and 20 files in it. I thought this issue was related to the folder names, maybe the spaces or the brackets so i numbered the folders like this..
The mod conflict detector only flags instances of conflict between two mods, specifically when they both modify the same resource in the game itself. It won't be able to detect broken mods, or ones that don't quite function as well as they should.
I know exactly what is conflicting already through mod conflict detector. Is deleting really the only way to fix it? Does conflicting cc do much more other than glitch out how the sim looks sometimes?
