ARK: Survival Ascended Dedicated Server: Complete Setup Guide

ARK: Survival Ascended rebuilt the original ARK on Unreal Engine 5, and the jump in visual fidelity came with a corresponding jump in server hardware requirements. If you're coming from hosting the original ARK: Survival Evolved, do not reuse the same box's specs — Ascended routinely needs two to three times the RAM and noticeably more single-core CPU headroom to hold a stable tick rate with a full tribe roster and a handful of mods.

Most of the "random crash" reports admins post in ARK communities trace back to one root cause: the server ran out of memory and UE5 crashed rather than degrading gracefully. Unlike a tick-rate slowdown you can observe and react to, an out-of-memory crash gives almost no warning — the server is fine, then it isn't. Everything in this guide is written with that failure mode in mind: size generously, monitor proactively, and treat scheduled restarts as a feature rather than an inconvenience.

This guide covers what Ascended actually needs on real hardware (not the marketing-minimum numbers), how to configure GameUserSettings.ini and Game.ini for a survival server that doesn't constantly crash, mod installation through the CurseForge-based mod system Ascended uses (a change from Evolved's Steam Workshop pipeline), and the crash/desync issues that show up most often in the wild.

What Is an ARK: Survival Ascended Dedicated Server?

It's the standalone server binary (distributed via SteamCMD as app ID 2430930) that runs a persistent ARK world independent of any player's own game session. Key differences from Evolved worth knowing before you provision hardware:

• Built on Unreal Engine 5, which means Nanite/Lumen-driven asset streaming pushes far more RAM and disk I/O than Evolved's UE4 engine did
• Mods are distributed through CurseForge rather than the Steam Workshop, requiring a CurseForge API key for automated mod downloads on the server side
• Save file format changed from Evolved, meaning you cannot simply copy an old Evolved save into Ascended — there are one-way conversion tools, but the maps themselves were rebuilt
• Cross-ARK transfers (via clusters) work the same conceptually as Evolved but require separate cluster ID configuration per server

System Requirements and Pricing

These numbers reflect real Ascended server behavior with a populated map (dinos tamed, structures built) rather than an empty freshly-wiped world, which uses noticeably less RAM.

If you're running a cluster (multiple connected maps like The Island plus Scorched Earth), remember each map is its own server process with its own RAM/CPU footprint — a 3-map cluster needs roughly 3x a single map's resources, not a shared pool.

Step-by-Step Setup

1. Install SteamCMD and Download the Server

ARK Ascended's dedicated server is downloaded through SteamCMD like most Source/Unreal-based dedicated servers:

steamcmd +force_install_dir ./ASA +login anonymous +app_update 2430930 validate +quit

The initial download is large (40+ GB with UE5 assets), so budget real time and disk space for the first install — subsequent updates are usually smaller delta patches.

1a. Monitor Disk Space During Install

The initial download and subsequent extraction can briefly require more free space than the final installed size, since SteamCMD downloads compressed archives before extracting them. Budget at least 1.5x the expected final install size as free space headroom during the first install to avoid a failed extraction partway through — restarting a failed 40 GB download because of a full disk is a frustrating way to lose an afternoon.

2. Configure GameUserSettings.ini

Located in ShooterGame/Saved/Config/WindowsServer/ (yes, "WindowsServer" even on a Linux host — this is an Unreal Engine convention carried over from the client build paths). The keys that matter most for a stable survival server:

3. Configure Game.ini for Deeper Balance Changes

Game.ini (same folder) handles per-species taming/breeding multipliers and engram point overrides that GameUserSettings.ini doesn't expose. A common addition for a PvE cluster is custom ConfigOverrideItemMaxQuantity and per-level engram point tables so players don't run out of engram points before reaching max level — the vanilla defaults are noticeably tight for modded or high-level servers.

4. Set Launch Parameters

The map and core flags are passed on the command line, not in an ini file:

