The islander is built in headless Blender (tools/models/figure.py,
`make figure`, `make art`) as twelve rigid parts with their origins at
their joints: an oilskin coat, a sou'wester, sea boots, a bedding roll
and the canvas wing-sail. Debian's Blender can't write glTF, so the
figure is jointed rather than skinned.
FigureRig hangs the parts on pivots, paints them from Palette with the
coat in the player's own oilskin, and plays FigurePoses' hand-written
key poses through one AnimationTree: idle, walk and run by speed,
crouch and creep, air, skydive, glide, swim and aboard; long, short and
carried holds; reload and use layers; fire, boathook swing, keg throw
and building as one-shots; and a flinch when health drops. The chest
takes a third of the pitch and the held item all of it.
Figures animate from replicated state only: positions, look, health,
the held item and the FLAG_ bits (reloading and using now reach
mirrored players), with actions from FX. Every boathook swing is now a
sim "swing" event, sent as a SHOT with no item, so misses are seen and
heard; the new FX kind PLACE shows pieces placed. Protocol version 4.
Tests: test_figure_rig (15), plus swing and PLACE cases in test_harvest
and test_net_fx. make check passes (604 tests); make client-check
passes. Captures: figure_states, figure_actions, figure_close
(make figure-captures), client_glide and client_landed.
Closes#42
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- Build ghost: ClientSession shows a BuildGhost in build mode while the
client plays, asking Building.check() of its own world and predicted
player with the mouse's newest look, so it agrees with the server.
- Flooded basins: ClientMirror.follow_flood() spreads the client's flood
as the server's tide tick does, from the tide and the pieces it has.
WaterView passes a mask of flooded cells (Flood.pours says when it
changed) to the sea shader, which leaves dry cells undrawn.
- Shots, impacts and swings: a new FX message (NetFx) goes unreliably on
the state channel next to each snapshot, with what happened within
NET_FX_RADIUS_METRES of what the client watches or involving that
player. ClientGame keeps them in `fx` for views and sound. They change
no state, so a lost one is a missed flash; sending them reliably would
add to the traffic a bad link can least afford (N8). The fuzzer covers
the new parser.
- Captures: client_build and client_build_refused show the ghost in its
allowed and refused tints; client_basin rings shore ground with
breakwaters and plays until the tide stands over it, and the server,
the client's flood and the drawn sea all keep the basin dry.
- Tests: NetFx round trips, limits and malformed input; a landed player's
shots and impacts reach a client, each matching a server event; the
client keeps a ringed basin dry through the first rise, floods it with
no ring, catches up after a long frame; the water mask follows pours.
The held item is still not drawn; that needs the models (A4, #44).
Closes#78
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>