Updates and saves

git pull
npm ci
npm run setup:assets     # updates only the asset bundles that changed

Each release is one commit on main. RELEASE-NOTES.md carries the history.

npm run setup:assets downloads the release matching your checkout, re-extracts only the bundles whose content changed, and deletes the asset files an earlier release shipped and this one no longer does. It deletes such a file only while its contents are exactly what a release shipped, so a file you edited or added under the asset folders is never touched; it lists the edited ones instead. npm run setup:assets -- --force re-extracts every bundle.

Saves live in the browser, never on a server. SAVE_VERSION migrates a save forward automatically, and an older build refuses a save written by a newer one rather than misread it. When a release cannot migrate saves it changes BUILD_EPOCH, and the first load of the new build clears the save, the town cache and the settings stored in the browser (saved character appearances are kept). The release notes of that release say so. Before updating across such a release, export your save from Settings → Save File → Export save and import it again if needed.

Written by release:site-sync from SETUP.md at v2026.09.22. Edit the engine document, not this page.