news Version 0.8.3.0 Released (23rd May 2026) - Focused community bug-fix release — every newly reported user issue from t…
How to Set Up a Cluster Server | ARK Ascended Server Manager v0.8.3

Setting Up a Cluster Server

Link multiple ARK servers so players can transfer (ASM v0.8.3)

A cluster is two or more ARK: Survival Ascended servers that share a folder on disk — players can use the in-game Travel to Another ARK obelisk option to move between maps with their character, dinos, and items intact. ASM v0.8.3 sets this up via the per-server Cluster Settings sub-tab: enable, point at a shared folder, set the same ID on every member.

Prerequisite: you need 2+ servers on the dashboard before clustering makes sense. If you haven't yet, follow Installing Your First Server twice (once per map) or Import an Existing Server for any that you already have.

Confirm You Have 2+ Servers on the Dashboard

Open the Dashboard. You should see at least two server tabs in the top tab strip. The screenshot below shows a typical two-map cluster setup: an Island server and a Scorched Earth server.

ASM dashboard with two servers (Island and Scorched) ready to be clustered

Pick a Shared Cluster Directory

Before you touch ASM, decide on one folder that all cluster members will write transfer data to. This folder must be:

Reachable from every server. If all servers run on one machine, any local path works. If servers are on different machines, use a network share (SMB, NFS) or a synced folder — both servers need read+write to the same files.
Empty when you start. ARK populates it on first transfer; pre-existing files from another cluster will mix in and cause confusion.
Outside your individual server folders. A common pattern is F:\ARK Clusters\MyCluster\ sitting alongside (not inside) each F:\Ark Servers\<name>\ folder.

Create the folder now in Windows Explorer (or on your NAS). ASM doesn't auto-create it.

Open Cluster Settings on the First Server

Click your first server's tab next to Dashboard, then click the Cluster Settings sub-tab in the sub-tab strip. The v0.8.3 Cluster Settings page has three main areas: the Cluster Configuration card (with an Enabled toggle), Quick Actions on the right, and Cross-Chat Management further down.

The Cluster Settings sub-tab showing Cluster Configuration with Directory Path and Cluster ID fields

Set Cluster Directory + Cluster ID

In the Cluster Configuration card:

1 Directory Path — click the browse button (or type the path) and pick the shared folder you created in Step 2. Use the same path on every cluster member — if they're on different machines, the path string can differ as long as each one points at the same underlying network share.
2 Cluster ID — a short string that identifies this cluster. Pick something unique to you, like my-island-cluster-2026. This value must be identical on every server in the cluster. If two servers have different IDs, they won't see each other's transfers even if pointing at the same directory.

Pick a non-obvious Cluster ID. Don't use defaults like "cluster" or "ark" — if another nearby server has the same ID and shared folder access, your players' data can leak between clusters. Treat it like a password.

Enable Clustering + Save

At the top of the Cluster Configuration card, flip the Disabled toggle to Enabled (the toggle slides right and turns green). Then click Confirm Saved at the top-right of the server tab (or the Save button at the bottom of the Cluster Configuration section, depending on layout).

ASM writes the cluster settings into the server's launch arguments — specifically -clusterid=<your-id> and -ClusterDirOverride=<your-path> — which take effect on the next server start.

Repeat for Every Other Cluster Member

Open each remaining server in the cluster and repeat steps 3–5 with the identical Cluster Directory and identical Cluster ID. The only field that differs per-server is whatever's already configured (port, name, map).

v0.8.4 (planned) will add a copy cluster settings between servers action so you only configure once and apply to siblings. For now, do it manually per server — 30 seconds each.

(Optional) Configure Transfer Restrictions

By default, players can transfer anything: themselves, dinos, items, tribute (artifacts/element). You can restrict any of these per-server via the Server Settings → Rules tab. Common choices and their Game.ini flags:

SettingWhat it blocksCommon use
noTributeDownloadsTribute (artifacts, element) downloads from other serversPvE clusters — prevents farming exotic resources on easy maps and importing.
PreventDownloadDinosDino transfers INMap-locked tame economies — each server has its own dino population.
PreventDownloadItemsItem transfers IN"Fresh start" servers where players keep their character but lose gear.
PreventDownloadSurvivorsCharacter transfers INClosed clusters — new players must start a character per server.
PreventUploadDinos / Items / SurvivorsThe OUT direction of each.One-way clusters — e.g. trial server feeds into main, no return.
CrossARKAllowForeignDinoDownloadsInverse: allows non-native creature downloads (defaults to disallow).If you want Aberration creatures on The Island map, etc.

These settings are per-server, not per-cluster. You can have asymmetric rules (e.g. block uploads on a PvP map but allow downloads to it).

Restart Each Server

Clustering takes effect on next launch — the cluster args are added to the ARK process command line at startup. Stop, then Start each server (or Restart if it was running). After the restart, the in-game obelisk transfer menu on each server will show the other cluster members in its destination list.

To verify it worked, join one server in-game and walk up to an obelisk (red, green, or blue). Choose Travel to Another ARK. If clustering is wired up, the other cluster members appear in the destination list. Pick one, accept the upload of your character/items/dinos, then download on the other side.

Troubleshooting

! Obelisk destination list is empty — check that the Cluster ID is identical on every server (case-sensitive). One typo and the servers can't see each other. Also confirm each server can read+write to the shared directory — permissions issues are silent in-game.
! Transfer succeeds but character/dinos disappear — this is almost always a stale or corrupted file in the cluster directory. Stop all cluster members, back up the cluster folder, then delete its contents and let ARK rebuild on the next transfer. Players don't lose anything they had pre-cluster.
! "Transfer in progress" hangs forever — the receiving server isn't running or can't reach the cluster folder. Verify the destination server's status from the ASM dashboard before initiating transfers.
! Cross-server chat doesn't work after enabling cluster — clustering and cross-server chat are separate features. Set up chat separately via Setting Up Cross-Server Chat.

Cluster Online!

Your servers now share a transfer namespace. Players can move between maps without losing their progress. Combine with Cross-Server Chat for a true multi-map experience.

Related Guides

Cross-Server Chat

Bridge chat between cluster members

View Guide
Discord Bot

Notify on transfers

View Guide
Automated Backups

Back up the cluster folder too

View Guide