1 client local offline save and bootstrap cache
forgejo-actions edited this page 2026-07-15 12:43:13 +00:00

Client Local Offline Save And Bootstrap Cache

Client local persistence separates offline-owned gameplay state from bootstrap cache data that can be replaced by authoritative realtime snapshots.

How It Works

offline_save.json lives under local state and stores offline-owned state. bootstrap_cache.json lives under local cache and stores client bootstrap hints. Local playtest and editor-style prediction can enable local persistence; standalone network authority disables local ownership for server-owned state.

How To Use It

Use offline save only for data the local runtime owns. Use bootstrap cache for hints that make startup smoother but can be overwritten by server bootstrap. Do not treat cached scene position, loadout, or condition state as authoritative while connected.

Invariants

Quest and condition state can be LocalOffline only in offline modes. Scene/loadout cache can be ClientCache or WorldServer depending on authority. Realtime bootstrap wins over stale cached loadout or scene hints.

Debugging

Schema mismatch, quarantined documents, stale scene hints, and cached loadouts replaced by realtime bootstrap are expected recovery paths. Inspect the authority boundary before deciding which file should be edited or deleted.

Examples

Local playtest may ignore cached scene position and start from its requested test scene. A connected standalone session should accept the server bootstrap even if the cache contains an older scene.