TRACKMANIARL / SYSTEM GUIDE / 08
Choose a local or remote actor
Both deployments use the same authenticated actor-learner protocol and durability guarantees.
01 Local deployment
02 Remote deployment
One Windows host
Launcher starts separate actor and
learner processes using spawn.
Local gRPC
The actor connects over loopback.
Rollouts still pass authentication.
Separate game host
The remote actor drives Trackmania and
retains a durable rollout spool.
SSH or VPN tunnel
Authenticated encryption forwards the
learner loopback endpoint.
Shared learner runtime
Authenticate identity → commit WAL → apply replay → update learner → publish policy /
checkpoint
IDENTITY
Both sides must agree on the run fingerprint,
map and contracts. The bearer token authorizes
requests.
ENCRYPTION
The bearer token does not encrypt traffic. Keep
learner gRPC on loopback and tunnel remote
access.
Download editable diagram