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 is a Resource you serialize yourself. Level content loads through AssetServer and scene spawn (bevy-asset-scenes). A scene spawn is not a player slot.
• Format: progress structs use serde and RON. The file holds primitives and a version field. Entity ids and asset handles stay out of the file.
• Schedule: write the slot from an explicit request system. Do not write the file from every Update frame.

serde and ron sit beside Bevy. The progress type is a normal resource.