ARK: Survival Ascended (ASA) Dedicated Server Setup and DLC Map Cluster Configuration

ARK: Survival Ascended (ASA) is rebuilt on Unreal Engine 5. When setting up a dedicated server, check ASA's startup arguments, cross-platform options, and CurseForge mod requirements separately; commands from its predecessor, ASE, cannot simply be copied across. This article covers installation and map cluster configuration. Compare the arguments with the server configuration documentation on the official ARK community wiki.

1. Hardware and resource planning

Estimate server capacity from the map, mods, concurrent players, and actual resource use. The game client's Lumen, Nanite, and GPU requirements are not direct purchasing criteria for a dedicated server. The following checklist supports capacity planning; validate the resources needed with your target combination of maps and mods:

2. Download and install the server with SteamCMD

You do not need to purchase the game to download the ASA dedicated server anonymously through SteamCMD (AppID 2430930):

This Windows example fixes the installation directory at C:\ASA_Server, matching the startup script below:

steamcmd +force_install_dir C:\ASA_Server +login anonymous +app_update 2430930 validate +quit

After the download, the main executable is located at: ShooterGame/Binaries/Win64/ArkAscendedServer.exe

3. Network ports and firewall planning

Start by configuring inbound rules for the game port actually listening. Manual port forwarding is needed only when accessing the server through the router's public internet entry point; on the same LAN, verify the local connection first:

ASA and ASE have different query and startup options. Do not treat ASE's QueryPort=27015 as a universal fix for ASA server listing problems. Give each instance its own game port and check server logs and actual listening state.

4. Startup arguments and DLC maps

Create a start_server.bat startup script. ASA supports switching between several official DLC maps:

@echo off
set "SERVER_DIR=C:\ASA_Server\ShooterGame\Binaries\Win64"
cd /d "%SERVER_DIR%"

start "" ArkAscendedServer.exe TheIsland_WP?listen?SessionName="LanGame ASA Server"?ServerPassword="your_pwd"?ServerAdminPassword="admin_pwd" -port=7777 -WinLiveMaxPlayers=20 -ServerPlatform=ALL -servergamelog -clusterid=LanGameCluster01 -ClusterDirOverride="C:\ASA_Cluster"

Key arguments explained:

1. Map names:
   • The Island: TheIsland_WP
   • Scorched Earth: ScorchedEarth_WP
   • Aberration: Aberration_WP
2. Cross-platform support: ASA uses -ServerPlatform to select allowed platforms. ALL allows all supported platforms; do not substitute ASE's -crossplay. Check client versions and the platform support of your mods as well.
3. CurseForge mods: -mods=<ModID1>,<ModID2>. ASA automatically downloads and activates CurseForge mods over the network on startup.
4. Cross-map server clusters: Use -ClusterId=<name> and -ClusterDirOverride=<shared directory> so instances on different ports or maps share Ark transfer data, allowing players and dinosaurs to transfer between maps.

Replace the example's server and administrator passwords before starting. Keep ServerAdminPassword as the last argument joined with ?; use -port=7777 for the game port instead of ASE's ?Port= syntax. See Dedicated server setup and Server configuration for installation and argument syntax. You can initially test without mods, then add confirmed CurseForge Mod IDs as needed.

5. Choose an approach: manual configuration or LanGame Server Manager (LGSM)

Manual ASA maintenance requires monitoring resource use, handling startup arguments, and coordinating cluster directories across maps.

LanGame's open-source dedicated server management tool can handle routine operations:

• Tool overview and client: LanGame Server Manager (LGSM) product page
• Open-source repository: GitHub - SZSLGJCOM/LanGame-Server-Manager

LGSM provides these ASA enhancements:

1. One-click map and cluster switching: Select TheIsland, ScorchedEarth, or Aberration visually and generate a standardized startup pipeline.
2. Visual CurseForge mod search: Search mod names in the interface and add them with one click, automatically maintaining and updating the -mods list.
3. Multiplier and sandbox templates: Change taming speed (TamingSpeedMultiplier), harvesting, and experience bonuses in a form and write them back to GameUserSettings.ini automatically.
4. Memory overload alerts and automatic restarts: Detects UE5 process failures and restarts smoothly after executing the save command (SaveWorld).

6. Common issues during long-term operations

1. Server crashes during loading

• Investigate: Check server logs and operating system events first to distinguish insufficient memory, failed file validation, and mod loading errors.
• Resolve: If logs indicate insufficient memory, check actual use and increase available resources. If the issue starts after adding mods, back up the save and test without mods. Set page file size according to system needs; no fixed size can guarantee a solution for every crash.

2. Server cannot be found in the in-game list

• Investigate: Check whether startup completed, client and server versions match, listing filters, -ServerPlatform, and mod platform support.
• Verify networking: Connect using the LAN address first, then check the forwarded public game port. Clients supporting console connections can try:

  open <server public IP>:7777 <password>