Jesse.MarkowitzandClaude Opus 5
06db36e5b5
The multiplayer set-up, the lobby, the start of a game, and four signals a remote client had never been sent. Reasoning, the preset table and what was verified how: CHANGELOG.md. - Co-op, Competitive, Cutthroat, Solitaire and Custom, on both screens, from one shared block — they had drifted, and each was missing a question the other asked. - A player reads the whole rule set before taking a seat, may leave a lobby or a running game, and keeps a seat across a reload. The host may clear a chair. The browser remembers every game it is in, not just the last one. - The start of a game is drawn: a handoff beat, an announcement, the code and type in the header. - Sound, the timetable flash, announcements and the just-drawn badge now reach a remote client; justDrawn goes to the seat that drew it and nobody else. - Played on StartOS, which found the rest: an Extra belongs to the player who played it, the board never named the Superintendent, bot seats were reported as absent players, and rule section numbers are out of every string a player reads. Also carries the previous session's Heavy Grade documentation work — asked again, answer unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016JczK5i33ZNSf2PtzZqdhS
29 lines
1.3 KiB
Markdown
29 lines
1.3 KiB
Markdown
# 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.
|