Skip to content
SoKnight Plugins

Network setup

A typical small network: one Velocity instance, two lobbies, a few game servers. This guide sets up all six plugins on it.

Layout

Section titled “Layout”
Server Role Plugins
velocity Entry point AnchorPoint (Velocity), ForgeRelay
lobby-1, lobby-2 Lobbies AnchorPoint, ForgeRelay, SaunaCache, StreamGate, PunishSync, BerkutWatch
game-* Games AnchorPoint, ForgeRelay, SaunaCache, PunishSync, BerkutWatch

StreamGate only goes where players see chat and alerts; for most networks that is the lobbies.

Tokens

Section titled “Tokens”

Create one token per server and name it after the server. When a server is retired, revoke its token and nothing else changes.

Shared config

Section titled “Shared config”

Keep one config template per role in your deployment repository and fill in the per-server values with environment variables. Every plugin reads ${ENV_NAME} inside config.yml:

server-token: "${SOKNIGHT_TOKEN}"
cluster: main
region: "${REGION}"

Order of startup

Section titled “Order of startup”
  1. Velocity.
  2. Lobbies, so AnchorPoint has somewhere to send players.
  3. Game servers.

Updates

Section titled “Updates”

Put one lobby on the beta channel and the rest on stable. Problems show up on that lobby first, and you can pin the others while a fix ships. See Channels and pinning.