SAVE ARCHITECTURE
Save Data & Schema Planner
Draft versioned save fields, types, required values, and migration notes as JSON.
VERSIONED SCHEMA
Plan your save format
| Field | Type | Required | Remove |
|---|---|---|---|
Save data and schema guide
Save data is a long-lived contract. A small schema decision today can become a migration problem after months of patches or a live-service reset.
Use the result as a balancing or prototyping starting point, then validate it against your own game data and playtests.
Version every format
Store an explicit schema version and write migrations from known older versions. Prefer additive changes with safe defaults, and never silently discard fields a newer client may need.
Worked example: adding a quest flag
Keep the save version at 2 while adding an optional quest flag with a safe false default, or increment to version 3 if the format contract changes. A migration should name the old version, add the field, and preserve all unrelated player data.
Assumptions and limits
This planner describes fields and required flags; it does not generate serializers, migrations, checksums, conflict resolution, cloud-save policy, or secure storage.
A practical production check
Record the assumptions behind the estimate, test a small and a worst-case scenario, then compare the result with a profiler, playtest, or representative content sample. This turns a one-off number into a repeatable design decision.
Prototype first, tune second
A calculator or generator can expose relationships quickly, but the final values should be checked against player experience, content cadence, and the rest of your economy or combat system.
Frequently asked questions
Does this replace playtesting or profiling?
No. It provides a fast, repeatable baseline so testing starts from informed numbers rather than guesses.
Can I use this for a shipped game?
Yes, as a planning and comparison aid. Confirm critical budgets with measurements from your target hardware, network conditions, or production data.
Does my data leave the browser?
No. These tools run locally in your browser.
Privacy note: save schema planning happens in your browser. Nothing is uploaded.