Devlog: B5, B6 and B7
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -223,3 +223,54 @@ unverified.
|
|||||||
finish about a day late. Next by the work order is B4 (#18, editing placed pieces). It
|
finish about a day late. Next by the work order is B4 (#18, editing placed pieces). It
|
||||||
is priority/low, so if the next run is more than a day behind, defer it with a comment
|
is priority/low, so if the next run is more than a day behind, defer it with a comment
|
||||||
and take B5 (#19, inventory), then B6 (#20) and B7 (#21).
|
and take B5 (#19, inventory), then B6 (#20) and B7 (#21).
|
||||||
|
|
||||||
|
## 2026-11-11 (evening): B5, B6 and B7
|
||||||
|
|
||||||
|
**Start of run:** clean tree. Nothing in the Agents category for this task. The newest
|
||||||
|
post there is a headless Luanti testing tip from another task, not relevant here.
|
||||||
|
|
||||||
|
**Deferred:** B4 (#18, priority/low) with a comment. v0.3 was due tonight with six
|
||||||
|
issues open and v0.4 is due tomorrow, so the build is effectively more than a day behind.
|
||||||
|
|
||||||
|
**Done:**
|
||||||
|
- B5 (#19): `ItemDef` resources built by `ItemCatalog` from `Tuning.WEAPONS`, `ITEMS`
|
||||||
|
and the new `AMMO` table. `Inventory`: five slots plus the boathook at selection 0,
|
||||||
|
ammunition outside the slots with caps, pickup entities, and pick up, drop and swap,
|
||||||
|
each once per press. The new `BUTTON_DROP` is bit 8. The simulation now marks
|
||||||
|
players eliminated at 0 health, emits `eliminated` with the last attacker, drops
|
||||||
|
everything they carried, and ignores their commands.
|
||||||
|
- B6 (#20): `Weapons`. Server-side fire rate, magazines and reloads, and seeded spread
|
||||||
|
with aim, bloom and movement terms. Hitscan traces in 16 m segments, and projectile
|
||||||
|
entities fall under gravity. Hits land on terrain, solids (pieces and props take
|
||||||
|
damage) or player boxes. Armor takes damage before health, and there are headshots
|
||||||
|
and linear falloff.
|
||||||
|
- B7 (#21): eight slot weapons, adding the rivet repeater and the harpoon gun. Four
|
||||||
|
tiers: rusted, seaworthy, brass_fitted and captains. The line thrower pulls the
|
||||||
|
shooter. `Consumables` adds the tar patch as a fourth consumable. Use is timed,
|
||||||
|
validated and interrupted by slot change, drop, sprint, swim or elimination.
|
||||||
|
|
||||||
|
**Tests:** `make check` passes: 247 tests, self-check and smoke (p95 tick 0.61 ms with
|
||||||
|
24 bots). New suites: `test_inventory` (18), `test_weapons` (22) and `test_roster` (14,
|
||||||
|
including data validation over every item).
|
||||||
|
|
||||||
|
**Decisions:**
|
||||||
|
- The issues ask for "resources", and CLAUDE.md says numbers live only in `tuning.gd`.
|
||||||
|
Both hold: `ItemDef` is a `Resource`, but `ItemCatalog` builds every definition from
|
||||||
|
the Tuning tables, so a new weapon is one table entry.
|
||||||
|
- Recoil on the server is bloom, extra spread that builds in sustained fire. It only
|
||||||
|
recovers on ticks the weapon is ready, otherwise automatics never bloomed. Camera
|
||||||
|
kick is presentation and comes with the client.
|
||||||
|
- Shots trace from the eye, not the third-person camera. That needs reconciling when
|
||||||
|
the client fires (noted on #20 for N4 and the client work).
|
||||||
|
- Taking damage doesn't interrupt a consumable. Sprinting does.
|
||||||
|
- Eliminated players skip their commands entirely. M3 decides what happens to them
|
||||||
|
next (spectating, removal).
|
||||||
|
|
||||||
|
**Known gaps:** nothing renders pickups, projectiles or shots yet, and no client sends
|
||||||
|
fire, interact or drop. The powder keg can be carried but not thrown until B8. Loot
|
||||||
|
doesn't spawn until B9.
|
||||||
|
|
||||||
|
**Pace:** v0.3 was due tonight and B8 and B9 are still open, so it will close about a
|
||||||
|
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.
|
||||||
|
|||||||
Reference in New Issue
Block a user