Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Extend the save loader for [game] from [old format versions] to [new version]. Inspect the current serializers, stable object IDs, and load order. Write a compatibility table showing which versions are supported and how missing fields receive deliberate defaults. Keep a separate fixture for each supported version.
Implement conversion as an inspectable data step before reconstructing the game world. Validate the converted result before committing a new save. Preserve the original fixture or last usable save if reading, validation, conversion, or writing fails. An unknown future version should receive an understandable response rather than being guessed into the current schema.
Verify a fresh load, each supported migration, missing optional fields, damaged required data, and a failed write using disposable test saves. Confirm restored progress and identity, not merely a successful parse. Report compatibility limits and the exact fixtures checked.Make this prompt yours
Use when changing saved progress, not when merely changing a settings label. Supply sanitized historical save fixtures.
You might also hear
- save migration
- game versioning
- schema conversion
- old save
- backward compatibility
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Supported: Original migration template. Godot documents selecting and reconstructing persistent objects; conversion, fixtures, validation, and retained recovery copies are proposed requirements rather than tutorial guarantees.