./ArkAscendedServer.exe TheIsland_WP?listen?SessionName=MyServer?ServerPassword=?ServerAdminPassword=changeme?Port=7777?QueryPort=27015 -server -log -NoBattlEye -crossplay -mods=123456,789012

Note -crossplay enables Epic Games Store cross-play alongside Steam — leave it off if you only want Steam players. -NoBattlEye disables BattlEye anti-cheat, which some modded servers require since certain mods are incompatible with it; only disable it if a specific mod needs it.

5. Install Mods via CurseForge

Unlike Evolved's Steam Workshop integration, Ascended mods are hosted on CurseForge. You'll need a CurseForge API key (free, registered through CurseForge Core) referenced in your server's mod-download script, since SteamCMD alone can't pull CurseForge-hosted content. Pass mod IDs via the -mods= launch flag in load order — order matters when mods modify overlapping systems like structures or engrams.

5a. Configure a Cluster for Multi-Map Transfers

To let tribes transfer dinos, items, and characters between maps, launch each server instance with the same -ClusterId=yourclustername flag and a shared -ClusterDirOverride path accessible to every map process. Enable PreventDownloadSurvivors=False, PreventDownloadItems=False, and PreventDownloadDinos=False in GameUserSettings.ini on each map if you want full transfer support — leaving any of these at their restrictive default silently blocks that specific category of transfer without an obvious error message to players.

6. Open Firewall Ports

Default ports are 7777 (game, UDP), 7778 (secondary, UDP), and 27015 (query, UDP). With UFW: sudo ufw allow 7777:7778/udp && sudo ufw allow 27015/udp. If running RCON for admin commands, also open your configured RCON port (commonly 27020) restricted to trusted IPs only.

7. Set Up Automated Restarts and Saves

