Bevy save and load

When to use

Load this when a design asks to persist player progress. Route asset and scene spawning to bevy-asset-scenes. Keep save bytes as data you serialize yourself until a current docs page names a format.

ECS shape

What exists: app-wide progress can be a Resource (see bevy-data-resources). Level content loads through AssetServer and may spawn with spawn_scene / queue_spawn_scene (bevy::scene, docs.rs latest, 0.20.0).
What was checked and rejected: https://docs.rs/bevy/latest/bevy/scene/struct.DynamicScene.html returned 404 on 2026-10-11. The live scene index documents Scene and bsn!, not a save-file serializer. Do not call DynamicScene::serialize from this skill.
Schedule: no save system is specified here. Do not invent a filesystem write inside Update.

Coming from Godot

Godot idea	Bevy idiom
Resource file for designer data	An asset `Handle`, or a `Resource` you own in code
Packed scene instance	`Scene` spawn on `bevy-asset-scenes`
Player save slot	Leave it as data you have not serialized yet. Check the docs before naming a slot format.

bevy-save-load

Bevy save and load

When to use

ECS shape

Coming from Godot