# Playtest saves

Save files that came in with a bug report, or that were kept from a session worth re-reading.

**Nothing in here is committed** — `.gitignore` keeps the directory empty as far as git is
concerned, except for this file. They are somebody's game, not part of the project, and they go
stale the moment the rules move.

## What a save is

A seed and the list of moves made — a few hundred bytes of JSON. That is enough to rebuild the
whole game, which is why a replay can be emailed like a text file. Written by **Save replay** on the
play screen; a multiplayer game's copy lives on the server, under its data directory.

## How to open one

Open `replays.html` on the site (or a local `npm run serve:web`) and use **Open a save file** at the
bottom of the page — it takes a file straight off disk, no upload anywhere. Step through it frame by
frame to find the position being reported.

A save replays only under the rules it was dealt with; every save records them, and one written
before a rules change may stop part-way. That is expected, and it is why these are kept beside a
report rather than in the repository.

## Publishing one

A replay worth keeping for everyone goes in `public/replays/` instead, where the build publishes it
into the site's replay directory with an index entry.