Networking and security
This page covers the ports, the limits, and what the protections do and do not cover. Keys and certificates are in keys and TLS.
Endpoints and TLS
Section titled “Endpoints and TLS”The server listens on one TCP port (network.port). Players connect to
/game, staff tools to /rc. Everything runs over TLS 1.3 with WebSocket
frames.
- Without
network.tls_certandnetwork.tls_keythe server creates a self-signed certificate under<data_dir>/tlsat the first start and prints its SHA-256 fingerprint. Give the fingerprint to players: a client pins it in the server list entry. A client that does not know the fingerprint asks the player once whether to trust it (trust on first use). A later certificate change is a hard error, not a second question. - With a certificate from a public authority, clients use the system trust store and no pin is needed.
- Plain
ws://is refused unless the server runs with--devornetwork.allow_insecure_localhost = true, and then only for loopback peers. Never use this on a public server.
Keys and secrets
Section titled “Keys and secrets”See keys and TLS for the signing key, the cache secret, and key rotation.
Logs and RC chat pass through a filter that removes Authorization, Proxy-Authorization, Cookie, and Set-Cookie values and bearer tokens. Script authors who echo secrets themselves are responsible for them.
Limits
Section titled “Limits”- Per IP address: 4 game and 2 RC connections.
- A client that breaks the protocol rules 20 times in a minute is disconnected, and staff see an alert in RC chat.
- Chat 4 per second, triggers 50 per second (burst 100), public show images 30 per second, file requests 20 per second, 200 messages per second over 5 seconds.
What signing and encryption protect
Section titled “What signing and encryption protect”Client scripts are signed by the server and checked by the client before they run; the client cache is encrypted with a key that exists only in memory. This keeps a modified or copied cache and a man in the middle from running code on the client. It does not make the client trustworthy: the server is the authority for every rule, and it validates movement, flags, triggers, and actions again.
PC ID can be spoofed by a modified client. The PC ID is a hash of the machine identifier and only helps with staff rules and bans against ordinary players; never use it as the only protection for an account or a right.
Engine version 0.1.0. Built 2026-11-18.