Ascended servers benefit heavily from a scheduled daily restart (UE5's memory footprint grows over long uptimes even with no leaks in the traditional sense, due to asset streaming caches). Combine this with RCON-triggered saveworld commands before each restart and before backups, so you're never backing up a mid-write save file.

8. Tune Structure and Resource Limits

Two settings prevent the most common late-game server degradation: TheMaxStructuresInRange (caps total structures within a radius to stop mega-bases from tanking performance for everyone nearby) and PerPlatformMaxStructuresMultiplier (limits structures per individual platform saddle, a common lag source on rafts and Mosasaur platforms). Both belong in GameUserSettings.ini and are worth setting deliberately rather than leaving at engine defaults once a server has been live for a few months.

9. Configure Dino Wipe and Decay Schedules

Structure and dino decay timers (PvPStructureDecayPeriodMultiplier, AutoDestroyOldStructuresMultiplier) keep abandoned bases from accumulating indefinitely on a public server. A reasonable starting point for a busy PvE server is a decay period long enough that active players never lose builds unexpectedly (2-3 weeks of inactivity) but short enough that truly abandoned tribes don't permanently occupy prime building spots.

Common Issues and Troubleshooting

Server Crashes Silently After a Few Hours

Check available RAM first — Ascended will crash rather than gracefully degrade when it runs out of memory, and this is by far the most common cause of "random" crashes. Check ShooterGame/Saved/Logs/ for out-of-memory or asset-streaming errors.

Players Can See the Server But Can't Connect

Almost always a UDP port issue on 7777/7778, or a QueryPort (27015) conflict if you're running multiple maps on one box — each map instance needs its own unique QueryPort, or the server browser listing will be wrong even if the game port itself works.

Mods Not Loading

Confirm mod IDs are correct CurseForge project IDs (not Evolved-era Workshop IDs — they are different numbering systems entirely) and that load order in the -mods= flag doesn't conflict; some mods explicitly require being loaded before or after a dependency.

Server Uses BattlEye but a Specific Mod Needs It Disabled

Check the mod's own documentation before disabling BattlEye server-wide — there's no per-mod BattlEye toggle, so turning it off to satisfy one mod removes anti-cheat protection for the entire server, which matters more on a public PvP server than a small private one.

Rubber-Banding / Desync During Raids or Boss Fights

This is typically a CPU tick-rate issue, not network bandwidth — large structure counts and dozens of dinos simultaneously processing collision and AI can bottleneck a single map's core allocation. Reducing structure decay timers to encourage cleanup, or splitting a mega-base community across a cluster, both help.

Corrupted Save After a Crash

Keep at least 3 rolling save backups taken via scheduled RCON saveworld + filesystem copy — Ascended's save files can occasionally corrupt on an ungraceful shutdown, and having same-day backups avoids losing a full wipe cycle's progress.

Tribe Log Spam or Missing Tribe Log Entries

Large, active tribes can generate enough log volume to slow down the tribe log UI itself; this is a client-side rendering symptom rather than a server performance issue, though extremely large tribe rosters can also indirectly cause it via sheer event volume. Encourage tribes to periodically clear old log entries if this becomes disruptive.

Cluster Transfers Failing Between Maps

Check that every map in the cluster shares the exact same -ClusterId and points at the same -ClusterDirOverride path with matching read/write permissions — a typo in the cluster ID on just one map is enough to silently break transfers to or from that specific server while the rest of the cluster works fine.

Server Uses Far More RAM Than Expected on a Fresh Map

Compare against a populated map, not an empty one — Ascended's baseline RAM use with zero players and no structures is meaningfully lower than the same map a month into a busy season, since tamed dinos, structures, and item entities all add ongoing memory overhead. Budget for the populated-map numbers, not day-one numbers.

Troubleshooting Reference Table

Common Mistakes to Avoid

The single most common mistake is sizing an Ascended server using Evolved-era numbers from an old spreadsheet or a friend's years-old server — Ascended's UE5 asset streaming genuinely needs more headroom, and undersizing shows up as unpredictable crashes rather than a gentle slowdown you can react to. A second common mistake is running a cluster without giving each map its own QueryPort, which causes the server browser listing to become unreliable even though direct-connect still works, confusing admins into thinking the whole server is down. A third is disabling BattlEye for a single mod's convenience and forgetting to re-enable it once that mod is removed, quietly leaving a public server without anti-cheat protection for months.

Buyer's Checklist

• Confirm the plan's RAM is sized for Ascended specifically, not reused Evolved-era sizing — Ascended needs meaningfully more
• Ask whether the host supports CurseForge mod integration or only legacy Steam Workshop tooling
• Check single-core clock speed, since UE5's per-map tick processing is CPU-bound similarly to other Unreal titles
• If running a cluster, confirm the host can allocate separate QueryPorts per map on the same IP without conflicts
• Verify NVMe storage — the large UE5 asset footprint means slow disk I/O shows up as loading stutter and save/backup delays
• Check whether automated restarts and RCON access are supported out of the box

Performance Tuning Walkthrough: From Stutter to Stable

If your Ascended server is already live but players complain about rubber-banding or the box keeps flirting with its RAM ceiling, work through these steps in order — one variable at a time, so you know which change mattered.

Step 1: Capture a Baseline During Peak Hours

Watch memory with free -m or your host's monitoring during a busy evening session, not an empty afternoon. Ascended's RAM curve climbs with tames, structures, and active players simultaneously, and the number that matters is your worst hour, not your average. If peak usage sits within 10-15% of your total RAM, you are one busy raid away from an out-of-memory crash regardless of how stable things look right now.

Step 2: Audit Structure and Dino Density

Use admin spectator mode to fly the map's popular build zones and look for mega-bases and oversized breeding pens. If one or two tribes account for most of the density, tightening TheMaxStructuresInRange and agreeing on community breeding caps will do more for tick stability than any hardware change — CPU cost here is about concentration, not just totals.

Step 3: Match Restart Cadence to Memory Growth

Chart RAM usage across a few days of uptime. If it climbs steadily and only resets on restart, shorten your scheduled restart interval until the peak stays comfortably inside your headroom — a 12-hour cycle instead of 24 is a free fix that costs players two brief planned interruptions instead of one surprise crash.

Step 4: Re-Test After Each Change

Apply one adjustment, observe a full peak cycle, and only then move to the next. Admins who change five settings at once end up with a stable server and no idea which change to keep when they next migrate hardware or set up a second map.

Evolved vs Ascended: What the Upgrade Costs in Hosting Terms

Plenty of communities still run both games side by side, and the hosting delta is worth seeing plainly before you commit to migrating a whole cluster.

The last row of that table is the one that changes admin behavior most: Evolved gave you a visible slowdown to react to, while Ascended tends to fail suddenly. Monitoring and headroom are not optional extras on Ascended — they are the difference between a planned upgrade and a mid-raid outage.

Real-World Scenario: A Two-Map Cluster on a Budget

A common community setup: The Island and Scorched Earth clustered together for a 15-player PvE group with a modest quality-of-life mod list. Each map runs as its own process with 16 GB of RAM budgeted, unique Port/QueryPort pairs, a shared -ClusterId and cluster directory, and a staggered restart schedule so both maps are never down simultaneously. The admin keeps three rolling saveworld-then-copy backups per map and tests every mod update on a throwaway instance first. Total spend lands around the cost of a single well-specced dedicated box — and when the community later votes to add a third map, the migration is a copy of an already-proven per-map recipe rather than a fresh research project. That repeatability is the real payoff of doing the first two maps carefully.

Frequently Asked Questions

Can I transfer my ARK: Survival Evolved save to Ascended?

Not directly — Ascended uses a different save format built for UE5. Some community conversion tools exist for specific map layouts, but treat Ascended as a fresh start rather than expecting a clean 1:1 migration.

How much RAM does a modded Ascended cluster actually need?

Budget at least 16-24 GB per map once you add several mods, and remember each map in a cluster is a separate process — a 3-map modded cluster can realistically need 60-80 GB total across the cluster.

Does Ascended support cross-play between Steam and Epic Games Store?

Yes, via the -crossplay launch flag, but it must be enabled server-side and both platforms' anti-cheat requirements need to be compatible with any mods you're running.

Why does my server show a different max dino level than expected?

Wild dino level caps are controlled by DifficultyOffset in GameUserSettings.ini combined with any Game.ini overrides — check both files, since a Game.ini override can silently take precedence.

Is BattlEye required?

It's on by default and recommended for public PvP servers to reduce cheating, but some mods are incompatible with it and require the -NoBattlEye flag — check your mod list's documentation before disabling it.

How many maps can realistically run in one cluster?

There's no hard engine limit, but each map is its own full server process with its own RAM/CPU footprint, so practical clusters top out around 4-6 maps before the combined hosting cost and admin overhead outweighs the benefit for most communities.

Do I need a separate RCON tool, or is one built in?

Ascended supports RCON natively via the port and password set in GameUserSettings.ini; any standard RCON client (or a purpose-built ARK admin panel) can connect to issue commands like saveworld, broadcast messages, or kick/ban players remotely.

What's the safest way to test a mod update before pushing it to a live server?

Spin up a second, smaller instance with the same mod list on the same box (different ports and a copied-but-separate save), verify the server boots cleanly and the map loads without errors, and only then update the mod IDs on the live cluster.

Why do structure counts near mega-bases cause lag even on a well-specced server?

Each structure carries ongoing decay-timer and rendering-relevancy calculations; a sufficiently dense mega-base can hit CPU limits regardless of raw hardware spend, which is why TheMaxStructuresInRange and reasonable per-platform caps matter as much as the underlying box.

ARK: Survival Ascended rewards a server that's sized correctly from day one — undersizing RAM is the single most common cause of the "random" crashes that frustrate whole tribes mid-raid. WebsNP's Linux dedicated server plans give you the dedicated cores and NVMe storage UE5 titles need, and our VPS hosting is a solid starting point for a smaller single-map server — contact us if you want help sizing a cluster. If you're weighing whether you even need a full dedicated server yet, our ARK non-dedicated vs dedicated comparison breaks down the trade-offs, and our SteamCMD guide covers the download process this server shares with dozens of other titles.