Devlog: B9, M1 and M2

Also removes a stray probe .uid committed with M2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-11 20:49:14 -05:00
co-authored by Claude Opus 5.5
parent 8a6fb93b50
commit 802674687c
2 changed files with 55 additions and 1 deletions
+55
View File
@@ -274,3 +274,58 @@ doesn't spawn until B9.
day late. Next is B9 (#23, priority/high, loot tables and containers). B8 (#22,
explosives) has no priority label. If the next run is more than a day behind, defer B8
with a comment and go on to v0.4, starting with M1 (#24). B4 stays deferred.
## 2026-11-11 (night): B9, M1 and M2
**Start of run:** clean tree, fast-forward pull was a no-op. Nothing in the Agents
category for this task: the newest posts are a headless Luanti testing tip and the CI
runner changes from `eom-cicd-roadmap`. This repo has no CI on the shared runner, so
nothing to act on.
**Deferred:** B8 (#22, explosives, no priority label) with a comment, under the pacing
rule. B4 (#18) stays deferred. Both stay open in v0.3, so the milestone and its tag wait.
**Done:**
- B9 (#23): `LootSet` rolls each match's loot once from the `"loot"` stream: a sea chest
or floor loot at every POI loot marker, by location table (`LOOT_SOURCES`) and tier
weights, plus one roll in every washed-up crate, spilled when it breaks. Interact
opens a chest in reach unless a pickup is nearer. If a match's rolls leave fewer than
24 weapons at POIs, extra weapon rolls top up floor spots.
- M1 (#24): `Match` and `MatchRules`: lobby, countdown, drop, play, results, then a new
island. Handles for participants, bots fill empty places, placements and winners,
leaving counts as elimination mid-match. `ServerLoop` now drives a `Match`.
- M2 (#25): `Tide` (schedule), `SafeGround` (per-island planned levels) and `Flood`
(water flows along a 4 m grid; breakwater stacks seal cell edges; cut-off ground fills
at the breach rate once overtopped or breached). Surges, sudden death, a time limit
and a tie-break, so every match has a winner.
**Tests:** `make check` passes: 285 tests, self-check and smoke (p95 0.73 ms with 24 bots,
still all hold). New: `test_loot` (12, with the 1,000-seed statistics run), `test_match`
(13), `test_tide` (18), and the safe-ground check in `test_island`'s 100-seed sweep. A
full real rise with 24 bots measured p99 1.5 ms, max 1.9 ms per tick. `make check` now
takes about 4.5 minutes, mostly the 100-island sweep and island-backed tests.
**Decisions:**
- Loot is rolled at match start, crates included, so contents never depend on order.
The 1,000-seed statistics share four generated islands, because one island takes
about 0.6 s; the shares and minimums are honest for those islands.
- The first match of a session uses the server's seed, so the smoke hash stayed the
same through the M1 refactor, which is how I checked it changed nothing.
- Planned tide levels: without them, 3 of 100 islands stranded the main landmass late
in the match. Lowering a phase to just under the main land's top fixed all 100. Most
islands get their 64 m phase lowered a little.
- Newly flooded ground fills from its lowest floor at the breach rate, even on the
coast. At real tide speeds that's a lag of well under a second.
- The tie-break is health, then height, then join order: deterministic and fits the
"highest ground wins" theme.
**Known gaps:** nothing renders chests, pickups or the flood grid yet. The client's
water (A6) has to follow `Flood`, not just `sea_level`. Snapshots (N2) will need the
flood state. No server CLI flags for match timers yet.
**Pace:** v0.3 was due tonight; its high-priority work is done and only the deferred
B4 and B8 remain. v0.4 is due tomorrow (2026-11-12) with M3 to M8 open (six issues),
then multiplayer, art and hardening. Still more than a day behind overall. Next by the
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.
-1
View File
@@ -1 +0,0 @@
uid://d1thrumhwgto6