ClientGame (N3) predicts, reconciles and interpolates, but only tests drive it. MatchView still reads a local server's Simulation. Nothing yet turns a connection into a game someone can play.
Join the two: the client program connects (address from the command line until N6 and A10 give it a menu), draws the match from ClientGame (own player from own_position(), everyone else from remote, the world from ClientGame.world), and feeds real keyboard and mouse input in as commands. Offline play should go the same way, against a local server, so there is one code path as the architecture document promises.
Acceptance
tools/godot.sh -- --connect=HOST:PORT (or similar) joins a listening server and plays a match.
A capture from tools/capture.sh of a client connected to a headless server shows the island, the client's own player and at least one other player, and is checked by eye.
Offline play runs through the same client path against a local server.
A test drives a scripted client through a whole match against a real server, lobby to results.
**Depends on:** N3, N5
`ClientGame` (N3) predicts, reconciles and interpolates, but only tests drive it. `MatchView` still reads a local server's `Simulation`. Nothing yet turns a connection into a game someone can play.
Join the two: the client program connects (address from the command line until N6 and A10 give it a menu), draws the match from `ClientGame` (own player from `own_position()`, everyone else from `remote`, the world from `ClientGame.world`), and feeds real keyboard and mouse input in as commands. Offline play should go the same way, against a local server, so there is one code path as the architecture document promises.
**Acceptance**
- `tools/godot.sh -- --connect=HOST:PORT` (or similar) joins a listening server and plays a match.
- A capture from `tools/capture.sh` of a client connected to a headless server shows the island, the client's own player and at least one other player, and is checked by eye.
- Offline play runs through the same client path against a local server.
- A test drives a scripted client through a whole match against a real server, lobby to results.
claude
added this to the v0.5 Multiplayer milestone 2026-11-12 16:30:29 +00:00
ClientSession (src/app/): a ClientGame, ClientInput (keyboard and mouse to one command a tick) and a MatchView. main.gd starts it: --connect=HOST[:PORT] joins a server, otherwise an offline match. Under tools/godot.sh, which has no window, --offline or --connect has to be asked for.
ClientMirror (src/net/): every frame it writes what the client is showing into the client's own copy of the world (other players from the recent past, its own player where it was predicted, items, the barge, the clock, the sea), so the existing views draw a networked match unchanged.
LocalServer (src/server/): offline play is the same ServerLoop and NetGame in the same process, with packets handed across in memory.
Keys: WASD, Space, Ctrl, Shift, mouse buttons, R, E, G, 1 to 6 for the boathook and slots, B for build mode (then 1 to 5 pick the piece, Tab the material).
Acceptance
--connect=HOST:PORT joins a listening server and plays: make client-check runs a server and a client as two processes over loopback UDP in real time. The client joined, followed the lobby and countdown into the drop and played 3,655 frames with no bad packets and no corrections. That run stops after 55 s; the whole match is the test below.
Capture, checked by eye: make client-captures. client_barge.png shows the client's own player in the middle of the deck, other passengers beside it and the island below. client_landed.png shows it standing on the island with another player gliding down beyond the houses. client_glide.png shows it over the forest. The first barge capture had the camera at the barge's centre with the player off to one side; MatchView.follow() now follows the player's own place on the deck.
Offline through the same path: test_offline_play_goes_through_the_same_client_against_a_local_server plays until the scripted player has landed and walked, then is eliminated and watches someone else, comparing world hashes with the local server's.
A scripted client through a whole match on a real server: test_a_scripted_client_plays_a_whole_match_on_a_real_server, over loopback UDP, lobby, countdown, drop, play, results: 3,385 server ticks, world hashes compared 11 times, no corrections.
Tested: make check passes, 448 tests, self-check and smoke. make match replays to the same hash.
Not verified, plainly
No window was opened and nobody pressed a key. The input mapping is tested as code; Input polling and mouse capture have only run headless. Frame rate and feel are unknown. That is R6 (#65).
The captures are software-rendered stills of a frozen moment.
Follow-ups: #78 (N11): build ghost, held item, shots and hits reaching the client, flooded basins on the client. No menus (N6 #37, A10 #50) or HUD (A9 #49) yet: one line of text says connecting, lobby or watching.
— tidewall-build
Done in 9a36ae8.
**What changed**
- `ClientSession` (`src/app/`): a `ClientGame`, `ClientInput` (keyboard and mouse to one command a tick) and a `MatchView`. `main.gd` starts it: `--connect=HOST[:PORT]` joins a server, otherwise an offline match. Under `tools/godot.sh`, which has no window, `--offline` or `--connect` has to be asked for.
- `ClientMirror` (`src/net/`): every frame it writes what the client is showing into the client's own copy of the world (other players from the recent past, its own player where it was predicted, items, the barge, the clock, the sea), so the existing views draw a networked match unchanged.
- `LocalServer` (`src/server/`): offline play is the same `ServerLoop` and `NetGame` in the same process, with packets handed across in memory.
- Keys: WASD, Space, Ctrl, Shift, mouse buttons, R, E, G, 1 to 6 for the boathook and slots, B for build mode (then 1 to 5 pick the piece, Tab the material).
**Acceptance**
- *`--connect=HOST:PORT` joins a listening server and plays*: `make client-check` runs a server and a client as two processes over loopback UDP in real time. The client joined, followed the lobby and countdown into the drop and played 3,655 frames with no bad packets and no corrections. That run stops after 55 s; the whole match is the test below.
- *Capture, checked by eye*: `make client-captures`. `client_barge.png` shows the client's own player in the middle of the deck, other passengers beside it and the island below. `client_landed.png` shows it standing on the island with another player gliding down beyond the houses. `client_glide.png` shows it over the forest. The first barge capture had the camera at the barge's centre with the player off to one side; `MatchView.follow()` now follows the player's own place on the deck.
- *Offline through the same path*: `test_offline_play_goes_through_the_same_client_against_a_local_server` plays until the scripted player has landed and walked, then is eliminated and watches someone else, comparing world hashes with the local server's.
- *A scripted client through a whole match on a real server*: `test_a_scripted_client_plays_a_whole_match_on_a_real_server`, over loopback UDP, lobby, countdown, drop, play, results: 3,385 server ticks, world hashes compared 11 times, no corrections.
**Tested**: `make check` passes, 448 tests, self-check and smoke. `make match` replays to the same hash.
**Not verified, plainly**
- No window was opened and nobody pressed a key. The input mapping is tested as code; `Input` polling and mouse capture have only run headless. Frame rate and feel are unknown. That is R6 (#65).
- The captures are software-rendered stills of a frozen moment.
**Follow-ups**: #78 (N11): build ghost, held item, shots and hits reaching the client, flooded basins on the client. No menus (N6 #37, A10 #50) or HUD (A9 #49) yet: one line of text says connecting, lobby or watching.
— tidewall-build
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Depends on: N3, N5
ClientGame(N3) predicts, reconciles and interpolates, but only tests drive it.MatchViewstill reads a local server'sSimulation. Nothing yet turns a connection into a game someone can play.Join the two: the client program connects (address from the command line until N6 and A10 give it a menu), draws the match from
ClientGame(own player fromown_position(), everyone else fromremote, the world fromClientGame.world), and feeds real keyboard and mouse input in as commands. Offline play should go the same way, against a local server, so there is one code path as the architecture document promises.Acceptance
tools/godot.sh -- --connect=HOST:PORT(or similar) joins a listening server and plays a match.tools/capture.shof a client connected to a headless server shows the island, the client's own player and at least one other player, and is checked by eye.Done in
9a36ae8.What changed
ClientSession(src/app/): aClientGame,ClientInput(keyboard and mouse to one command a tick) and aMatchView.main.gdstarts it:--connect=HOST[:PORT]joins a server, otherwise an offline match. Undertools/godot.sh, which has no window,--offlineor--connecthas to be asked for.ClientMirror(src/net/): every frame it writes what the client is showing into the client's own copy of the world (other players from the recent past, its own player where it was predicted, items, the barge, the clock, the sea), so the existing views draw a networked match unchanged.LocalServer(src/server/): offline play is the sameServerLoopandNetGamein the same process, with packets handed across in memory.Acceptance
--connect=HOST:PORTjoins a listening server and plays:make client-checkruns a server and a client as two processes over loopback UDP in real time. The client joined, followed the lobby and countdown into the drop and played 3,655 frames with no bad packets and no corrections. That run stops after 55 s; the whole match is the test below.make client-captures.client_barge.pngshows the client's own player in the middle of the deck, other passengers beside it and the island below.client_landed.pngshows it standing on the island with another player gliding down beyond the houses.client_glide.pngshows it over the forest. The first barge capture had the camera at the barge's centre with the player off to one side;MatchView.follow()now follows the player's own place on the deck.test_offline_play_goes_through_the_same_client_against_a_local_serverplays until the scripted player has landed and walked, then is eliminated and watches someone else, comparing world hashes with the local server's.test_a_scripted_client_plays_a_whole_match_on_a_real_server, over loopback UDP, lobby, countdown, drop, play, results: 3,385 server ticks, world hashes compared 11 times, no corrections.Tested:
make checkpasses, 448 tests, self-check and smoke.make matchreplays to the same hash.Not verified, plainly
Inputpolling and mouse capture have only run headless. Frame rate and feel are unknown. That is R6 (#65).Follow-ups: #78 (N11): build ghost, held item, shots and hits reaching the client, flooded basins on the client. No menus (N6 #37, A10 #50) or HUD (A9 #49) yet: one line of text says connecting, lobby or watching.
— tidewall-build