Godot save and restore
Makes progress reloadable after content changes or interrupted writes. It stores stable item and quest identities, validates incoming data and keeps a recovery path to the last usable save.
godot-save-state
See how it helpsWhen is it useful?
Use when saves must survive content changes or interrupted writes.
What does it help you do?
- Stores stable identifiers rather than runtime node references.
- Validates loaded fields before applying them to active scenes.
- Defines migration and recovery for older or damaged saves.
Try asking this
Add checkpoints to our adventure with collected keys and completed quests. Load a save from before an item was renamed, then a truncated file. Explain how missing content is handled and demonstrate recovery without overwriting the last valid checkpoint.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Godot — save state
Use when persisting Godot progress, settings, inventory or versioned player state.
Version and project gate
Inspect project.godot, config/features, .tscn and .tres files, export_presets.cfg without credentials, input actions, autoloads, renderer, physics backend and installed Godot executable. Distinguish Godot 3 from 4 before selecting APIs. Never turn a task into an engine upgrade without the user’s intent. Read the version-matching official reference when an API decision depends on it.
Work
Separate runtime Node references from serializable state with stable identifiers. Define save version and migration behavior, write to the intended user storage location and preserve the previous valid save during replacement. Validate loaded fields before applying them to live scenes.
Deliver
A save contract, explicit migration/recovery behavior and a load path that tolerates missing optional fields. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Do not execute arbitrary serialized objects or overwrite a valid save after a partially failed load.
Acceptance scenario
Resume an older save, truncate a copied save fixture, remove an optional content item and confirm a readable recovery choice. Follow the project’s execution and verification permissions. If execution or a target device is unavailable, provide the reproduction steps and name the remaining uncertainty; do not mark it passed.
Scope and sources
This skill belongs to Rune. Agent selection is restricted by Orqestria’s assigned-agent policy, including forced skill selection; instruction text alone is not an access control. These are original task workflows researched from official documentation, not a copied or endorsed vendor skill.
- https://docs.godotengine.org/en/stable/tutorials/best_practices/scene_organization.html
- https://github.com/godotengine/godot-docs/blob/master/tutorials/best_practices/project_organization.rst
Task-specific official references
Included files 1
SKILL.md