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>
Gamepad: PadInput reads pad events in one fixed layout (sticks move and
look, triggers aim and fire, bumpers step slots and build pieces, Start
pauses), fed through ClientInput alongside the keys and mouse. Menus take
South to choose and East or Start to go back. The tutorial names pad
buttons once the pad is used.
Aim assist (option, on by default, pad only): friction across an
opponent in plain sight near the look, and a pull of at most 9 deg/s
while aiming. Client look only; never through cover.
Accessibility (new Access tab): colour-vision sets for the signal colours
(red-green, blue-yellow), checked by simulated colour vision in
test_palette; interface size 90-130%, with the HUD hotbar refitting at the
larger sizes; captions for key sounds with direction; reduce motion
(calmer aim zoom and hurt flash).
Tests for the pad, aim assist, captions, palettes, settings, the menus
driven from a pad, and a pad playing through a real offline session.
make access-captures renders the new screens and options.
Closes#53
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Two-player teams, enforced by the simulation:
- Match puts every player on a team (SimEntity.team); Weapons.damage_player
refuses damage between teammates from every weapon, the boathook and blasts.
- A player whose health runs out with a teammate standing goes down instead of
out: 60 health to bleed (one point every half second), crawling at 1 m/s, no
firing, building, looting or items. Hits still take it; drowning too.
- A standing teammate within 2 m holding interact for 6 s revives them with 30
health. Letting go or moving away starts it over.
- Downed players are out when their health runs out again or when no teammate
is left standing, credited to whoever downed them. A team falls together and
shares its place; the tie-break puts standing ahead of downed.
- Downs and revives go through Match events and the kill feed ("X knocked Y
down"); the HUD says what to do while down.
Wire: FLAG_DOWNED in the player record and the own block (flags now u16),
so prediction crawls too. Protocol version 5.
Bots: never target a teammate, land with their teammate, regroup when they
stray past 30 m, crawl toward a standing teammate when down, go to revive a
downed teammate within 60 m when not in a fight, and turn from a downed target
to its standing teammate when it's in view.
Options: --team-size=2 on the server, --duos offline, and Solo/Duos under
Crew in the Practice menu. The figure has a downed crawl pose.
Tests: test_duos (downing, crawl, revive, interrupted revive, bleed-out,
finishing, team out, falling together, no friendly damage including kegs,
drowning while down, hash, match placement and tie-break), bots as teammates,
the downed flag on the wire, the feed, server and menu options. make
duo-matches plays 10 bot duos matches.
Closes#30
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The HUD (src/client/hud) is drawn in the paper-and-ink motifs of the style
guide:
- top centre: the tide post, the most prominent thing on screen. It is a
notched post with the sea filled in, the next level's rust notch and the
player's own height. Beside it are the phase, the time to the rise, both
levels and how far the player stands above or below the next line;
- top right: how many are standing, and the kill feed in words;
- bottom left: health and armour, each with a number, a word, quarter notches
and its own hatching. Low health adds LOW;
- bottom centre: the boathook and five slots, with names on two lines, rounds
and reserve or counts, and tier pips;
- bottom right: materials, and the build line ("NOT ENOUGH" when short).
Snapshots only carry nearby players, so the server now sends FEED (NetFeed,
reliable) when anyone is placed and at each phase change. It carries who is
standing, the match size and the newest 16 entries with names. Bots get crew
names (CrewNames). HudState works out what to show from the client, or from a
server's match for captures and tests, so the drawing never reaches into
either.
The project now stretches canvas items from a 1280x720 base, so the HUD scales
to any screen. make hud-captures renders it at 1280x720 and 3840x2160. The
parser fuzzer covers FEED.
Closes#49
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>
The soak's drops under loss came from stalls: the server's island (#79) and
each client process making islands on its main thread fed ENet second-long
round-trip samples, its retransmission timer grew, and two losses of one
reliable message in the busy drop that followed reached the 15 s timeout.
- ClientGame.build_in_background makes a new match's island on a
WorkerThreadPool task and holds the packets that arrive meanwhile, then
takes them in order. The networked client and the soak's clients use it;
the soak's own one-island-a-frame holding is gone.
- NetServer.close(grace_msec) sends the shutdown notice reliably and
services the socket while clients acknowledge it. The headless server
waits up to 2 s. A notice sent once was lost under 2% loss, and that
client timed out instead of hearing the server stop.
- Tests: background island holding and ordering, freeing mid-build, a
graceful shutdown reaching four clients behind 50% loss (it fails with
the old one-shot notice), and the scripted UDP match and client capture
wait for the client's island the way a real 20 s lobby would.
The soak at 2% loss and +/-20 ms now keeps all 24 clients for both matches,
with 0 of 3,758 world hashes differing and every client told of the stop.
It still fails on client memory growth between matches in two of three
processes (17 and 20 MB), which is not yet explained, so #39 stays open.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The client program now turns a connection into a match someone can play.
- ClientSession: a ClientGame, the keyboard and mouse as commands
(ClientInput), and a MatchView of the client's own copy of the world.
- ClientMirror writes what the client is showing into that world every
frame: other players from the recent past, its own player where it was
predicted, items, the barge, the clock and the sea. The existing views
draw it unchanged.
- LocalServer: offline play is the same ServerLoop and NetGame in the same
process, with packets handed across in memory, so there is one path.
- main.gd: --connect=HOST[:PORT] joins a server, otherwise an offline
match; --autoplay and --client-seconds=N for scripts and checks.
- The camera aboard the barge follows the player's own place on the deck.
Tests drive a scripted client through a whole match on a real server over
loopback UDP, lobby to results, and through an offline match. `make
client-check` does it with two real processes, and `make client-captures`
renders what the client sees.
Closes#77
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>