Diagnostic Matrix: Plugin Corruption Types and xEdit Treatment
In Bethesda modding communities (Skyrim, Fallout 4, Starfield), plugin instability often stems from unintended author edits saved into .esp or .esm files. However, blind cleaning of every mod flag shown in LOOT can permanently break intentional mod overrides.
| Dirty Record Type | Engine Failure Behavior | Severity Level | Automated xEdit Action | When to Avoid Cleaning |
|---|---|---|---|---|
| Deleted References (UDR) | Immediate Crash-to-Desktop (CTD) when another mod references the deleted FormID | Critical | Undelete and Disable References (UDR -> Set Initially Disabled) | Never avoid. UDRs must always be cleaned to prevent fatal crashes. |
| Identical to Master (ITM) | Overwrites downstream mods with vanilla master values, undoing patches | Medium | Remove Identical to Master records | Avoid cleaning if mod deliberately reverts a previous DLC change or compatibility override. |
| Deleted Navmeshes | NPCs freeze, CTD upon entering exterior cell boundary | Fatal | Cannot be auto-cleaned; requires manual recreation in Creation Kit | Do not attempt auto-clean. Contact mod author or download community navmesh patch. |
| Wild / Rogue Edits | Unrelated worldspace edits, accidental water height or landscape tweaks | Medium | Manual record pruning in xEdit | Manually inspect records in left tree view before deletion. |
The Mechanics of a UDR Crash
When a modder clicks "Delete" on a vanilla object in the Creation Kit rather than checking "Initially Disabled":
- The engine completely strips the FormID reference from memory when loading the cell.
- If another mod in your load order (such as a lighting overhaul, physics mod, or NPC AI package) attempts to attach scripts or query coordinates from that missing FormID, the game engine encounters a null pointer dereference and crashes immediately to desktop with zero warning.
- Cleaning through xEdit converts the fatal deletion into an "Undelete and Disable" operation, hiding the object 30,000 units beneath the map surface while preserving its memory pointer for downstream mods.
Practical Cleaning Protocol: xEdit Quick Clean
Step 1: Configure Quick Auto Clean Shortcut
- Download the latest version of xEdit (e.g.,
SSEEdit.exefor Skyrim Special Edition). - Create a desktop shortcut or configure an executable entry inside Mod Organizer 2 (MO2) or Vortex.
- In the arguments field, append the command flag:
-quickautoclean - Verify your backup directory path is valid in settings.
Step 2: Safe Cleaning Execution
- Launch the Quick Auto Clean executable.
- Select only one single plugin at a time from the module selection window.
- Allow xEdit to perform its automated passes:
- Identical to Master removal
- UDR undelete and disable
- When the log displays
Quick Clean complete, close the window to save the stripped plugin. - Re-run LOOT to verify the dirty edit warning has cleared.