Swarm Hosts / Guides

Conan Exiles

Staging — awaiting client validation

Conan Exiles is available for server evaluation. Player connection, server-browser discovery, and mod compatibility have not been validated. Begin with a disposable world.

The dedicated-server runtime uses separate UDP game, adjacent raw-socket, and query ports. Game files, world data, and configuration remain in persistent storage. See Staging games for evaluation limits.

Requirements

Start with 4 CPU cores and 8 GiB memory for evaluation. Large worlds, players, and mods can need more. Allow enough disk space for the game download, world database, logs, mods, and backups.

Launch and settings

  1. Choose Conan Exiles from Staging and select a suitable host.
  2. Keep the offered launch defaults for the first test.
  3. Launch and inspect the game download and startup logs.
  4. Leave the initial private admin credential blank to generate a unique value for new configuration. After configuration exists, stop the server and use Files & Backups to edit ServerSettings.ini for the name, player password, or administrator credential.
  5. Restart and check the reported game version before attempting a client join.

Funcom's default dedicated-server branch changed to Enhanced, while Legacy uses a separate branch. The client and server must use the same branch and version; an older mod or world should not be treated as compatible with Enhanced. See Funcom's official server guidance.

Connect

For later client evaluation, use Conan Exiles' server browser or direct-connect flow with the player address shown on the Swarm Server page. Default container ports are 7777/UDP, 7778/UDP, and 27015/UDP. Use the displayed relay endpoint when assigned. Test public listing separately from direct joining.

Persistent data and backups

Persistent storage is mounted at /serverdata. Backups target /serverdata/serverfiles/ConanSandbox/Saved, preserving generated configuration and any world database without the installed game binaries. The local restart check preserved configuration only; it did not create a player world database. Back up before changing branch, version, mods, or world data, and test restoration before moving an existing world to this staging server.

Server Actions

Game-specific Server Actions are unavailable during staging. Use platform lifecycle, logs, settings, files, and backup controls according to your permissions.

Mods & Content

The content page tracks Workshop IDs only. It does not install, verify, resolve exact versions, or roll back mods. Apply compatible files and the server's mod list manually after a backup. Enhanced and Legacy mods are not interchangeable; evaluate vanilla before adding content.