Migration

Review draft. This source page has not completed website editorial and release-specific verification.

SaveGame Director 1.0.x keeps the current public save-format and slot-identity contract. Plugin version labels and persisted-data versions are separate; changing a plugin version does not by itself migrate a save.

Version compatibility

• The current USaveGameDirectorSaveGame wrapper version is 1.
• The canonical document envelope version is 1.
• Actor records use version 2; the runtime supports normalization of the documented legacy Actor record version 1. Other unsupported record versions fail validation.
• Contributor payload schema versions are owned by the contributor. V1 requires exact equality between the saved and registered schema versions; there is no general contributor migration callback.

Corrupt data and unsupported future wrapper, file, or record versions fail before restore. A known contributor schema mismatch fails during contributor preflight. Unknown optional contributors can be skipped with a warning; missing or unknown required contributor data can fail restore. See Persistence Format for the full compatibility rules.

Updating a project

Keep a copy of important save slots before changing a product’s serializer or contributor schema. Test representative saves with the target runtime and integrations in a disposable project or slot. Coordinate contributor schema changes with the system that owns that payload; do not edit encoded bytes or change version fields manually.

Slot identity remains the exact slot name and user index. The runtime does not rename slots, normalize names, or initiate map travel to satisfy a load request. Map availability and supported restore policy remain the host game’s responsibility.

See Restore Lifecycle for preflight and restore ordering, Slots and Autosave for slot behavior, and Troubleshooting for compatibility failures.