#72: The packet ship, the lifeline mortar and the gull-kite

Eric chose option B on #72. The drop is now the GDD's launch:

- A packet ship sails a seeded straight line past the island, offshore,
  as close in as it can while keeping 45 m of open water from any land
  (eight-way probes; up to 32 headings, then the four world sides).
- Jump fires the lifeline mortar along the look heading. How high the
  player aims sets the charge (-10 to 45 degrees: 16 to 110 m/s over
  the ground; every shot climbs at 75 m/s). The climb can't be steered
  and the kite can't open until the arc tops out. Riders still aboard at
  the end are fired towards the middle of the island.
- Drop.reach() mirrors the fall for both ways down (kite at the top, or
  a fall with the kite opening by itself); bots, the soak and autoplay
  clients and the tutorial pilot aim with Drop.aim_charge().
- Bots fire at their landing spot once abeam of it, when in easy reach
  at their own staggered moment, or just before the route ends, and open
  the kite early only when the spot is beyond the rest of a fall.
- Art: VesselModels.ship() (two-masted packet, tanned square sails, a
  salt-white boot-top, a bowsprit and the mortar on its bed, mirrored to
  face the island), the figure's gull-kite (figure.py), and a lifeline
  cord from the muzzle to each player still climbing.
- Renamed barge to ship and wing-sail to gull-kite throughout code,
  tests, captures, docs and the tutorial text. make match now defaults to
  seed 2, where the scripted player still harvests and builds.

Closes #72

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-15 12:49:21 -05:00
co-authored by Claude Opus 5.5
parent 4357861bd4
commit aa797580a7
69 changed files with 1753 additions and 847 deletions
+7 -7
View File
@@ -172,7 +172,7 @@ sources tracked per second). A source is an IPv4 address, or an IPv6 address's w
**Lobby, backfill and late arrivals.** People who connect during the lobby or the
countdown take places (`Match.join()`); bots are only added when the match starts,
into whatever places are still empty, so people joining and leaving in the lobby
never displace or strand a bot. Someone who connects after the barge leaves, or
never displace or strand a bot. Someone who connects after the ship sails, or
during results, becomes a watcher (`Match.watch()`): they spectate a living player
(the winner during results) through the same snapshots an eliminated player gets,
and take a place ahead of any bots when the next lobby opens. The server still turns
@@ -360,7 +360,7 @@ trips, 41 of 41 shots hit; with the lag ignored, 0 of 41. At 500 ms, past the ca
`ClientGame` (`src/net/`) is a client's side of a match. It works on packets, so it
runs the same over a `NetClient` or a test's simulated link. From the seed in the
MATCH notice it generates the island itself (a `Simulation` it never steps) and plans
the same barge route, so it can run the server's movement code on the server's ground.
the same ship route, so it can run the server's movement code on the server's ground.
**The command clock.** A command must reach the server before the tick it names, so
the client's tick runs ahead of the server's by the trip there plus a margin. Nobody
@@ -482,7 +482,7 @@ weights from the island's elevation bands, with rock on steep ground.
`MatchView` (`src/client/`) is the client's picture of one match: sky, sun, terrain,
sea, points of interest, props, built pieces and `EntityView`, which draws players, the
barge, items and chests. All of it reads one `Simulation` and never writes to it, and a
ship, items and chests. All of it reads one `Simulation` and never writes to it, and a
new match gets a new view. The camera sits on a player's shoulder through `CameraRig`.
`EffectsView` (`src/client/effects/`, A7) draws the match's visual effects from the
server's FX records and from changes it sees in the world (pieces gone, players in the
@@ -490,7 +490,7 @@ water, surges). Its particles are simulated on the CPU in packed arrays and draw
two MultiMeshes (blended and added) of camera-facing quads, sized per instance by a
small shader, with tracers as a third; everything is allocated once at the preset's
budget, so a big fight costs a fixed three draw calls and never adds nodes or grows buffers.
The figure (`FigureRig`), items (`ItemModels`) and barge and chests (`VesselModels`) are
The figure (`FigureRig`), items (`ItemModels`) and ship and chests (`VesselModels`) are
the generated art described in assets/PROVENANCE.md; `test_world_art` fails on any
primitive stand-in mesh.
@@ -499,7 +499,7 @@ In play, the simulation it reads is the client's own copy of the world: the
`ClientWorld` keeps its pieces, props, chests and tide in line with the server, and
`ClientMirror` (`src/net/`) writes the rest of the picture into it every frame: each
entity the server has told this client about, where it is being drawn now (everyone
else from the recent past, the client's own player where it was predicted), the barge,
else from the recent past, the client's own player where it was predicted), the ship,
the clock and the sea level. So the same views draw a networked match, a local
server's simulation in a test, or a replay in a capture, and there is one set of
drawing code. Captures and tests still point a `MatchView` straight at a server's
@@ -559,7 +559,7 @@ budget:
The max includes one long tick per match: unthrottled, the 15 s results screen passes
in a fraction of a second, so the main thread waits for the worker still building the
next island. At the real 30 Hz the worker finishes long before the lobby opens.
- **Client:** the match `make match` saved, rendered at the whole island, the barge (24
- **Client:** the match `make match` saved, rendered at the whole island, the ship (24
figures together, the worst case for draw calls), landed, a build and the final
players, and a crowded pine forest. Each capture reports its frame's draw calls,
primitives, objects, nodes and memory (`tools/capture.gd`'s `render` field).
@@ -631,7 +631,7 @@ model and tier. The hotbar shows the icons.
## Player figure (A2)
`tools/models/figure.py` builds the islander in headless Blender as twelve rigid
parts (pelvis, torso, head, upper arms, forearms, thighs, shins and the wing-sail),
parts (pelvis, torso, head, upper arms, forearms, thighs, shins and the gull-kite),
each an OBJ whose origin is the joint it turns about, plus `figure.json` with the
joints and hand points (`make art` rebuilds these and the items). OBJ has no
skeleton, so the figure is jointed rather than skinned.