Saves and Settings

The whole game persists as one Dungeons entity per user — a single optional save plus settings — through the same auth/unauth single-blob pattern as clicker.

How it works

A Save is the full run state: player (position, direction, party monsters, inventory, respawn location), the active tilemapKey, and per-map world state (chest opened-flags). useReadDungeons loads the blob at page setup (authed: dungeons.readDungeons; anonymous: localStorage DungeonsStore); the Title scene's Continue resumes dungeons.save (enabled only when one exists), New Game starts from a fresh Save. Saving is manual — the world menu's Save option calls saveData, which assigns the active save onto dungeons.save and persists via useSave — there is no autosave.

No legacy shapes — per the latest-shape-only convention, dungeonsSchema and the Dungeons constructor accept only the current single-save shape; a blob that fails to parse starts fresh. If real save slots are ever wanted, design them as slots (their own ids, names, timestamps) rather than resurrecting the old array.

Settings — the Settings scene edits dungeons.settings, shared across runs: text speed (Slow/Mid/Fast, driving dialog animation delay), battle style, animations on/off, sound on/off + volume percentage, and theme mode (recoloring the UI glass panels via ThemeModeColorsMap). Settings persist in the same blob write.

Achievements — seven, all on the dungeons.saveDungeons trigger path. Two count saves (DungeonCrawler: 1, DungeonMaster: 50); five are play milestones whose condition reads the saved run when the player checkpoints (unlock pipeline): MonsterCatcher (party size ≥ 2 — the starter is one, so two means a capture), MonsterTrainer / MonsterElite (any monster at level 10 / 25), MonsterCollector (every species present in the party), and DungeonHomeowner (every chest discovered so far opened, across all maps' WorldData). Since saving is manual, all of these reflect play, unlike the clicker's autosave-driven counts.

Procedures

Key files

Paths relative to packages/app.

Notes

• A party wipe respawns the player at player.respawnLocation with the party healed (useWorldPlayerStore.respawn / healParty) — in-session state is kept, not rolled back to the last save.