How to Install ARK Mods on Your Server

Installing mods on an ARK server is straightforward once you understand how ARK loads them — and the process differs between ARK: Survival Evolved (ASE) and ARK: Survival Ascended (ASA). This guide walks through both, plus the launch arguments and load-order tips that keep a modded server stable.

Step 1: Find Your Mod IDs

Every ARK mod is referenced by an ID, and where you get that ID depends on your game.

For ASE, mods live on the Steam Workshop. Open a mod's Workshop page and the ID is the long number at the end of the URL (for example, ?id=731604991). That number is what your server needs.

For ASA, mods live on CurseForge. Each mod has a CurseForge project ID shown on its page and used by ASA's built-in mod system. ASA downloads mods automatically through this system, so you generally don't hand-place files the way you might have with older ASE setups.

Collect the IDs for every mod you want, in the order you intend to load them.

Step 2: Tell the Server Which Mods to Load

ARK reads its active mods in one of two ways.

The most common method is the ActiveMods line in your GameUserSettings.ini, under the [ServerSettings] section. List your mod IDs separated by commas, with no spaces:

ActiveMods=731604991,111111111,222222222

Alternatively, you can pass mods on the command line using the -mods= launch argument:

-mods=731604991,111111111,222222222

Both achieve the same result — pick one method and stick with it to avoid confusion. If you set both, the launch argument typically wins, so don't split your list across the two.

Step 3: Mind the Load Order

The order of your mod IDs matters. ARK loads mods top to bottom, and later mods can override earlier ones. As a rule of thumb, load total-conversion and map mods appropriately for their type, and place mods that modify the same systems (like multiple structures or stacking mods) carefully so the one you want to "win" loads last. If something behaves unexpectedly after adding a mod, reordering your list is the first thing to try.

Step 4: Map Mods Are a Special Case

If you're running a custom map like Astraeos, you don't just add it to your mod list — you also set the map name in your server's startup so ARK loads that world instead of the default. The map mod still needs to be in your active mods so it downloads, but the server's map/level parameter is what actually points ARK at it. Check the map mod's page for the exact map name to use.

Step 5: Clients Auto-Download Everything

Here's the good news for your players: clients automatically download mods when they join. When someone connects to your modded server, ARK pulls the required Workshop items (ASE) or CurseForge mods (ASA) in the background before they spawn in. You don't need to send players a manual mod pack or installation instructions — as long as your server's mod list is correct, joining does the rest. Just make sure your players are on the same game build and the mods are up to date, since version mismatches are the most common cause of "failed to load" errors.

Troubleshooting Common Issues

If mods won't load, check the basics first: confirm every ID is correct, ensure there are no spaces in your comma-separated list, and verify each mod supports your current game version. A single outdated or delisted mod can prevent the whole server from starting. Restart the server after any mod change so it re-downloads and re-reads the list cleanly.

The Easy Way with Nxeon

Editing INI files and juggling launch arguments is doable, but it's easy to fat-finger an ID. Nxeon's ARK server hosting includes a one-click Mods manager that lets you add mods by ID, reorder your load order with drag-and-drop, and switch maps without touching a config file. It works for both ASE Workshop mods and ASA CurseForge mods, validates your list before launch, and restarts cleanly so clients auto-download on join. Set your mods once and get back to playing.