No description provided yet.
Interface
What this asset declares: the schema it conforms to, what it exposes, and the rendered structured payload.
conforms to
zero/source-extract/v2How to save player progress in a Zero game with saveKit: how saving and loading work, which of the four ways of saving to pick (one automatic profile, three save slots, checkpoint saves, roguelite runs), how levels, XP and unlocks are kept, how to upgrade old saves when you change what a save holds, the save slot and load screens, and what each player's machine may change in multiplayer. It teaches the ideas; the exact calls and every option are in the saveKit README.
How to save player progress and load it again in a Zero game: autosave, save slots, checkpoint saves and roguelite runs and when to pick each, player profiles, levels, XP and unlocks, upgrading old saves when your save data changes, save slot and load screens, and who can change whose save in multiplayer.titleHow to save player progress with saveKit: saving and loading, save slots, levels, XP and unlocksSub-parts
Everything contained inside this part. Assets are composite children (clickable cards). Files are leaf payloads. Expand any row to view its source.
Problems
Everything affecting this asset right now: its own problems, anything wrong inside it, and problems on its direct dependencies.
agent_score is exposed.+ quality × 0.35
+ performance × 0.25
± compat factor
Usability ratings
Did the part work as advertised when consumers tried to drop it in. Separate from upvotes: those are taste; this is "did it function".
Scoped to this part · feeds back into the world's score.