Skip to content
Anomaly

Auth Model, Offline Mode, and @anomaly IDs

Intended scope

Section titled “Intended scope”
  • Why the server is offline-mode once Anomaly.Server loads — no Steam tickets, no NorthWood auth.
  • Handshake walkthrough — client-presented ECDSA public key, server challenge, X25519 key exchange, AES-GCM session (brief summary; full wire-level detail in Reference → Protocol).
  • Using @anomaly IDs in remote-admin config alongside or instead of @steam IDs.
  • How to read a player’s @anomaly ID from server logs or admin tools.
  • Rejection reasons the server emits and how to map them to client-side causes.

Sources

Section titled “Sources”
  • Anomaly.Shared\Auth\ — ECDSA / X25519 / AES-GCM primitives and handshake message layout.
  • Anomaly.Server\ — auth handler and role integration.