Savegame Diagnostic and Cleaning Action Matrix
| Diagnostic Indicator | Typical Root Cause | ReSaver Cleaning Action | Safe to Clean? | Expected Recovery Outcome |
|---|---|---|---|---|
| Unattached Script Instances | Uninstalled scripted mods leaving orphaned script logic | Remove unattached instances | Yes (Low Risk) | Reduces save size, eliminates missing reference log spam |
| Suspended Script Stacks | Script frozen waiting for nonexistent actor/cell reference | Terminate suspended stacks | Moderate Risk | Unfreezes quest triggers; may reset active thread timers |
| Undefined Element Records | Corrupted array or broken FormID reference | Remove undefined elements | Yes (Low Risk) | Prevents CTD when game parses internal cell forms |
| Active Script Thread Loops | Poorly optimized mod polling game state every millisecond | Script cleaning cannot fix; must patch or remove mod | No (Dangerous) | Cleaning active loops causes quest lockups |
Game engines utilizing the Papyrus virtual machine (such as Skyrim and Fallout 4) serialize running script instances directly into .ess save files. Removing a scripted mod mid-playthrough does not remove its active scripts; the engine perpetually stores these orphaned threads, resulting in save bloat, script lag, delayed interaction prompts, and eventual crash-to-desktop (CTD) on auto-save.
Step-by-Step Save Inspection Using FallrimTools (ReSaver)
Before manipulating any savegame, create a redundant manual backup in a separate archival directory.
- Locate and Isolate Save File:
- Save path:
Documents\My Games\[GameName]\Saves\save[Number].ess - Copy the target file to an isolated folder:
C:\SaveBackups\.
- Save path:
- Launch ReSaver:
- Open FallrimTools ReSaver.exe.
- Select File -> Open and load your target savegame.
- Inspect Virtual Machine Health:
- Observe the overview panel:
- Active Scripts: Normal baseline is between 50 and 500. Figures exceeding 5,000 indicate severe script flooding.
- Suspended Stacks: Should normally be 0 to 5. Anything exceeding 50 points to frozen engine threads.
- Observe the overview panel:
Safe Cleaning Protocol
- Navigate to the top menu bar: Select Clean -> Show unattached instances.
- Review the listed script names. Confirm they correspond to mods you intentionally deleted.
- Right-click and select Delete all unattached instances.
- Select Clean -> Show undefined elements.
- Right-click and choose Delete all undefined elements.
- Inspecting Suspended Stacks:
- If your game experiences severe dialogue freezes or non-responsive triggers, select Clean -> Show suspended stacks.
- Carefully terminate stacks associated exclusively with missing mods. Never terminate core game quest stacks (e.g.,
MQ101,DialogueFollowerScript).
- Save New Cleaned File:
- Select File -> Save As.
- Save under a distinct incremental filename (e.g.,
save002_cleaned.ess). Never overwrite original saves directly.
Post-Cleaning Verification Checklist
- Load the cleaned savegame in a clean interior cell (such as an empty tavern or player home).
- Wait 72 in-game hours using the wait function to allow Papyrus cell buffers and respawn timers to reinitialize.
- Verify save time: A healthy save should write to disk in under 2 seconds; prolonged multi-second disk writing indicates residual script serialization lag.