Devlog: A1, A9 and N8; v0.5 closed

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-13 09:41:16 -05:00
co-authored by Claude Opus 5.5
parent 880e001fbb
commit 98d86eb2da
2 changed files with 54 additions and 0 deletions
+3
View File
@@ -10,6 +10,7 @@ continuity.
- [docs/DEVLOG.md](docs/DEVLOG.md): what happened, newest entries at the bottom. - [docs/DEVLOG.md](docs/DEVLOG.md): what happened, newest entries at the bottom.
- [docs/GDD.md](docs/GDD.md): the game design. - [docs/GDD.md](docs/GDD.md): the game design.
- [docs/ORIGINALITY.md](docs/ORIGINALITY.md): binding rules for everything we make. - [docs/ORIGINALITY.md](docs/ORIGINALITY.md): binding rules for everything we make.
- [docs/STYLE.md](docs/STYLE.md): the look and sound. Every client colour comes from `Palette`.
- [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md): server-authoritative design and module map. - [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md): server-authoritative design and module map.
- [src/sim/tuning.gd](src/sim/tuning.gd): the one table of gameplay numbers. - [src/sim/tuning.gd](src/sim/tuning.gd): the one table of gameplay numbers.
@@ -37,6 +38,8 @@ continuity.
| `make discovery-check` | Starts a list server and a game server as processes and checks `--browse` finds the game both on the LAN (loopback) and through the list (about 15 s). | | `make discovery-check` | Starts a list server and a game server as processes and checks `--browse` finds the game both on the LAN (loopback) and through the list (about 15 s). |
| `make fuzz` | Feeds 1,000,000 malformed messages (`FUZZ_MESSAGES=N`, `FUZZ_SEED=N`) to every network parser and fails on any engine error or memory growth (about 40 s). | | `make fuzz` | Feeds 1,000,000 malformed messages (`FUZZ_MESSAGES=N`, `FUZZ_SEED=N`) to every network parser and fails on any engine error or memory growth (about 40 s). |
| `make client-captures` | Renders what a network client sees on the barge, gliding and landed, the build ghost allowed and refused, and a breakwater basin kept dry by the tide (`captures/client_<stage>.png`, about 4 min). Needs Docker. Look at them. | | `make client-captures` | Renders what a network client sees on the barge, gliding and landed, the build ghost allowed and refused, and a breakwater basin kept dry by the tide (`captures/client_<stage>.png`, about 4 min). Needs Docker. Look at them. |
| `make hud-captures` | Renders the HUD over a staged moment of play (three bots out, carried items, a wound) at 1280x720, in build mode, and at 3840x2160 (`captures/hud_*.png`, about 5 min). Needs Docker. Look at them. |
| `make style-captures` | Renders a hamlet and a dock with and without the woodcut print pass (`captures/style_*.png`). Needs Docker. |
| `make soak` | The 24-client network soak (N8): a real server and 24 headless `SoakPlayer` clients in three processes, each behind a `UdpRelay` adding 60 ms, +/-20 ms jitter and 2% loss each way, for two whole matches in real time (about 30 min, under `nice`). Fails on a world-hash mismatch, errors, unreadable packets, a client that didn't play every match, memory growth between matches, or a p99 tick over budget. `SOAK_MATCHES`, `SOAK_CLIENTS`, `SOAK_PROCS`, `SOAK_LATENCY`, `SOAK_JITTER`, `SOAK_LOSS` scale it. Results in `build/soak/report.txt`. | | `make soak` | The 24-client network soak (N8): a real server and 24 headless `SoakPlayer` clients in three processes, each behind a `UdpRelay` adding 60 ms, +/-20 ms jitter and 2% loss each way, for two whole matches in real time (about 30 min, under `nice`). Fails on a world-hash mismatch, errors, unreadable packets, a client that didn't play every match, memory growth between matches, or a p99 tick over budget. `SOAK_MATCHES`, `SOAK_CLIENTS`, `SOAK_PROCS`, `SOAK_LATENCY`, `SOAK_JITTER`, `SOAK_LOSS` scale it. Results in `build/soak/report.txt`. |
| `make soak-selfcheck` | About a minute: tampers with one client's world and checks the soak's comparison catches it and only it. | | `make soak-selfcheck` | About a minute: tampers with one client's world and checks the soak's comparison catches it and only it. |
| `make server-package-check` | Builds the server image with `packaging/docker/compose.yaml`, waits for it to be healthy, checks it is non-root and read-only, joins it with a headless client and stops it with SIGTERM (N7, about 1.5 min). Needs Docker. See `packaging/README.md`. | | `make server-package-check` | Builds the server image with `packaging/docker/compose.yaml`, waits for it to be healthy, checks it is non-root and read-only, joins it with a headless client and stops it with SIGTERM (N7, about 1.5 min). Needs Docker. See `packaging/README.md`. |
+51
View File
@@ -843,3 +843,54 @@ high-priority issues, and A3, A7, A12 and A13 deferred.
**Known gaps:** the soak's client memory growth (#39). The held item isn't drawn (A4). Nobody has played the game, and frame rate and feel are unknown (R6). No HUD or menus yet (A9, A10). The client's flood can show water a moment early if a breakwater arrives late; it is only drawn and used for prediction. **Known gaps:** the soak's client memory growth (#39). The held item isn't drawn (A4). Nobody has played the game, and frame rate and feel are unknown (R6). No HUD or menus yet (A9, A10). The client's flood can show water a moment early if a breakwater arrives late; it is only drawn and used for prediction.
**Pace:** v0.5 has only N8 left, open on the memory check, and v0.6 was due tonight. This is still more than a day behind, with about three days left. Next run: find the client memory growth in N8 with the new object counts. Then v0.6's high-priority issues: A1 (style guide), A9 (HUD), A10 (menus), A11 (map), A2, A4, A5, A6 and A8. **Pace:** v0.5 has only N8 left, open on the memory check, and v0.6 was due tonight. This is still more than a day behind, with about three days left. Next run: find the client memory growth in N8 with the new object counts. Then v0.6's high-priority issues: A1 (style guide), A9 (HUD), A10 (menus), A11 (map), A2, A4, A5, A6 and A8.
## 2026-11-13 (morning): A1, A9 and N8 done; v0.5 closed
**Start of run:** the project lock was still held by this task's own 05:03 run, which stopped three minutes in. It left uncommitted live-object counting for N8, and it never released the lock. Nothing else held the lock and no Tidewall processes were running, so this run carried on and finished that work. The fast-forward pull was a no-op. The Agents category had nothing addressed to this task, and nothing was posted.
**Done:**
- **A1 (#41), closed: the style guide.**
- `docs/STYLE.md` covers the palette, shape language, character proportions, shading, UI motifs, audio palette and a never list.
- `Palette` is the one table of client colours. Every colour scattered over the views now names its entry, with values unchanged. `test_palette` fails on a colour literal elsewhere in `src/client` or `src/app`, and on a palette entry the guide doesn't list.
- `Look` builds the sky, the grading (saturation 0.86, contrast 1.05), the sun and the woodcut print pass, for the match view and the capture scenes.
- The print pass (`folk_print.gdshader`) is a full-screen quad multiplied over the frame. It draws ink lines at depth jumps and creases, hatching in real shadow, and paper grain. Lines scale with screen height. Ground under the sea gets no ink.
- **A9 (#49), closed: the HUD.**
- Tide post at top centre, standing count and kill feed at top right, health and armour at bottom left, the boathook and five slots at bottom centre, materials and the build line at bottom right.
- Nothing depends on colour alone: numbers, words, hatching patterns, tier pips and notches carry the meaning.
- A new reliable **FEED** message (`NetFeed`) carries who is standing and the newest 16 placements with names, because snapshots only hold nearby players. Bots get crew names (`CrewNames`).
- `HudState` is plain data, worked out from the client or from a server's match.
- The project stretches canvas items from 1280x720.
- **N8 (#39), closed: the memory leak is found and the soak passes.** That closes v0.5, tagged `v0.5.0`.
- `SoakPlayer` kept a strong reference to the last world it played on until its client next asked it for a command, so finished islands stayed alive across a match change. That is a soak-tool bug; the real client has no SoakPlayer. It now keeps only the seed.
- `LiveCount` counts live Simulations and SimGrounds. The soak report now fails if, a minute into a match, a client process holds an island that isn't a client's world or one being made.
**Tests:**
- `make check` passes: parse, 524 tests, self-check and smoke.
- `make fuzz` passes with FEED included: 1,000,000 messages, 0 errors, 3 KB growth.
- Captures, all opened and looked at:
- `style_hamlet` / `style_hamlet_plain` and `style_dock` / `style_dock_plain`: ink outlines on pines, houses and the jetty, and hatching only under trees and on shaded walls.
- The first try hatched all the lit grass and drew a frame round the screen's edge. Both are fixed: the hatch threshold is now 0.055 linear, and the edges are skipped.
- `hud_720`, `hud_build_720` and `hud_2160`: the same layout at 1280x720 and 3840x2160.
- Item names were cut off ("Dock Carbin"). They now wrap onto two lines.
- **The instrumented soak, run before the fix** (and loaded by tests and captures I ran alongside):
- 24/24 clients through both matches.
- Client memory growth was 2.2, 6.2 and 2.4 MB, under the 16 MB limit this time. One process held a 9th live Simulation that no client referenced, which pointed at SoakPlayer.
- p99 tick 6.1 ms.
- **One world hash of 3,754 differed:** client 17 at tick 19500 of match 1. All the other clients agreed. The server's world changed between 19500 and 19501, and client 17 agreed again at the next sample. Opened as H13 (#80).
**Decisions and what I learned:**
- The print pass is drawn last (render priority max) and only multiplies. Transparent things drawn before it, the sea and the build ghost, are darkened but never overwritten. A pass that wrote the screen texture back would erase them, because that texture is copied before the transparent pass.
- Hatching thresholds are in linear light before tone mapping. Lit grass sits near 0.1 there, so anything above about 0.06 hatches lit ground.
- Canvas-items stretch from a 1280x720 base scales every Control and Label, and leaves 3D at the native resolution.
- `make check` takes over 10 minutes when other work is running, so run it in the background.
- **The soak after the fix passes:**
- 24/24 clients through both matches and told of the stop.
- 3,750 hashes compared, 0 differing.
- Worst client process growth 0.1 MB, with 0 extra islands. Server growth 0.8 MB.
- p99 tick with network 6.9 ms (simulation 2.6 ms), max 69 ms.
- 24.9 kbit/s down and 11.6 up per client, and 0.6 Mbit/s out of the server in all.
**Known gaps:** the soak's transient hash mismatch (#80), seen once in four runs since H12. The HUD has no menus or map yet (A10, A11), the held item still isn't drawn (A4), and nobody has played it on real hardware (R6).
**Pace:** v0.5 is closed, two days after it was due. v0.6 has A1 and A9 done; it was due last night. That is still more than a day behind, with about two and a half days left. B4, B8, M6, M7 and the other low or unprioritised issues stay deferred. **Next run:** H13 (#80), the soak's transient hash mismatch, because it's a multiplayer bug. Then A10 (menus and settings) and A11 (map and tide forecast), which a playable release needs most, then A2, A4, A5, A6 and A8.