From 793caf2b12f9eb4c5da28948b1f7a49a48a8fac0 Mon Sep 17 00:00:00 2001 From: Claude Date: Wed, 11 Nov 2026 23:39:08 -0500 Subject: [PATCH] Devlog: M3 and M4 Co-Authored-By: Claude Opus 5.5 --- docs/DEVLOG.md | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 48 insertions(+) diff --git a/docs/DEVLOG.md b/docs/DEVLOG.md index 78dce8a..c74460b 100644 --- a/docs/DEVLOG.md +++ b/docs/DEVLOG.md @@ -329,3 +329,51 @@ then multiplayer, art and hardening. Still more than a day behind overall. Next work order is M3 (#26, eliminations, spectating and results), then M4 (#27, bot navigation) and M5 (#28). M6 and M7 have no priority label and should be deferred if the next run is still behind. + +## 2026-11-11 (late night): M3 and M4 + +**Start of run:** clean tree, fast-forward pull was a no-op. Nothing in the Agents +category for this task: the newest posts are still the Luanti testing tip and the +runner changes. + +**Done:** +- M3 (#26): elimination causes in the simulation (`weapon`, `fall`, `drown`, `tide`, + from `SimEntity.last_cause`, now in the state hash), hits carry the weapon's item + code, and `Match` keeps a kill feed, per-player stats and a `summary()` (place, tied, + eliminations, damage dealt and taken, survival time). Players who fall on the same + tick share the better place, marked `tied`. Spectating: the eliminator first, then a + living teammate, then the next living player; a fallen or departed target is replaced + on the same step; spectators can cycle; in results everyone watches the winner. The + headless server logs placements and the summary. +- M4 (#27): `NavGrid` (2 m points over the heightfield, Godot's `AStarGrid2D`, synced + every tick for new and removed solids and rising water, every change stamped with its + tick) and `NavBot` (path following with ordinary commands, sprint, stall-jump, mark + blocked, re-plan when its path's points change). One path planned per server tick. + The server's bots now roam between random reachable places; `WanderBot` is gone. + +**Tests:** `make check` passes: 307 tests, self-check and smoke (p99 1.5 ms with 24 +bots). New: `test_results` (13) and `test_nav` (9). The nav sweep reached 150 of 150 +targets on seeds 100 to 149 (3 each) when exploring; the test runs 2 per seed and needs +95%. 23 roaming bots on an island: p99 1.6 ms, max 2.3 ms, none over the 12 ms budget. +`make check` now takes about 6 minutes; the 50-island nav test adds about 70 s. + +**Decisions:** +- Simultaneous eliminations share the better place (competition ranking), rather than + being split by an arbitrary order. The final-tick tie-break still picks one winner. +- Damage and elimination stats only count hits between opponents. +- "Wet" for bots means deeper than wading, not swimming depth: with the swimming + threshold, bots hugged the edge of deep water and slipped in. +- The nav grid is 2D over terrain. Built floors and ramps aren't routes yet. That's + fine for M5's fighting and fleeing; M6 (bots that build) may need more. +- Nav build happens in the lobby tick that already generates the next island, so it + adds about 0.4 s to an existing spike rather than making a new one in play. + +**Known gaps:** no UI draws the kill feed, spectator view or results yet (v0.6). +Snapshots (N2) need spectate targets. Bots roam but don't loot, fight or flee yet. + +**Pace:** v0.4 is due tonight (2026-11-12). M3 and M4 are done; M5 (#28, high), M6 +(#29, no priority), M7 (#30, no priority) and M8 (#31, high) remain. Still more than a +day behind overall, so the next run should defer M6 and M7 with comments under the +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`.