Staging games¶

Staging is the launch-menu category for additional game servers awaiting manual player connection checks. Staging evaluation covers local server startup, stability, and restart behavior. It does not establish public network or relay reachability, client joining, server-browser discovery, or game feature support.

Available games¶

The allocations below are Swarm Hosts starting values for evaluation, not a promise of performance at maximum player count. Leave additional capacity for the host, downloads, world generation, and backups.

Launch and evaluate¶

1. Connect a supported host using the installation guide.
2. Open the launch menu, choose a game from Staging, and read its guide.
3. Select a host with sufficient available resources and use the offered defaults for a new test world.
4. Set unique private credentials wherever the launch form requires them.
5. Launch, inspect logs, and monitor CPU, memory, and disk while the game initializes.
6. When you are ready to evaluate a client, match its version to the server and follow the game's connection steps.
7. Join, play briefly, disconnect, restart, and reconnect to confirm your test world's persistence.
8. Take and restore a test backup before trusting the server with a valuable world.

For multiple-port games, keep every required game route reachable. Use the public endpoint shown on the Swarm Server page when a relay is assigned; container defaults are not the public port numbers. See Relays and Port Forwarding. Some games also depend on publisher services, Game IDs, login tokens, or a separate query endpoint. A public-port check cannot verify those flows.

Tools and content¶

Game-specific Server Actions are unavailable for these entries. Platform lifecycle controls, settings, logs, monitoring, files, and backups remain subject to the game and your permissions. Their presence does not establish a successful restore or game-side effect.

Read each guide before changing content. A desired mod list may record IDs without installing or checking the files. Evaluate vanilla first and preserve a backup before manual changes. Exact artifact selection and rollback are available only when a guide explicitly documents them.

Report an evaluation result¶

Include the game and server version, client platform/storefront, whether you used a relay or direct route, the step that failed, and a short redacted error message. Do not include passwords, login tokens, account identifiers, or private player information. See the support checklist.