The Sims 4 gives you a folder and no tools. When a mod stops working there
is usually no error, no LastException and no clue.
SimScan reads the folder offline and tells you what is broken, what is
duplicated, what is fighting - and which mod the game actually applies.
Windows installer plus a portable zip. MIT-licensed source and the full test suite are on GitHub, so you can check the download against what was built.
11 files | 7 packages | 1 script mod | 208.9 KB | 0.0s [HIGH] 1 script mod that will never load The Sims 4 only loads .ts4script files up to one subfolder deep. Anything deeper is ignored completely - no error, no LastException. - ScriptMods/MCCC/mc_cmd_center.ts4script [HIGH] 2 duplicated mods (2 wasted) Byte-for-byte identical under different names, so name-based duplicate checkers miss them entirely. Reclaim roughly 0.1 MB. - Loose Files/JacBaconIsLife (1).package - [MOD] SimmerTales/Jac_BaconIsLife.package [HIGH] 1 resource conflict between mods (1 gameplay) SimData 545AC67A:00000000:2F1A3C4D5E6F7788 loaded: [MOD] TraitPackB/Bold_Trait_Remake.package (priority 500, depth 2) ignored: [MOD] TraitPackA/Bold_Trait_v1.package [MEDIUM] 1 package with no content - Loose Files/empty.package exit 1 - 3 high-severity findings
Existing managers are good at browsing and organising, and trackers tell you whether a mod has been updated. These are the four things that routinely go wrong and are almost never reported.
You tidy your folder, bury a .ts4script two
levels deep, and it stops working. No error, no exception, no clue.
SimScan flags every script file below the depth the game actually
reads.
You re-download a hair and get Hair (1).package.
Name-based checkers miss it completely. SimScan compares content
hashes, so an identical file is caught whatever it is called.
Most tools say "these two conflict". None say which one the game
applies. SimScan works the winner out from Resource.cfg
priority, folder depth and filename order - and names it.
One damaged download can make an entire folder look broken. SimScan reads every package index and reports exactly which ones cannot be read, so one bad file does not hide the rest.
Evidence: DBPF header / index parse failureThis is SimScan 1.0.2 output, unedited, from a deliberately broken Mods folder: a script mod buried too deep, two pairs of identical files under different names, a resource conflict between two trait mods, an empty package and some junk that should not be there. Every file it names in this report is a synthetic test file built for the test suite - no third-party mods are redistributed with the product.
This area is full of tools that over-promise. Here is the line, stated plainly.
Nothing can, except the game reproducing the fault. SimScan ranks suspects; you still have to test them.
It writes the plan and halves the work. It will not launch your game.
It does not scan for malware and it does not download or update mods. Use a mod manager for that.
_disabled folder the game ignores, with
Undo to put them back; Delete sends files to the
Recycle Bin, not oblivion.
Adjacent tools are useful, and none of them do this.
| Question | Mod managers | Update trackers | SimScan |
|---|---|---|---|
| Browse and organise mods | Yes | - | Not asked |
| Is this mod updated yet? | No | Yes | Not asked |
| Which script files the game ignores? | No | No | Yes |
| Duplicates by content, not filename? | No | No | Yes |
| Which mod wins a conflict? | Rarely | No | Named, with the rule used |
| Reads the game crash reports? | No | No | Yes |
The source is MIT and public. So is the test suite, and so is the record of what has actually been run.
One price, both builds, no subscription. Source stays free and public - buying gets you the built Windows binaries so you do not have to construct them yourself.