Yayy, another patch 🫠 If your Mods folder is as ridiculously huge as mine, patch day = a hellscape of broken mods and Last Exception spam. I thought I might share something that makes patch days slightly more bearable for me. It's a script I wrote to make Windows scan the script mods (TS4SCRIPT files) in my Mods folder and generate a report that looks a bit like this:
(I cropped the tables in this image of my report, because I have a lot of script mods 😅)
The report doesn't tell you what script mods are actually broken, but it does give you a good idea of what script mods you probably want to check/update first when there's a patch, where they're located, and what date you installed/updated them. It also gives you other info, like what script mods you might have accidentally placed too deep inside your Mods folder to work. You don't need to download anything for this - it's just a script I wrote to make Windows generate the report for you as an HTML file.
Under the cut: How to make Windows spit out info about your script mods to save you time on patch days 🪄 ⤵
So to make Windows generate this report, I run a script in PowerShell. No, wait, don't leave! I promise this is super easy to do! 😅 PowerShell is just Windows’ built-in command box, where you can type or paste little scripts to make your computer do useful tasks (like making it a bit less painful to hunt down broken mods).
Super simple step-by-step guide:
❌ Step 1. Close The Sims 4 (important!).
📂 Step 2. Open your Mods folder:
Documents > Electronic Arts > The Sims 4 > Mods
🖱️ Step 3. Hold Shift + Right-Click in an empty spot in the folder → click "Open PowerShell window here" (or “Open in Terminal”). You don't need to open it as admin, if that option appears.
📜 Step 4. I've saved my script in a Notepad (.txt) file that you can view or download from my Google Drive via the link at the bottom of this post. Highlight/Select All the entire script, copy it (right-click & "Copy" or Ctrl+C), and paste it into PowerShell (right-click & "Paste", or Ctrl+V). Paste it after the blinking cursor (PowerShell won't let you paste it anywhere else anyway :P)
🤔 Note: When you paste the script into PowerShell/Terminal, this window will probably pop up:
This is just PowerShell’s way of saying “Hey, this is more than one line — are you sure you meant to paste a whole block?” Click "Paste anyway" to make PowerShell stop trying to be the script police.
🔍 Step 5. Hit Enter and wait a few seconds for the script to run. You'll see PowerShell doing some fast scrolling as it scans your Mods folder for script mods.
🖥️ Step 6. Check your Desktop → you’ll see:
S4_AllScriptMods_DATE.csv
S4_Suspects_DATE.csv
S4_ModReport_DATE.html
📄 Step 7. Those CSV files contain the raw data that PowerShell generated when it scanned your Mods folder. The HTML file is that same data, just organised into a nice table layout that's easier to read. If you open the CSV files, they'll open in Excel/Sheets if you prefer to read the data that way. To view the cleanly formatted version, double-click the .html file to view the summary in your browser.
💫 Step 8. Behold! You've now made Windows generate a report containing organised tables of:
All subfolders inside your Mods folder that contain script mods, organised by the number of script mods inside them: "Top folders by script count";
All the scripts you might have in your Mods folder/subfolders that are older than 2025: "Scripts older than 2025 (check these first)";
A list of all your installed script mods that are more likely to break when Sims 4 has a patch update: "Patch sensitive frameworks detected";
A bonus list of any script mods you might have placed more than one folder deep by accident (meaning they won't work): "Script mods nested deeper than one folder (move these up)"
✨SCRIPT TO PASTE INTO POWERSHELL: Google Drive Link ✨
This link opens my .txt file in Google Drive’s viewer — you don’t need to download anything if you don't want to, you can just copy-paste the script right from the page, into your own .txt or other document file. Or you can download the file itself if you prefer 😊
I hope this report generator script is helpful! It's not something that will actually identify which of your script mods have borked on patch day - but it's saved me a ton of time hunting down the most bork-prone ones 😆
