Manual-first Windows server guide
ARK: Survival Ascended Dedicated Server Setup and Recovery
This ASA-specific guide avoids the most damaging ARK mistake: copying Survival Evolved commands into a Survival Ascended server. It uses app 2430930, ArkAscendedServer.exe, current map identifiers and ASA port syntax, then preserves map, survivor, tribe, cluster, configuration and ordered mod state as one recoverable operational set.
An ASA instance is map-centered and memory-heavy even before players build, while clusters add coordinated transfer state across multiple maps. ASA also uses a CurseForge-backed cross-platform mod ecosystem rather than ASE Steam Workshop automation, and its official-community documentation mixes shared ARK examples that must be checked for the correct executable, App ID and syntax.
SteamCMD App ID
2430930
Do not substitute ARK: Survival Evolved app 376030 from a shared or older example.
ASA executable
ArkAscendedServer.exe
ShooterGameServer.exe is the older ASE executable and is not the correct ASA runtime.
Default map ID
TheIsland_WP
Use an ASA map identifier and verify it against the current map table before launch.
Default network set
UDP 7777, 7778 and 27015
Gameplay, companion/peer and query each need the actual instance-specific value.
Core configuration
GameUserSettings.ini and Game.ini
Stop before editing because the running server can remove changes.
Native mod argument
-mods=<id>,<id>
ASA uses its cross-platform mod ecosystem, not ASE ActiveMods or Steam Workshop server syntax.
Protect the server first: Run SaveWorld and stop cleanly before copying the complete ShooterGame/Saved state, both WindowsServer INIs, launch line, map ID, cluster store and ordered mod IDs. Never test an update or mod removal on the only good world.
Size the host before downloading
PC and capacity guidance
The map-memory figures come from the ARK Official Community Wiki and describe empty, unmodded examples, not guaranteed ceilings. Player labels and 32 GB host planning are conservative editorial recommendations that require measurement on the selected map.
| Profile | Players | Memory | Processor | Storage |
|---|---|---|---|---|
| One small unmodded map Conservative starting point | A private group on one map | 32 GB total host RAM is a conservative editorial starting point | At least four logical cores with strong single-thread performance | SSD space for the roughly 11 GiB base install, live save, update staging and a separate full snapshot |
| Mature, modded or clustered world Conservative starting point | Persistent maps with structures, tames, transfers or mods | Size each map from observed peak commit; do not multiply an empty-map number into a promise | Four logical cores per instance as a planning baseline, with measured per-core headroom | One coordinated pre-update snapshot for every map and its cluster transfer store |
ASA, not ASE
Install the correct Survival Ascended runtime
Verify the App ID, executable and map syntax before creating any world; mixed ARK examples are a common source of false starts.
- 1
Install app 2430930 to an isolated folder
Use 64-bit Windows and SteamCMD anonymous login, keeping this instance separate from any ARK: Survival Evolved install.
steamcmd +force_install_dir <server-path> +login anonymous +app_update 2430930 validate +quit - 2
Verify the ASA executable
Require ShooterGame/Binaries/Win64/ArkAscendedServer.exe before launch. Reject ShooterGameServer.exe and app 376030 as ASE artifacts.
- 3
Build an ASA launch line
Start with a current ASA map such as TheIsland_WP, concatenate question-mark options after it, and use spaced hyphen arguments such as -port=7777.
Place ServerAdminPassword last among the question-mark options; the setup reference warns ASA can consume following text as part of it.
First validation
Prove the map can save, restart and be joined
A browser listing is not the acceptance test; prove world identity and UDP gameplay before adding mods or a cluster.
- 1
Start private and unmodded
Confirm the intended map/save directory and allow one test survivor to establish persistent state.
- 2
Exercise clean save and exit
Authenticate as administrator, run cheat SaveWorld, allow disk completion, then run DoExit and confirm the process has ended.
cheat SaveWorld - 3
Test each network path
Verify the gameplay pair and query port from an independent outside network, then test every advertised client platform on a matching build.
Query visibility and RCON success do not prove that player gameplay traffic works.
Keep every layer consistent
Ports, firewall, and router setup
Open only the services your ARK: Survival Ascended server actually uses. The game process, Windows Firewall rule, router forward, and player join address must all agree on the same port and protocol.
| Port | Protocol | Purpose | Exposure | Notes |
|---|---|---|---|---|
| 7777 (configurable) | UDP | Primary gameplay traffic | Internet playersRequired for this use | ASA changes this listener with -port=, not the older ASE ?Port= form.[ark-setup] |
| 7778 (game port + 1) | UDP | Companion/peer traffic | Internet playersRequired for this use | Reserve a non-overlapping pair for every concurrently running map.[ark-setup] |
| 27015 (configurable) | UDP | Steam query and browser discovery | Internet playersRequired for this use | A visible listing proves query registration, not that gameplay UDP reaches the instance.[ark-setup] |
| 27020 by default when enabled | TCP | Optional RCON administration | Optional administrationOptional | Keep private or tightly allowlisted; RCON is not required for players to join.[ark-setup][ark-commands] |
Never expose an administration or RCON port merely so players can join. Keep remote administration private whenever possible, use a strong unique credential, and confirm the game's own security model before forwarding it.
Know what must survive a reinstall
Files, worlds, and configuration
| File or folder | Purpose | Backup | Notes |
|---|---|---|---|
| ShooterGame/Saved/SavedArks | Map, survivor, tribe and related persistent world state | Critical | Resolve AltSaveDirectoryName and the active ASA map subdirectory before copying.[ark-setup][ark-config] |
| ShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini | Basic and intermediate server settings | Critical | Most server settings live under the documented sections; stop before editing.[ark-config] |
| ShooterGame/Saved/Config/WindowsServer/Game.ini | Advanced rules, levels, engrams and balance configuration | Critical | Version it with GameUserSettings.ini, the map ID and launch line.[ark-config] |
| Configured cluster transfer directory | Cross-map upload/download state for clustered servers | Critical | Snapshot every participating map and the transfer store as a coordinated set.[ark-setup][ark-config] |
| Setting or file | Location | What it controls | Restart? |
|---|---|---|---|
SessionName?SessionName=DistinctiveName | Question-mark launch option after the map identifier | Names the server in discovery.[ark-setup][ark-config] | Yes |
ServerPassword and ServerAdminPasswordUse unrelated secrets and place ServerAdminPassword last among question-mark options | Question-mark launch options | Separates joining from administrator authentication.[ark-setup] | Yes |
-port-port=7777 | Hyphen launch argument | Changes ASA's UDP gameplay listener.[ark-setup] | Yes |
-mods-mods=123456,789012 | Hyphen launch argument | Loads ASA mod IDs in the intended order.[ark-config][ark-crunch-381] | Yes |
AltSaveDirectoryNameA stable per-map folder name chosen before the first public start | Question-mark launch option | Separates save layouts for multiple local maps.[ark-setup][ark-config] | Yes |
Avoid incompatible clients and unsafe shortcuts
Players, mods, and administration
Cross-play and editions
Wildcard announced ASA multiplayer across Steam, Xbox/Windows and PlayStation, but the exact self-hosted platform-filter syntax remains version-sensitive.
- The official-community wiki describes -ServerPlatform examples but marks the switch undocumented by Wildcard.
- No platform filter is described as allowing cross-play by default; verify that behavior on the current server build.
- A mod must be available for every joining platform; a cross-platform ecosystem does not make every package cross-platform.
- Non-Nitrado self-hosted servers may appear under a player-server filter, which must be checked on each client UI.
Mods and extensions
ASA loads ordered CurseForge-backed mod IDs with -mods=; it does not use ASE's ActiveMods, -automanagedmods or Steam Workshop server workflow.
- Preserve the exact ordered ID list before updates.
- Create an unmodded recovery point before installing the first package.
- Verify the package supports every promised client platform.
- Test content-mod removal on a copied map because saving without the mod can permanently remove owned objects.
Administration
Use separate join and admin secrets, in-game admin commands or restricted RCON, and capture current platform-aware account identifiers before maintaining access lists.
- Put ServerAdminPassword last among question-mark launch options.
- In-game multiplayer commands generally require enablecheats and the cheat/admincheat prefix.
- Optional RCON is an administration path, not a player connectivity requirement.
- Do not assume an old Steam-ID-only allowlist guide applies to all ASA platforms.
Preserve a return path before maintenance
Updates, backups, and rollback
Update without gambling the world
Update only after a clean save and complete matched snapshot; test map, survivor/tribe state, ordered mods and external joining before reopening.
- 1
Record and stop
Record build, map, launch line, INI hashes, platform choices and mod order, then run SaveWorld and DoExit.
- 2
Snapshot every dependent state store
Copy the complete map save, both INIs and launch configuration; for a cluster, coordinate all participating maps and transfer state.
- 3
Validate and reopen cautiously
Run app_update 2430930 validate while stopped, review mod compatibility, then verify tribe ownership, representative tames/structures and a matching-client join.
steamcmd +login anonymous +app_update 2430930 validate +quit
Back up and prove the restore path
ASA's rolling backups are useful, but the reliable recovery unit includes map, survivor/tribe or combined store state, configuration, mods and any cluster transfer data.
- 1
Identify the save model
Resolve the active map directory, AltSaveDirectoryName and whether the current build uses classic separate profiles or the combined store model.
- 2
Take an off-tree matched snapshot
After SaveWorld and DoExit, copy the complete state set outside the install folder rather than relying only on rotating in-tree backups.
- 3
Restore in quarantine
Verify a known survivor, tribe ownership, structures, tames, inventory and any cluster upload/download before replacing production state.
Diagnose before reinstalling
Common ARK: Survival Ascended server problems
The ASA server starts the wrong runtime or exits immediately
What players see
The command references ShooterGameServer.exe, app 376030 or an ASE-style map/port option.
Likely cause
A mixed ARK or Survival Evolved example was copied into a Survival Ascended deployment.
- 1.Protect any existing ShooterGame/Saved data before reinstalling.
- 2.Confirm app 2430930 and ArkAscendedServer.exe.
- 3.Rebuild the launch line with a current ASA map ID and -port= syntax.
ASA keeps listening on UDP 7777
What players see
A custom gameplay port in the command appears to be ignored.
Likely cause
The older ASE ?Port= option was used instead of ASA's -port= hyphen argument.
- 1.Back up the launch configuration and stop the instance.
- 2.Replace the option with -port=<value> and reserve value+1 for peer traffic.
- 3.Update firewall/router rules and verify sockets before external testing.
Options after the ASA admin password do not apply
What players see
Part of the launch line behaves as though it became password text.
Likely cause
ServerAdminPassword was not placed last among the question-mark options.
- 1.Rotate any secret exposed during diagnosis.
- 2.Move ServerAdminPassword to the end of the concatenated question-mark block.
- 3.Restart privately and verify each option from logs/runtime behavior.
A modded ASA map loads with missing content
What players see
Structures, creatures or items disappear after a mod update/removal.
Likely cause
The ordered mod set changed, a package is unavailable for the platform/build, or the world saved without its content mod.
- 1.Stop immediately and duplicate the current save before another write.
- 2.Restore the exact ordered -mods list and compatible package versions on a copy.
- 3.Use the matched pre-change snapshot if missing content persists.
Every focused ARK: Survival Ascended troubleshooting guide
- ARK: Survival Ascended Connection Timeout Fixes →
- ARK: Survival Ascended Server Settings Explained →
- ARK: Survival Ascended Mods Not Loading After Update →
- ARK: Survival Ascended Server Backup and Rollback →
- Fix an ASE Command Used for an ARK: Survival Ascended Server →
- ARK: Survival Ascended Custom Port Stuck on UDP 7777 →
- ASA Admin Password Breaks Options After It: Fix Launch Order →
Evidence stays visible
Sources and verification
Technical behavior changes with server builds. These are the references reviewed for this guide. Official documentation wins if a later patch changes a path, port, command, or compatibility rule.
[ark-setup] ARK Official Community Wiki
Dedicated server setup ↗Reviewed 2026-08-30 · Community or project reference
[ark-config] ARK Official Community Wiki
Server configuration ↗Reviewed 2026-08-30 · Community or project reference
[ark-commands] ARK Official Community Wiki
Console commands ↗Reviewed 2026-08-30 · Community or project reference
[ark-crunch-381] Studio Wildcard
Community Crunch 381: ASA platforms and cross-platform mods ↗Reviewed 2026-08-30 · Official documentation
[ark-crunch-399] Studio Wildcard
Community Crunch 399: cross-platform mod examples ↗Reviewed 2026-08-30 · Official documentation
Keep learning
Related guides
Host a game server at home
Prepare Windows, network and backup boundaries before exposing an ASA map.
Open guide →
ASA troubleshooting
Diagnose runtime, port, mod and map-state failures without risking the only save.
Open guide →
ASA dedicated-server FAQ
Review focused answers about ASA syntax, saves, cross-play and clusters.
Open guide →