Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (client) (push) Successful in 12m27s
Foundation / checks (network) (push) Successful in 12m46s
Foundation / checks (tsan) (push) Successful in 7m59s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 25m13s
Foundation / checks (postgres) (push) Canceled after 12m48s
ADR-0095. The engineering client times presentation with the tick clock: its own marker between ticks, other markers interpolated a few ticks behind (grey when stale). Silence beyond 3 ticks and long-gap holds are stale. A lost session leaves its last view frozen and labelled stale until the reconnect's fresh baseline; nothing is predicted or sent meanwhile. evo-motion-trace --remote measures remote-marker error between two clients through the relay, with a 1.5 s outage (motion-trace-remote-smoke CTest). Prediction errors are recorded only for ticks inputs are scheduled for. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
46 lines
2.4 KiB
Markdown
46 lines
2.4 KiB
Markdown
# Engineering client over M10 sessions (M10.5c)
|
|
|
|
Decisions: ADR-0091 (grants, bundles, grant lifetime), ADR-0092 (intentions), ADR-0093
|
|
(snapshots, interest, client behaviour), ADR-0087 (dev route). **evolution-dev only.**
|
|
|
|
## Operator: issue a grant bundle
|
|
|
|
On a machine that holds the dev issuer key (never give the key to testers):
|
|
|
|
```sh
|
|
evo-session-probe grants --issuer-key issuer.key --world 100 --frame 9 --region 1 \
|
|
--account <32 hex digits, one per tester> --count 16 --lifetime 3600 --out tester.grants
|
|
```
|
|
|
|
The file is created new and owner-only; it holds 16 single-use grants, valid together for
|
|
the lifetime. A lifetime above 300 s needs the region to run with
|
|
`--m10-max-grant-lifetime` at least that long (dev only); otherwise every grant is refused.
|
|
Issue a new bundle (same account; newer serials are automatic) when one runs out or
|
|
expires. Give the tester the bundle and the public dev CA (`dev-ca.pem`).
|
|
|
|
## Tester: connect
|
|
|
|
Run `evo-client`, choose **Connect to a dev region** and fill in the endpoint (default
|
|
`void.aeternalisgames.com:7400`, UDP; reachable only from 172.10.1.0/24), the server name
|
|
on the dev certificate, `dev-ca.pem` and the bundle. Or:
|
|
|
|
```sh
|
|
evo-client --connect void.aeternalisgames.com:7400 --server-name NAME --ca dev-ca.pem \
|
|
--grants tester.grants
|
|
```
|
|
|
|
- The view follows the region's default view until you pan or zoom; then the 15 x 15
|
|
cells around the camera centre are replicated (radius 7).
|
|
- W A S D send movement intentions. They move your probe marker (amber square; others
|
|
are blue), an engineering experiment, not an organism (ADR-0094). It is predicted
|
|
locally and corrected by the server; the camera follows it until you pan or zoom.
|
|
The Session panel lists each intention as sent, admitted, rejected, simulated (final;
|
|
intentions are never durable) or unknown, plus the prediction figures. Other players'
|
|
markers are shown a few ticks in the past, interpolated (ADR-0095); grey means stale.
|
|
- If the connection is lost, the last view stays on screen, frozen and labelled STALE,
|
|
until the reconnect brings a fresh view. Nothing you press is sent meanwhile.
|
|
- Each reconnect uses the next grant. A second client with a bundle for the same account
|
|
takes the session over; the first stops (do not share bundles).
|
|
- A server on an older session protocol (v1, v2) refuses the client
|
|
(`unsupported_version`): deploy a v3 server first.
|