Check what changed#
Open a save written before your SaveGame class changed. Keep Issues on Packaged game and review dropped or changed values. Preserve the original file while testing.
Recover a simple rename#
- Select the renamed field in Issues.
- Choose Add Rename Rule....
- Confirm the old and new fields.
- Press Migrate in the inspector.
- Compare the result with the original.
Rules are managed under Project Settings → Plugins → Save Game Inspector → Field Renames.
Create a new save version#
For wider changes, choose New Save Version from the plugin's Tools menu or the SaveGame Blueprint's Content Browser menu.
- Select the changed SaveGame class.
- Choose an older save to test.
- Select where each lost field should move.
- Review each move's result and resolve failures.
- Create the proposed new version.
A path such as Stats.Score identifies a nested field. In supported field moves, Inventory[*].Health addresses the field for every element.
Use recovery in the game#
Replace the normal load node with Load Game From Slot (Migrated), Async Load Game From Slot (Migrated), or, for saves your game reads itself, Load Game From Memory (Migrated). Check the returned report for unresolved losses.
Continue saving with the normal Save Game To Slot node.
Test before releasing#
Try representative saves from older versions in both the inspector and a packaged build. Confirm values you expect to retain and review the report. Raising a version number alone does not recover a missing field; the required rules or migration steps must exist.