ARK: Survival Ascended uses CurseForge for mod distribution instead of the Steam Workshop. This guide covers finding mods, installing them on your server, managing mod load order, adding custom maps, updating and removing mods, and troubleshooting common mod-related issues.
Before You Start: Make sure your server is set up and running. If you have not configured your ARK: Survival Ascended server yet, see the Server Configuration Guide first. You will need access to GPanel to manage startup parameters.
ASA uses CurseForge, not Steam Workshop. Unlike ARK: Survival Evolved, ARK: Survival Ascended does not use the Steam Workshop for mods. All ASA mods are hosted on CurseForge. You cannot use Steam Workshop mod IDs for ASA.
Finding Mods on CurseForge
All ARK: Survival Ascended mods are published on CurseForge. To find the mod ID you need for server installation:
- Visit the ARK: Survival Ascended section on CurseForge.
- Browse or search for the mod you want. You can filter by category (gameplay, maps, items, structures, etc.).
- Open the mod page and locate the Project ID on the right side under the About Project section. This numeric ID is what you need.
Example CurseForge URL: https://www.curseforge.com/ark-survival-ascended/mods/super-structures
Project ID (shown on the page): 929420
^^^^^^ this is the mod ID you need
Tip: Write down or save the mod IDs before heading to GPanel. If you are installing multiple mods, keep a list of all IDs and the order you want them to load in.
Installing Mods via GPanel
The recommended method for adding mods to your ARK: Survival Ascended server is through GPanel startup variables:
- Stop your server from the GPanel console page.
- Navigate to the Startup tab.
- Locate the Mod IDs (or MODS) startup variable.
- Enter your CurseForge mod IDs separated by commas with no spaces:
929420,926956,927131 - Start the server. Mods will be downloaded and installed automatically on startup.
First startup with mods takes longer. The server must download each mod before it can finish starting. Large mods or total conversion mods can add several minutes to the startup time. Do not restart the server while mods are downloading.
Adding Mods via GameUserSettings.ini
You can also add mods by editing the configuration file directly. Access GameUserSettings.ini through GPanel's File Manager or via SFTP.
Under the [ServerSettings] section, add or edit the ActiveMods line:
[ServerSettings]
ActiveMods=929420,926956,927131Alternatively, mods can be specified in the server launch command line using the -mods flag:
-mods="929420,926956,927131"
Note: On Legion Hosting servers, the GPanel startup variable method is preferred over manual file editing. If you set mods in both the startup variable and the config file, the startup variable typically takes priority.
Mod Load Order
The order in which mod IDs are listed determines the load order. This matters because mods that modify the same game systems can conflict with each other.
| Position | What to Place Here | Example |
|---|---|---|
| First | Total conversion mods or custom maps (these override core game systems) | Total conversion, modded map |
| Middle | Major gameplay overhauls (stacking, structures, taming) | Super Structures, Awesome SpyGlass |
| Last | Minor quality-of-life mods and cosmetics | Death Recovery, HUD mods |
If two mods conflict, the one listed first takes priority. When troubleshooting mod issues, try rearranging the load order before removing mods entirely.
Installing Custom Maps (Modded Maps)
Modded maps work similarly to regular mods but require an additional step to tell the server which map to load:
- Find the modded map on CurseForge and note its Project ID.
- Add the map's mod ID to your mod list (ideally as the first entry).
- In GPanel's Startup tab, change the Map (or SERVER_MAP) variable to the map's internal name. This is usually listed on the mod's CurseForge page under installation instructions.
- Start the server. The map mod will download and the server will load the custom map.
Modded maps vs. DLC maps: DLC maps (such as The Center, Scorched Earth, Aberration, etc.) are official content and do not require a mod ID. They are selected using only the Map startup variable. Modded maps from CurseForge require both the mod ID in the mod list and the correct map name in the Map variable.
Client-Side Mod Installation
Players connecting to your modded server must have the same mods installed on their client. If a player is missing a required mod, they will not be able to join or will be disconnected during loading.
How Players Install Mods
- Players can install the CurseForge app and subscribe to the same mods your server uses.
- Alternatively, when a player attempts to join a modded server, ARK: Survival Ascended will prompt them to download any missing mods automatically (if the mods are available on CurseForge).
- Players should ensure their mod versions match the server's. Outdated mods on the client side will cause connection failures.
Share your mod list: It is a good practice to share your server's mod list (including CurseForge links or mod IDs) with your players. This helps them install mods before attempting to connect and reduces troubleshooting time.
Updating Mods
Mod updates are handled automatically in most cases:
- Server-side: When the server starts, it checks for mod updates and downloads new versions automatically. A simple server restart is usually enough to apply mod updates.
- Client-side: Players using the CurseForge app will receive mod update notifications. Players must update their local mod files to match the server version.
- Forcing an update: If a mod does not update automatically, stop the server, and start it again. The startup process re-validates all mod files.
Mod updates can break things. A mod update may introduce incompatibilities with other mods or with the current game version. If your server stops working after a mod update, check the mod's CurseForge page for known issues or roll back by disabling the problematic mod temporarily.
Removing Mods
- Stop the server.
- Go to the Startup tab in GPanel and remove the mod ID from the mod list.
- If you added the mod via
GameUserSettings.ini, also remove it from theActiveModsline. - Start the server. The mod will no longer load.
Warning: Removing mods that add items, structures, or creatures to the game will cause those objects to disappear from the world. Players who had modded items in their inventory will lose them. This can cause issues with bases built using modded structures. Always warn your players before removing content mods.
Troubleshooting Common Mod Issues
Server fails to start with mods
- Check mod IDs: Verify that all mod IDs in your startup variable or config file are correct CurseForge Project IDs. A typo or invalid ID will prevent the server from starting.
- Check for incompatible mods: Remove all mods, then add them back one at a time, starting the server after each addition. This identifies which mod is causing the failure.
- Console errors: Check the GPanel console output for error messages. Mod-related errors usually mention the mod ID or mod name.
- Mod discontinued: If a mod has been removed from CurseForge, the server cannot download it. Remove the ID from your mod list.
Version mismatch errors
- Game update vs. mod update: After a major ARK: Survival Ascended game update, some mods may not be compatible with the new version until the mod author updates them. Check each mod's CurseForge page for compatibility notes.
- Client/server mismatch: Both the server and all players must be running the same version of each mod. Restart the server to pull the latest mod versions, and ask players to update their mods via the CurseForge app.
Mod conflicts
- Symptoms: Crashes, missing items, broken UI, or unexpected gameplay behavior after adding a new mod.
- Resolution: Rearrange the mod load order (see the Mod Load Order section above). If the conflict persists, check the mod pages on CurseForge for known incompatibilities. You may need to choose one mod over the other.
Players cannot connect to the modded server
- Confirm players have all required mods installed and up to date.
- Verify the mod versions match between the server and the client.
- If the issue started after adding a new mod, try removing it temporarily to confirm it is the cause.
- Ensure BattleEye settings match between the server and client. See the How to Connect guide for details.
Performance issues with mods
- Each mod adds server load. Running many large mods can increase startup time, RAM usage, and cause lag.
- Total conversion mods are the heaviest. Combining multiple total conversions is not recommended.
- If the server is struggling, consider reducing the number of active mods or upgrading your server plan for more resources.
Popular Mod Categories
| Category | Description | Examples |
|---|---|---|
| Structures | Enhanced building pieces, snapping improvements, and new construction options | Super Structures, Castles & Keeps |
| Quality of Life | Stacking mods, HUD enhancements, death recovery helpers | Awesome SpyGlass, Death Recovery |
| Creatures | New tameable creatures, creature rebalancing, and companion overhauls | Additional Creatures, Dino Storage |
| Maps | Custom worlds with unique terrain, resources, and challenges | Community-created custom maps |
| Total Conversions | Complete game overhauls that change core mechanics, progression, and gameplay | Various total conversion projects |
Related Articles
- ARK: Survival Ascended Server Configuration
- ARK: Survival Ascended Admin Commands
- How to Connect to Your ARK: Survival Ascended Server
- How to Find Your Server IP and Port
- How to Upload Files via SFTP
Need Help? If you are experiencing mod issues not covered in this guide, open a support ticket and include your server ID, the mod IDs you are using, and any relevant console output from GPanel.
