Files
aevolution/docs/networking/M10_CLIENT_SESSIONS.md
T
dingoandClaude Opus 5.5 96237ca10a
Foundation / checks (checks) (push) Successful in 32m33s
Foundation / checks (client) (push) Successful in 12m28s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (network) (push) Successful in 12m8s
Foundation / checks (postgres) (push) Successful in 40m38s
Foundation / checks (tsan) (push) Successful in 8m4s
Foundation / postgres-tools (push) Successful in 1m36s
Foundation / image (push) Successful in 2m33s
Foundation / server-image (push) Successful in 3m53s
Wire M10.6b probe markers through sessions, evo-server, probe and client
EXPERIMENT (ADR-0094). RegionSessions owns the probe markers: admitted
intentions schedule them, each poll advances them to the simulated tick, and
snapshots carry them. evo-server sets the motion area from the region's
habitat sites; the probe prints its own marker.

The engineering client predicts its marker with the adaptive input lead,
rebases on each snapshot, resends a lost or refused intention, smooths
corrections, draws markers and follows its own with camera and interest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-06 16:07:34 -04:00

2.1 KiB

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):

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:

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.
  • 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.