

NOTE: I have never experienced any save corruption in Oldrim, and I run heavily modded setups with many active scripts. The issue is the sheer number of scripts being run actively, not when or where the save is being made, apparently. Which means that the supposed problem with in-combat while running scripts and saving is not a thing - the poster was very specific in that Papyrus ceases running scripts while conducting a save. To execute automatically after each reload, add this to \Data\SKSE\skse.Reading the reddit that Delta posted, I note a few things:ġ) There is no difference in types of saves. This may take hours depending on the amount of bloat.

When applied to an already bloated save, it will stop growing further and instead shrink over time as the game processes all queued events. This prevents orphaned OnUpdate() events and the resulting bloated/broken saves when removing certain mods. Note that the official patches have now fixed ash piles and nirnroots not being properly cleaned up.Īnother option to fix already bloated save game files is by using Skyrim Script Extender's (SKSE) ClearInvalidRegistrations console command.Īdd console command ClearInvalidRegistrations to remove invalid OnUpdate() registrations It will be necessary to visit each affected map twice before the cleanup can take effect on existing saves though. The fix also removes bloat from excess flags that have been accumulating. This is due to a bug in CWMapActivatorScript which does not clean up placed flag activators.

NPCs will no longer drop weapons or shields as separate objects, as these are never cleaned up which greatly adds to save bloating and.For PC players, install the Unofficial Skyrim Patch.
