Files
aevolution/docs/networking/M10_CLIENT_SESSIONS.md
T
aevolution-gitops-bot ce1b5b8140
Foundation / checks (checks) (push) Successful in 32m12s
Foundation / checks (client) (push) Failing after 10m0s
Foundation / checks (deploy) (push) Successful in 3m19s
Foundation / checks (ecs) (push) Successful in 1m56s
Foundation / checks (network) (push) Successful in 13m21s
Foundation / checks (postgres) (push) Successful in 44m18s
Foundation / checks (tsan) (push) Successful in 7m58s
Foundation / postgres-tools (push) Skipped
Foundation / image (push) Skipped
Foundation / server-image (push) Skipped
Extend DEV M10 grant lifetime to four hours
2026-10-07 13:41:36 -04:00

3.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 14400 --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. 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-v3) refuses the client (unsupported_version): deploy a v4 server first.

Two regions (M10.8, ADR-0096, EXPERIMENT)

Regions with adjacent areas hand a probe over when it walks across the edge. The client follows on its own: the view stays on screen, no grant is used, and the Session panel counts the crossings. Each region needs:

  • --m10-area X0,Y0,X1,Y1 (its cells);
  • --m10-handoff-key issuer.key (a pair from evo-session-probe keys);
  • one --m10-neighbour REGION=X0,Y0,X1,Y1=HOST:PORT=SERVER_NAME=neighbour.pub per neighbour.

All of them need schema v13. Issue bundles with one --region per region:

evo-session-probe grants --issuer-key issuer.key --world 100 --frame 9 --region 1 --region 2   --account <hex> --count 8 --lifetime 3600 --out tester.grants

A login at a region that does not own the probe is redirected to the one that does.