Save safety

AERR never writes to the DDS save file. Here's what it does instead.

AERR treats the DDS save file as read-only. Everything AERR persists lives in Win64\AERR\ alongside the DLL.

How it works

AERR hooks UFunction calls for the game’s RamaSave save/load events via ProcessEvent. When the game triggers a save, AERR writes a parallel JSON state file for its own managers (scripts, recipes, panels, keybinds). When the game loads, AERR reads that same file and restores script state.

What this means for you

Rolling back a save rolls back AERR state too — they travel together.
Deleting Win64\AERR\ wipes AERR state but leaves the DDS save intact.
Crashes mid-save don’t corrupt the DDS save — the hook is read-only on the game’s side.

What this does not protect against

Manual edits to the DDS save file while AERR is running.
Third-party save tools that rewrite the save.

Always back up saves before trying new recipes in the overlay.