How to Set Up an ARK Server Cluster

MANAfuel Team

6 min readMay 27, 2026Updated May 2026

ARK Survival Evolved server cluster setup on MANAfuel

Link multiple ARK: Survival Evolved servers into a cluster so players can transfer characters, dinos, and items between maps on MANAfuel.

Plan Your Cluster
An ARK cluster links two or more servers so players can transfer characters, dinos, and items between maps. Each map (The Island, Ragnarok, Aberration, etc.) runs as a separate server with its own resources. Plan which maps you want to offer — most communities start with two maps and expand over time. Each server in the cluster needs its own MANAfuel deployment.
Deploy Multiple ARK Servers
Deploy one ARK: Survival Evolved server per map from the MANAfuel dashboard. Each server needs at least 8 GB RAM (Gamer plan recommended). Name each server clearly by map — "MyCluster - The Island" and "MyCluster - Ragnarok" — so players know which map they are joining. Note the deployment IDs for each server.
Configure the Cluster ID
Every server in a cluster must share the same cluster ID. Open the server settings for each deployment and set the same clusterid value — use a unique string like your community name. This tells ARK that these servers are linked and should share transfer data. The cluster ID goes in the GameUserSettings.ini configuration accessible through the File Manager.
Enable Cross-ARK Transfers
In each server's GameUserSettings.ini (via the File Manager), verify these settings are enabled: bPreventDownloadSurvivors=False, bPreventDownloadItems=False, bPreventDownloadDinos=False, bPreventUploadSurvivors=False, bPreventUploadItems=False, bPreventUploadDinos=False. These allow players to upload and download their characters, items, and tamed dinos at any Obelisk or supply drop.
Set Transfer Cooldowns
Prevent abuse with transfer cooldowns. Configure TributeItemExpirationSeconds (how long uploaded items persist — default 86400 seconds or 24 hours), TributeDinoExpirationSeconds (same for dinos), and TributeCharacterExpirationSeconds (same for characters). Most communities use 24 to 48 hours. These settings prevent item duplication exploits and encourage players to commit to a map before transferring.
Test the Cluster
Join each server and walk to an Obelisk. Open the Obelisk terminal and verify you see the Upload and Download tabs for characters, items, and dinos. Upload a character on one server, disconnect, join the other server, and download it at an Obelisk. Bob monitors both servers and alerts you if the cluster connection fails or if transfer data becomes corrupted.

FAQ

Frequently asked questions

Can I add more maps to an existing cluster later?

Yes. Deploy a new ARK server, set the same cluster ID in its configuration, enable cross-ARK transfers, and restart. The new map joins the cluster immediately. Existing players can transfer to the new map from any Obelisk.

Do all servers in the cluster need to be on the same plan?

No. Each server runs independently. A busy map like Ragnarok might need a Creator plan (12 GB) while a less populated map like Aberration runs fine on a Gamer plan (8 GB). Allocate resources based on expected player traffic per map.

What happens if one server in the cluster goes down?

Other servers in the cluster continue running normally. Players on the down server are disconnected but their characters and progress are safe. Transfer data persists for the configured expiration period. When the server comes back online, everything resumes.

Troubleshooting