@@ -1680,3 +1680,57 @@ landed far apart.
|
|||||||
1. If the release has its binaries, verify them and close R5.
|
1. If the release has its binaries, verify them and close R5.
|
||||||
2. Otherwise A12, the tutorial (#52).
|
2. Otherwise A12, the tutorial (#52).
|
||||||
3. Then A13, gamepad and accessibility (#53).
|
3. Then A13, gamepad and accessibility (#53).
|
||||||
|
|
||||||
|
## 2026-11-15 (morning): A12, the tutorial
|
||||||
|
|
||||||
|
The v1.0.0 release is still a draft with no binaries, so R5 still waits on Eric. This
|
||||||
|
run took A12 (#52). Commit b604ced is on `main` after the v1.0.0 tag, like M7.
|
||||||
|
|
||||||
|
**The design.** The tutorial is an ordinary offline match. Only the server's rules
|
||||||
|
change; the lesson itself lives on the client.
|
||||||
|
- **Rules:** `MatchRules.tutorial()` is one player and no bots. `last_team_wins` is
|
||||||
|
off, so a player alone isn't the winner at once; only the tide, or nobody left
|
||||||
|
standing, ends it. `starting_kit` gives `Tuning.TUTORIAL_KIT`: a dock carbine with a
|
||||||
|
full magazine and 60 cartridges.
|
||||||
|
- **Command logs:** both new rules are recorded. Logs without them read with the
|
||||||
|
defaults (`OPTIONAL_RULE_KEYS`), so older logs still load.
|
||||||
|
- **Steps:** `Tutorial` (src/app) watches the predicted player, the world copy and the
|
||||||
|
FX. The steps are leap, glide, walk 12 m and jump, gather 15 with enough for a wall,
|
||||||
|
place a piece (a PLACE FX), hit something with a weapon (an IMPACT FX), and open the
|
||||||
|
chart then stand 1 m above the tide line after next for 2 s.
|
||||||
|
- **Card:** `TutorialCard` sits under the minimap. Every instruction names the
|
||||||
|
player's own bindings.
|
||||||
|
- **Pilot:** `TutorialPilot` plays the tutorial through `ClientInput`, setting the held
|
||||||
|
keys and actions and where it looks. It pauses half a second in build mode before
|
||||||
|
placing, as a person would; without that pause, the build capture caught the moment
|
||||||
|
after placing.
|
||||||
|
- **Menus:** a new `welcome` screen on first launch (until answered, saved as
|
||||||
|
`tutorial.offered`), a Tutorial button on the main menu, and `tutorial.done` saved
|
||||||
|
on finishing. `--tutorial` works on the command line.
|
||||||
|
|
||||||
|
**Tests:**
|
||||||
|
- `make check`: 745 tests, smoke ok. `test_menus` now opens with the tutorial already
|
||||||
|
offered, and its focus-order test includes the new button.
|
||||||
|
- `make tutorial-check` (new): 12 of 12 seeds finish, in 23–32 s of game time each.
|
||||||
|
- `tidewall --tutorial --autoplay --seed=7 --client-seconds=75`, in real time: done,
|
||||||
|
0 corrections.
|
||||||
|
- `make match`: ok, and the replay hash matches.
|
||||||
|
|
||||||
|
**Captures (software rendering), looked at:**
|
||||||
|
- `tutorial_move`, `tutorial_build` and `tutorial_tide`: the card under the minimap,
|
||||||
|
readable, with the step counter and progress line.
|
||||||
|
- `menu_welcome`: the offer, with both buttons and the focus ring on Start.
|
||||||
|
|
||||||
|
**Notes:**
|
||||||
|
- Most seeds land the player well above the line, so the tide step is mostly about
|
||||||
|
opening the chart and reading the numbers.
|
||||||
|
- The wording follows the code's "barge" and "sail". #72 (the launch fiction) may
|
||||||
|
change it.
|
||||||
|
|
||||||
|
**Next run:**
|
||||||
|
1. If the release has its binaries, verify them and close R5.
|
||||||
|
2. Otherwise A13, gamepad and accessibility (#53). It's the last workable issue in a
|
||||||
|
build milestone apart from the priority/low ones and #80, which is open until it
|
||||||
|
reproduces.
|
||||||
|
3. Then the Finishing steps: README status, comments on R6 and R7, and disable the
|
||||||
|
task.
|
||||||
|
|||||||
Reference in New Issue
Block a user