Help with using the Mod conflict detector
I am used to using conflict Mod detector programs in other sims series so decided to try the program for 4 over on MTS however despite it stating the language is in english most is not but I managed t...
Forum Discussion
If you look down at the bottom under Settings, the color coding is explained (including examples of exactly what it will look like). by default, that grey is "normal file, no conflict". it's the same as green, but for a different type of file.
Not Analyzed means it didn't check the file. If you look at the very bottom of your screenshot, see that orange bar that's half full? That is the scan and analysis progress. It is not complete, in your image. hence why so many files are not analyzed.
Those loading errors along the left are files that it is having trouble loading. For me, those cause the program to hang...leading to analysis never completing. 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.
Honestly, the analyzer is so far from perfect it is hardly a useful tool. It reports conflicts that aren't truly a problem, so take the results with a grain of salt. I use it to scan for duplicates, and then look at each conflict it detects making a note of what mods they are...then I go in game to see how the supposed conflicts actually function. 99% of the time, they all function fine and I leave them in.
The best source of mod issues is the forums/site where you downloaded them. Don't use mods after any game patch until their author gives the okay or provides an update saying they are fine. Any mods where the authors aren't around anymore, I personally purge, although you can of course test and read community reports on how they are functioning. More hassle than it's worth imo though, as mods can often break things in game that are seemingly un-related to what the mod does. (I'm not saying do not use the analyzer...just don't expect it to save you much time managing mods).
Not Analyzed means it didn't check the file. If you look at the very bottom of your screenshot, see that orange bar that's half full? That is the scan and analysis progress. It is not complete, in your image. hence why so many files are not analyzed.
Those loading errors along the left are files that it is having trouble loading. For me, those cause the program to hang...leading to analysis never completing. 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.
Honestly, the analyzer is so far from perfect it is hardly a useful tool. It reports conflicts that aren't truly a problem, so take the results with a grain of salt. I use it to scan for duplicates, and then look at each conflict it detects making a note of what mods they are...then I go in game to see how the supposed conflicts actually function. 99% of the time, they all function fine and I leave them in.
The best source of mod issues is the forums/site where you downloaded them. Don't use mods after any game patch until their author gives the okay or provides an update saying they are fine. Any mods where the authors aren't around anymore, I personally purge, although you can of course test and read community reports on how they are functioning. More hassle than it's worth imo though, as mods can often break things in game that are seemingly un-related to what the mod does. (I'm not saying do not use the analyzer...just don't expect it to save you much time managing mods).
