Game save migrations
A saved game carries progress across releases. Saveglint keeps migration code and sample saves in the same AI coding conversation so you can inspect how old data reaches the next version.
function migrate(save: SaveV1): SaveV2 {
if (save.version !== 1) throw new Error("version");
return { ...save, version: 2, inventory: [] };
}- Connection
- Base URL, credentials and a reachable server.
- Project
- Test an empty inventory, a damaged save and an unsupported newer version while preserving the original file on failure.
- Review before applying
- Compare actual behavior with the expected result. If a check fails, investigate it before applying more changes.
function migrate(save: SaveV1): SaveV2 {
if (save.version !== 1) throw new Error("version");
return { ...save, version: 2, inventory: [] };
}Develop a save change without losing its history
A new game feature can change the meaning of data players already have. Saveglint is a Windows AI coding workspace for discussing that change with the project open and the existing save format in view. Start by separating the format currently in use from the format you want, then explain what must survive the transition. The assistant's proposal should answer that compatibility question.
The sample migration from one save version to another provides a concrete development example. Ask for inspection of the loader, version check and code that supplies new fields. Work with copied fixtures, including a representative older save and a version the application should reject. Saveglint does not provide a finished migration system; you develop and review the behavior in your own game code.
You can select an uncensored AI model when one is available through a supported OpenAI-compatible or Anthropic endpoint. Add required credentials and check the connection's context and tool support, which depend on the model and server. Read the proposed changes, run your project tests and reopen migrated fixtures in the game. Confirm both preserved values and newly introduced fields before relying on the change.
Preparing a save-format change
Which save files should I use during development?
Use disposable copies representing supported older versions and the new format. Include a rejected version as a separate case. Keep originals recoverable, and explain which values should remain unchanged after each migration rather than checking only whether loading succeeds.
Does adding a version number complete a migration?
No. Inspect how existing fields are preserved and how new fields receive meaningful values. The loader must also handle unsupported input appropriately. Test the resulting game state, because a version label alone says little about compatibility.
Should generated migration code touch players' original saves first?
Develop against copies and review every proposed write. Establish the expected output from known input before considering real data. Saveglint's sample illustrates a coding task; it is not evidence that any production save has been migrated safely.
Does an uncensored model change data-handling responsibility?
No. That label concerns your selected model, whose service and server still determine capabilities and restrictions. A local model needs a separately running server and does not make external tools local. Review what save context you share.
Saveglint · Updated 2026-10-25
