Bevy world saves
Saves meaningful world data rather than temporary engine handles. It restores relationships using stable identities and handles older formats or missing content without discarding the last valid world save.
bevy-world-persistence
See how it helpsWhen is it useful?
Use when a rebuilt Bevy world must restore saved entities and their relationships.
What does it help you do?
- Separates persistent domain identifiers from temporary engine Entity handles.
- Defines save versions, missing-content handling and reference reconstruction order.
- Preserves an earlier valid save while preparing bounded format migrations.
Try asking this
Save our colony with workers assigned to buildings and items in storage. Reload after runtime entity IDs have changed, then test a missing building type. Rebuild references in a defined order, explain unresolved content and preserve the previous valid save during a failed migration.
Detailed documentation
Read the skill’s original instructions, examples and checks in their authored language.
Show less
Bevy — world persistence
Use when implementing Bevy saves, world serialization, replay or stable entity references.
Version and project gate
Inspect Cargo.toml, Cargo.lock, Rust toolchain, exact Bevy release, plugin compatibility, feature selection, schedules, state definitions, asset roots and target backend. Read the matching migration guide before using newer examples. 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 persistent identifiers and domain data from transient Entity handles. Define schema versions, missing-content behavior and dependency reconstruction. Choose reflection/serialization facilities available in the pinned release. Restore in an order that resolves references without retaining old-world handles.
Deliver
A save/restore contract and bounded migration path with an untouched previous valid save. Keep the change in the existing project structure; separate actual observations from the proposed acceptance scenario below.
Failure to prevent
Serializing a raw Entity value is not a portable identity contract across rebuilt worlds.
Acceptance scenario
Reload into a new world, remove optional content, load an older save and resolve cross-entity references without duplication. 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 Talon. 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.
Included files 1
SKILL.md