Server Actions
Manage your ARK: Survival Ascended server
Available tools depend on the game, server status, and your permissions. The game guide explains any setup needed for Server Actions.
Server status
Read the configured session, map, runtime build, and connected-player count.
List players
List connected players while keeping their EOS account identifiers private.
Broadcast message
Send a server-authored chat message to connected players.
Save world
Flush the active ARKSA world state to persistent storage.
Respawn wild dinos
Remove every wild dinosaur so ARK can repopulate stuck or unbalanced spawns. Tamed creatures are preserved.
Mods & Content status
Mods and custom content
ARK: Survival Ascended resolves the ordered CurseForge project IDs at runtime. Swarm Hosts does not claim an exact installed file version without runtime observation.
The default map is TheIslandWP. When Server Tools → Mods & Content is available, ARK profiles store an ordered list of positive CurseForge project IDs. ARK resolves those projects during startup, so the profile controls selection and order rather than promising an exact downloaded file version.
Saved mod sets belong privately to the account that creates them. Choose Saved mod set from your account when launching another ARK server or in an existing server's Mods & Content page. Reuse the same set across your Swarm Hosts. Deleting the original server or Swarm Host does not delete the saved set, and saving a new revision does not automatically update other servers.
For an existing world:
- create and verify a backup
- add a small group of project IDs
- keep their load order intentional
- apply the profile; and
- verify startup and join once with a real client.
Know before launch
Before you launch
- Host on Windows 10/11 or Linux with Docker Desktop in Linux-container mode on Windows, or Docker Engine or rootful Podman on Linux.
- Managed shared relay when the game, host, and current relay path support it.
- Still starting: wait for download verification, runtime initialization, and the successful-start log line. A running container alone is not ready.
- Missing from the browser: select Unofficial servers, enable player servers, clear filters, verify the session name, and refresh after startup.
- Timeout after selecting the server: verify the displayed relay or direct UDP path. Private RCON success does not prove the UDP player path.
- Old CPU warning: move the Swarm Server to a newer x86-64 host.
- Memory pressure: allocate at least 16 GiB and reduce mod load before assuming a network problem.
Windows 10/11 + Linux
Ready to host ARK: Survival Ascended?
Connect the Windows or Linux computer you already own, then follow the game-specific launch path.