Probably Stolen Mod Compatibility and Troubleshooting

Most Probably Stolen mods work without drama. The ones that fail usually fail for one of five reasons: the mod is older than the game patch, it needs a loader, it collides with another UI mod, it depends on a mod you do not have, or the save contains content from a mod you removed.

This guide gives you a diagnostic order. Start with the game, then the loader, then the mod list, then the save.

For installation basics, see how to install mods.

The five failure classes

Step 1: test vanilla

Disable every mod and launch the game. If it still crashes, the problem is the game install, not the mods. Verify the game files in Steam and try again.

If vanilla works, the problem is in the mod set. That is good news: you can find it by elimination.

Step 2: check the Mono loader

The Workshop has 15 mods tagged mono. Those mods usually need a loader, and the loader must match the game version. If the loader is out of date, the mod may fail silently or crash on launch.

Check:

1. The loader version against the game version.
2. The loader log for the first error, not the last.
3. The mod's own requirements section.
4. Whether the mod was updated after the last game patch.

Do not install two loaders for the same mod type. That is a common cause of a launch crash.

Step 3: check dependencies

Some mods require another mod, a framework, or a specific loader. If the dependency is missing, the mod may load but do nothing, or it may crash when its feature is used.

Read the mod description before subscribing. If it says “requires X”, install X first, then the mod.

Step 4: bisect the mod list

The fastest way to find a conflict:

1. Disable half the mods.
2. Launch and test.
3. If the crash is gone, the culprit is in the disabled half.
4. If the crash remains, it is in the enabled half.
5. Repeat until one mod remains.

This takes a few restarts, but it is faster than guessing. Test one mod at a time after you find the suspect.

Step 5: check load order

Load order matters when two mods change the same system. A general convention:

1. Loader or core library.
2. Framework and dependency mods.
3. Gameplay mods.
4. UI mods.
5. Translation mods.
6. Cosmetic mods.

If two UI mods rewrite the inventory, the later one wins. That can produce a blank panel or a mix of both layouts. Pick one.

Known conflict patterns

These are patterns, not confirmed mod-specific bugs:

• Two inventory overhauls. Smart Inventory Arrange plus another inventory rewrite can fight over the same grid.
• Translation plus UI mod. A UI mod that adds new labels may not be translated, producing mixed-language screens.
• Multiple chemistry tools. Pen's Pipette and another chemistry UI mod can overlap.
• Multiplayer plus gameplay overhaul. Probably Multiplayer is version-sensitive; large gameplay mods increase the mismatch risk.
• Old Mono mod plus new patch. The loader may not expose the new game API.

If you use one of these combinations and it works, keep a note of the versions. A future update can break it.

Reading logs

The game and loader may write logs to the install directory or the user data directory. Look for:

• The first exception, not the last.
• Missing file or missing assembly errors.
• Repeated null references when opening a specific menu.
• A mod name in the stack trace.

If the log names a mod, disable that mod first. If it names a loader assembly, update the loader.

After a game patch

A patch can break mods even if the mod author did nothing wrong. The safe sequence:

1. Back up the save.
2. Disable all mods.
3. Launch vanilla and confirm the patch works.
4. Re-enable UI mods first.
5. Re-enable gameplay mods one at a time.
6. Check the Workshop for updates.

Do not re-enable a large mod list at once after a patch. You will not know which mod broke.

Save safety

Removing a mod that added items can make a save fail to load. If you must remove it:

1. Back up the save.
2. Remove the mod.
3. Load an earlier save that did not contain the mod's items.
4. If the save is already affected, re-enable the mod long enough to sell or delete the items, then remove it.

There is no universal save editor for this. Prevention is easier than repair.

Performance problems

A large mod list can slow the game down, especially UI mods that redraw every frame. If performance drops:

• Disable UI mods one at a time.
• Check for mods that add continuous scans.
• Reduce the number of inventory sorters.
• Test without multiplayer.

The base game is not heavy; a stutter that appears only with mods is usually a mod issue.

FAQ

Why does my mod not show up? Check that Steam finished downloading it, that it is enabled in the game, and that its dependencies are installed.

Can I use mods with the Mac version? Some mods work, some do not. Check the mod page for platform notes.

Do mods break achievements? Not documented. Use UI-only mods for achievement runs.

How do I report a mod bug? Post on the mod's Workshop page with the game version, mod version, other mods installed, and the log excerpt.

Community source: Steam Workshop ↗, Workshop tag counts and item pages, and the Steam Community guide hub ↗. Store reference: Probably Stolen ↗. Workshop example: Purchase Stay Counter ↗.

Related

• Mods Guide
• How to Install Mods
• Best Mods