From df367d691aa2a32ba6d5695a395dfd510ecdd423 Mon Sep 17 00:00:00 2001 From: Claude Date: Sat, 14 Nov 2026 07:16:07 -0500 Subject: [PATCH] Devlog: H3 and H4 Co-Authored-By: Claude Opus 5.5 --- docs/DEVLOG.md | 53 ++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+) diff --git a/docs/DEVLOG.md b/docs/DEVLOG.md index 6e6ccff..575954a 100644 --- a/docs/DEVLOG.md +++ b/docs/DEVLOG.md @@ -1214,3 +1214,56 @@ high-priority issues, and A3, A7, A12 and A13 deferred. - Still about a day behind the milestone dates, but every release-path item except R3, R4 and R5 is done, and both packages are checked outside the repo. **Next run:** H3 (`make balance` over at least 200 matches is about 100 minutes of bot matches under `nice`, so start it early and write `docs/BALANCE.md` while it runs), then H4 (soak, which also tries to reproduce H13 with `SOAK_CLIENTS=8`). R3 and R4 after that. + +## 2026-11-14 (morning): H3 and H4 done + +**Start of run (05:03 ET Saturday):** the lock was free and taken fresh. The pull was a no-op, and the tree was clean. Nothing in the Agents category was addressed to this task. + +**H3 (#56), closed: balance pass.** The full write-up is in `docs/BALANCE.md`. +- `make balance` (`tools/balance.sh`, `BalanceReport`): 200 bot-only matches in four processes under `nice`, about 15 min. It reports length quantiles, players standing every two minutes, causes of death, eliminations by weapon and by difficulty. The targets are `BALANCE_*` in Tuning; the GDD has a new Balance section, which sets the weapon limit at 35%. +- **Before:** median 5.0 min, 3.4 of 24 standing at 2 min, the boathook 41% of eliminations. **After** (seeds 1001–1200): median 13.1 min, p10 9.2, p90 14.6, rivet repeater 31.7% at the top. Passes. +- **Findings from tracing single matches:** + - **Bug:** bots leapt from the barge on a fixed timer and landed hundreds of metres short. `NavBot._ride` now waits for gliding reach, or for the barge to start drawing away from the spot. + - Unarmed bots started brawls. Bots hunted the whole island. Nobody disengaged. The tide's squeeze came at about 9 minutes. +- **Changes:** + - Landing spread. + - Brawls only against whoever hit you. + - New opponents picked out only within 30 m. + - Roam within 60 m, then hold for 45 s. This was the big one. + - Unarmed bots run from guns; normal and hard break off when hurt. + - Wider aim error. + - Repeater damage 17 to 15. + - Tide: lower early levels and longer holds; the whole schedule plus sudden death is 17.75 min. +- **Tried and dropped:** doubling `LOOT_MIN_POI_WEAPONS`. The leap bug was the cause, not loot. +- **Test fallout:** + - Several tests leaned on old bot luck. Idle bots in the brain tests are now pinned. + - The offline-client test brings the scripted player down directly. + - The replication test keeps the scripted player alive until it has built, and breaks one prop itself. + - `make match` and the scripted-player test move to seed 29. On seed 2 the scripted player now dies in a landing fight. +- **Still open:** + - About 18 of 24 bots still fall in the first two minutes. Noted on #74, with a traced cause: bots leave an emptied hut and trek off unarmed. + - Hard bots now win 74% of matches. + - The longgun and harpoon gun are rarely the finishing weapon. + +**H4 (#57), closed: long-run stability.** +- `make stability` (`tools/stability.sh`, `StabilityReport`): one server process, 50 bot matches back to back, unthrottled, with resident memory sampled every 5 s. It fails on a crash, a hang (over 240 s a match), an error, a match with no winner, or a memory trend after the first five matches. +- The first run had no crash, hang or error, but found **two leaks**: + - `ServerLoop` kept every tick's duration, about 21 MB a day, and sorted all of it for every progress line. It's replaced by `TickTimes`: an exact 1 µs histogram plus the rare slow ticks, in fixed memory. + - Resident memory grew 28 MB a match (905 MB by match 42) from glibc's per-thread malloc arenas, because each island is built on a worker thread. Measured over 15 matches: `MALLOC_ARENA_MAX=2` grew in steps, `=1` stayed flat, and tick time was unchanged. The server launchers (tarball, .deb, Docker, systemd) and `tools/godot.sh --server` now set it to 1 unless already set. +- **After:** 50 matches in 756 s, exit 0, no errors, static memory +1.6 KiB a match, resident +145 KiB a match and flat at 204 MB. No seed crashed, so there's no crash seed for a regression test. + +**H13 (#80):** an 8-client, one-match soak compared 375 hashes with 0 differing. Still not reproduced. + +**Tests:** +- `make check` passed (663). +- Also passed: `make bot-matches` (easy won 3 of 20, 2.6% drowned), `make match` (seed 29), `make dist-check` and `make server-package-check`. +- `make balance` and `make stability` pass as described above. + +**Pace (07:20 ET Saturday):** +- Closed this run: H3 and H4. About 49 hours remain to Monday 08:00. +- v0.9 still has H6 (visual QA), H13 (the bug) and the low-priority H8, H10 and H14. v1.0 has R3, R4 and R5; R6 and R7 wait on Eric. +- **Dependency snag:** H6 depends on A7 (visual effects), and R4 depends on H6. A7 is open and was deferred for having no priority label, along with A3, A12, A13, B4, B8, M6 and M7. So the next run has a choice: + - do A7 (it's visual polish and fits H6's capture pass), or + - run H6 with A7's effects noted as missing. + +**Next run:** R3 (docs; every documented command must be run, so budget for it). Then A7 or H6 as above, then R4.