Save Systems
Design save/load for game state, choosing what to serialize, file formats, save slots...
Install
npx skills add gamedev-skills/awesome-gamedev-agent-skills --skill save-systems -g -a claude-code -y- Repository
- gamedev-skills/awesome-gamedev-agent-skills6.4k
- Category
- Design
- Updated
- 8d ago
- License
- Apache-2.0
- Context cost
- Mediumabout 2,204 tokens
- Runs scripts
- No, instructions only
What it does
Design save/load for game state, choosing what to serialize, file formats, save slots, atomic crash-safe writes, schema versioning and migration, and autosave. Engine-neutral. Use when the user mentions save system, save/load, game state persistence, save slots, autosave, save file corruption, or migrating old saves to a new version.
Save systems
A save file is a serialized snapshot of game state that survives restarts. The hard parts aren't writing bytes, they're choosing what to save, writing it so a crash mid-save can't corrupt it, and reading old saves after you ship a patch. Get those three right and the rest is plumbing.
When to use
- Use to persist progress: player stats, inventory, world flags, settings, positions, across sessions and game updates.
- Use to design save slots, quicksave/autosave, and crash-safe writes.
- Use when old save files break after a content/code change (versioning & migration).
When not to use: for Roblox cloud persistence specifics, use
roblox-datastores. For the data model the save serializes (resources/SOs), use
godot-resources / unity-scriptableobjects. For Godot's FileAccess/
ResourceSaver and user:// paths, defer to the Godot engine skill while
applying the patterns here.
