diff --git a/docs/DEVLOG.md b/docs/DEVLOG.md index c74460b..e1577d8 100644 --- a/docs/DEVLOG.md +++ b/docs/DEVLOG.md @@ -377,3 +377,64 @@ day behind overall, so the next run should defer M6 and M7 with comments under t pacing rule and do M5, then M8. M5's acceptance needs 20 complete bot-only matches; a full tide is about 18 minutes of game time, so that batch should be a separate make target run under `nice`, not part of `make check`. + +## 2026-11-12 (early morning): M5 + +**Start of run:** clean tree, fast-forward pull was a no-op. Nothing new in the Agents +category for this task, and nothing posted. + +**Deferred:** M6 (#29, bots that build) and M7 (#30, duos and revive), both without a +priority label, with comments, under the pacing rule. Both stay open in v0.4, so that +milestone and its tag wait, like v0.3's. + +**Done:** +- M5 (#28): `BotBrain` and `BotWorld`. Bots pick a landing marker near the barge's + route, loot (items in view, chests, then the next marker on the map), fight opponents + they can see with a clear line, bandage themselves when nobody is in view, and leave + for ground the coming tide won't reach when the time left only just covers the walk. + Three difficulties set reaction time, sight range and aim error. The server mixes + them; `--bot-difficulty` overrides. `make bot-matches` plays whole bot matches. + +**Tests:** `make check` passes: 322 tests, self-check and smoke (p99 2.0 ms with 24 +bots, none over budget). It now takes a little over 7 minutes. New: `test_bot_brain` +(14) and a config test. `make bot-matches` logic on seeds 101 to 120: 20 of 20 matches +with a winner, none by the time limit; 453 deaths by weapon and 7 by drowning (1.5%); +mean place easy 13.7, normal 11.8, hard 12.0; eliminations 132, 137, 186; wins 2, 9, 9. +Hard beat easy 20 to 0 in duels. Worst match p99 2.3 ms; 21 of about 226,000 ticks over +the 12 ms budget. That batch ran before the last change to the batch's own pass/fail +rule (see decisions), so the numbers are real but the full 20-seed run hasn't been +repeated through `make bot-matches`; a 2-seed run through it passed. + +**Decisions and what I learned:** +- Safe ground is the dry land joined to the island's highest walkable ground, so it + only shrinks. My first version used the largest dry piece per phase. On a two-summit + island the largest piece changed summits between phases, and bots left a dry summit + to swim to the other and drowned (13 in one match). +- Human players can be stranded the same way: on a summit that is dry for one more + phase but cut off from the last ground. The map and forecast (A11) should show the + last ground. Noted on #74. +- Most loot markers are inside huts, whose 1.4 m doors the 2 m nav grid can't see, so + at first bots opened almost no chests and ended matches unarmed, standing together + until sudden death. Bots now walk the points of interest's own routes in and out + (`Poi.routes`), keeping to the line between points so they don't catch on stairs. +- A path search to a cut-off goal explores the whole island: about 70 ms. `NavGrid` + now labels regions at build and refuses those goals at once. Regions are as the + island was at the start; a wall built later can still cause a slow search. +- Bots open fire only inside a range scaled by their aim, so easy bots don't empty + their magazines at the horizon. Ammunition is scarce: one pickup with each weapon. +- The batch check first demanded easy > normal > hard in mean place. Over 20 matches + hard and normal aren't separated by place (they are by eliminations), so the check + asserts what holds: easy places worst and hard takes the most eliminations. +- The boathook doesn't damage players at all (#73, a bug), so unarmed bots ignore + opponents. + +**Known gaps:** bots don't build, break crates, or use powder kegs and the line +thrower. Seed 101 had 4 drownings in one match, untraced (#74). Most chests stay +closed in a match. Nothing renders bots, shots or pickups yet. + +**Pace:** v0.4 was due tonight (2026-11-12) and M8 (#31, the offline match gate) is +still open; v0.5 Multiplayer is due at the end of today and hasn't started. That is +more than a day behind, with four days left. M8 is next: it needs a scripted client, +`make match`, a seed-and-command-log replay, and captures at each stage. After it, +N1 (#32) onward; multiplayer is core and isn't deferred. To make Monday, v0.6 will +have to be cut to its high-priority issues, and A3, A7, A12 and A13 deferred.