Swarm Hosts / Guides

Killing Floor 2

Staging — awaiting client validation

Local server startup, five-minute stability, and configuration persistence on restart are the evaluation scope. Public networking, relay access, player joining, server-browser discovery, and gameplay remain unverified.

Swarm Hosts offers the native Linux runtime for evaluation. Read Staging games before inviting players.

Requirements

Start with 4 CPU cores and 8 GiB memory on a Linux host with fast storage and enough free disk for server downloads, generated worlds, and backups. These are evaluation allocations, not a maximum-player performance promise. Downloads and initial world setup may take several minutes.

Launch and settings

  1. Choose Killing Floor 2 from Staging and select a suitable host.
  2. Read the settings below and use a new disposable test deployment.
  3. Launch, inspect startup logs, and monitor resources before attempting a client connection.

The default evaluation map is KF-BioticsLab in Survival mode with six player slots. Web administration is not published.

The internal routes are 7777/UDP for players, 20560/UDP for Steam, and 27015/UDP for server queries. Share the assigned public player endpoint shown on the server page. Container ports can differ from public relay ports. See Relays and Port Forwarding. Private administration services are not player routes.

Connect

Use the PC server browser with the matching game version. Check both the player route and query route; a local query response does not establish public listing. See the publisher guidance. Check the reported server version before selecting a client; the template does not promise that a later download has the same build as the staging test.

Persistent data and backups

The persistent storage root is /serverdata. Keep generated configuration and saves together when moving the deployment. The restart check covers initial server artifacts; no player progression or restored backup has been certified. Take an independent backup and restore it into a disposable deployment before trusting a valuable world. See the user guide.

Server Actions

Game-specific Server Actions are unavailable during staging. Platform start, stop, restart, settings, files, logs, monitoring, and backups remain subject to the game and your permissions. Their presence does not certify a game-side administration effect or successful backup restoration.

Mods & Content

A desired Workshop-ID list can record content for later manual work; it does not install, validate, or roll back artifacts. Custom maps and Workshop content need separate manual evaluation. Preserve a backup before modifying server files and repeat connection and persistence checks after a change.