A12: Tutorial

A short, skippable tutorial on an island of your own: leave the barge, glide
down, walk and jump, cut materials with the boathook, place a wall, aim and
fire, and get above the line the tide will reach after its next rise.

- MatchRules.tutorial(): one player, no bots, last_team_wins off (alone is
  not a win, only the tide or a fall ends it) and starting_kit (a dock
  carbine with a full magazine and 60 cartridges, Tuning.TUTORIAL_KIT).
  Both rules go in command logs; older logs read with the defaults.
- Tutorial watches the client's own view (predicted player, world copy,
  FX) and moves on when each step is done. Instructions name the player's
  own key bindings. TutorialCard shows it under the minimap.
- TutorialPilot plays it through ClientInput for --tutorial --autoplay,
  the tests and make tutorial-check (12 seeds, all finish).
- First launch offers it (welcome screen, remembered in settings); it is
  always on the main menu; Leave in the pause menu skips it. Finishing is
  saved. --tutorial on the command line.
- make tutorial-captures; PLAY.md, the man page, ARCHITECTURE.md and
  CLAUDE.md updated.

Closes #52

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-15 05:47:31 -05:00
co-authored by Claude Opus 5.5
parent 4ea170175d
commit b604ced923
32 changed files with 1110 additions and 23 deletions
+11 -2
View File
@@ -523,8 +523,17 @@ game starts an offline match, or joins a server with `--connect`. Without a wind
(`tools/godot.sh` is always headless) a mode has to be asked for. `--autoplay` puts a
small script at the controls and `--client-seconds=N` quits after N seconds with one
JSON line saying how far the client got, which is what `make client-check` reads.
There are no menus yet (N6, A10) and no HUD (A9): one line of text says when the
client is connecting, in the lobby or watching.
With a window and no mode, `AppShell` opens the menus (A10) and the HUD (A9) draws
over each match.
The tutorial (A12, `--tutorial` or the menus) is an ordinary offline match under
`MatchRules.tutorial()`: one player, no bots, `last_team_wins` off so being alone
isn't a win, and `starting_kit` putting `Tuning.TUTORIAL_KIT` in hand. The server
rules are the only change to the game; the lesson itself is client-side. `Tutorial`
watches what the client already has (its predicted player, its copy of the world and
the FX it is sent) and moves on when each step is done; `TutorialCard` shows it on the
HUD with the player's own key names; `TutorialPilot` plays it through `ClientInput`
for `--autoplay`, the tests and `make tutorial-check`.
## Performance budgets