in: Production, How to play, Interface
Saving and save migration
In the alpha Interface · facts checked 2 November 2026
Saving in Arborwake depends on the build you play. Each build keeps its own save in your browser, and none of them deletes an older save. This page explains what each build stores and how progress moves between them.
How it works#
Integrated alpha#
The Arborwake alpha saves to browser local storage under arborwake.game.progress.v1.
- Automatic and transactional: a change is saved in full before the game shows its result, receipt or effect. If storage fails, your wallet and services stay as they were.
- Safety copies: the save keeps the current state and the previous good state. If the current one is damaged, the previous one is recovered.
- One tab at a time: a writer lock stops a second tab from saving, and an older tab cannot overwrite newer progress.
- Rooms: each encounter action is checked by replaying the real turn engine and saved before its animation plays. A room cannot declare its own win. A completed room pays once, even after a reload. Reloading in the middle of a room records an interrupted attempt; it never resumes the room and never refunds the attempt.
- Threadway: your town position is saved every five seconds. When you leave town, you arrive at the measured point beside the road you took.
session.game version 1 holds the story scenes, observations and journal, the companion roster, side quests, home duties and buildings, pending rewards and your Threadway position.
Live preview#
The Live preview site saves under arborwake.alpha.progress.v1, with its own writer lock. Lessons are free, and one endurance is reserved before each other attempt.
Circuit Ranger prototype#
The Circuit Ranger prototype saves only when you choose Save home. It uses IndexedDB arborwake-save-v1 (store snapshots, version 1) and keeps the current and previous saves.
Save migration#
- Arborwake rename (31 October): on first use in a browser, the prototype copies the old-brand current and previous saves into
arborwake-save-v1. It never overwrites existing Arborwake saves or deletes the source. Skill kits now use the wire idarborwake.skills; older kits are converted on load. Only one compatibility module may recognise the retired name. - Alpha to integrated alpha (2 November): the integrated alpha reads the earlier alpha save once and leaves it untouched. It keeps your Supply, items and services, keeps a Sentinel or Warden class (anything else becomes Sentinel) and banks any carried cargo. Earlier room records are archived as "legacy records". They appear in Run records but do not advance the story, recruit anyone or grant Imprints. A journal entry explains the move.
- Services v1 to v3: a carried recovery parcel, now removed from the game, is refunded as 4 Supply.
- Memory Meadow: the alpha shows the new name, but the map's internal id is still
practice.
Development#
- Local development preview (1 November, uncommitted on
main):arborwake.overworld.progress.v1introduced the transactional save, writer lock and previous-good snapshot. The lead reports 8 systems browser tests passed, including a failed save and competing tabs. - Alpha: the lead's release browser tests cover return and reload, interrupted attempts and separation from the previous save.
- Open: CR-SAVE-01, the versioned schema for the full campaign and expeditions, is still open. The lead warns against appending new fields to these formats without that review.
See also#
Arborwake alpha · Live preview site · Circuit Ranger prototype · Controls
Sources#
b89f778c2:docs/ops/INTERFACES.mdb89f778c2:src/main-game/alpha/README.md69c7b5470:src/main-game/game/state.js69c7b5470:src/main-game/game/migration.js69c7b5470:src/main-game/threadway3d/final-preview.js82c3add0d:src/main-game/alpha/README.mdacfb2ff9b:docs/ops/agent-messages/2026-10-31-lead-arborwake-rename.md- docs/ops/agent-messages/2026-11-01-lead-services-integration.md (working copy, not in Git)