Swarm Hosts / Guides

ARK: Survival Evolved

Staging — awaiting client validation

ARK: Survival Evolved is available for server evaluation. Player connection, public server-browser discovery, and storefront compatibility have not been validated.

This entry is for Survival Evolved, which uses a different server and client from Survival Ascended. Its dedicated-server runtime persists game files, configuration, and worlds. See Staging games for evaluation limits.

Requirements

Start with 4 CPU cores and 12 GiB memory. Maps, player counts, and mods can increase resource use substantially. Leave free disk space for the server installation, world, downloaded content, logs, and backups.

Launch and settings

  1. Choose ARK: Survival Evolved from Staging and select a suitable host.
  2. Set the server name and optional player join password; keep the offered map and network defaults for the first test.
  3. Leave Private admin credential blank on a new server to generate a unique value.
  4. Launch and inspect the logs while the game installation and world initialization finish.
  5. Stop the server before editing generated server configuration; restart to apply it.

Keep the primary game, adjacent raw-socket, and query UDP routes together. Default container ports are 7777/UDP, 7778/UDP, and 27015/UDP. Use the assigned public mappings shown by Swarm Hosts. The remote administration port is not published by this staging setup.

Connect

For later client evaluation, open the Survival Evolved client and use its server connection or favorites workflow with the displayed public game and query endpoints. A relay endpoint replaces the home host address when assigned. Test discovery and joining separately. This staging entry does not promise Epic, console, crossplay, cluster travel, or mod compatibility.

Persistent data and backups

Persistent storage is mounted at /serverdata. Backups target /serverdata/serverfiles/ShooterGame/Saved, preserving generated configuration and saves without the installed game binaries. The local restart check preserved substantive server configuration; it did not establish world-save identity or player progression. Back up before changing map, version, or content, and test restoration before reusing a valuable world.

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 records Workshop IDs and can pass the wrapper's configured mod list. It does not prove installation, compatibility, or exact-version rollback. Manually verify the installed content after restart and keep a pre-change backup. Begin client evaluation with vanilla.