Script mods & frameworks

Script mods are different from package mods. They run actual Python code in the game, which means they can do more, break more, and depend on each other in ways that SimSweep can detect. If you have ever had a script mod stop working after a patch and had no idea why, this is the part of the app that helps you figure it out.

Where to find script analysis#

Script mod data shows up in a few places:

• Diagnostics > Conflicts and Duplicates > Broken Scripts - The main hub for framework issues.
• My CC - Individual script mod cards show dependency counts, author/version hints, and risk signals.
• File inspector - The detail panel for a script mod shows classification and dependency details.
• Dependency Details modal - Opens from a file card when you click into dependency information.

What SimSweep reads#

When SimSweep scans a script mod, it reads the Python bytecode inside the .ts4script file and extracts:

• Every import statement (which modules this mod depends on)
• Which modules this file provides (so SimSweep knows if it is a framework or a dependent)
• Author and version hints baked into the file metadata
• Source filenames packed inside the archive
• Whether the Python bytecode is valid for the version the game expects
• Non-code files bundled inside the script

Risk tiers for known game API categories are loaded from a server config when available, with a hardcoded fallback. Risk tiers describe how sensitive the API surface is, not whether the mod is malicious. For actual malware signals, see the Threats section in Diagnostics.

Framework providers and dependents#

Many popular script mods act as frameworks: they provide a shared base that other mods depend on. SimSweep identifies these automatically and groups them.

The Broken Scripts view shows three summary cards:

• Providers - Framework mods installed and active in your folder.
• Dependents - Mods that rely on at least one framework.
• Missing frameworks - Frameworks that one or more of your mods need but cannot find.

Below the summary, you get three sections you can expand or collapse:

Missing frameworks#

These are framework namespaces that your installed mods import but that SimSweep cannot find anywhere in your Mods folder. The fix is almost always to install the missing framework, not to delete the mod that depends on it. Deleting the dependent mod removes the symptom but leaves other dependents broken.

Duplicate framework providers#

Two or more files providing the same framework namespace. This can happen when a mod bundles a copy of a framework alongside its own code, or when two versions of the same framework coexist. Review the file paths and the apparent creators before removing anything. Some bundled copies are intentional.

Installed frameworks#

A list of detected framework providers that are active and have no detected issues. These are the mods other things depend on.

Dependency details#

Click into any script mod's card or open the Dependency Details modal to see a full breakdown: what the mod imports, what it provides, which other mods depend on it, and where each file came from.

Heads up: Before deleting a framework provider, check the dependents list. Removing a framework with active dependents will break those mods in the game.

Detailed metadata and Decrypt#

The summary cards, missing framework counts, and duplicate provider warnings are always free. Detailed metadata in the file inspector (full import lists, classification, risk tier labels) requires Decrypt.

Next up#

Back to Diagnostics for the full picture, or check Conflicts and duplicates if your script analysis is showing up under Broken Scripts alongside package conflicts.