Crashes, conflicts, or mods not applying? Most times it’s a bad load order. Let’s fix it step by step, fast and clean.
Prerequisites
- Access to your Oxygenserv panel (login and password)
- List of your Ark Steam Workshop mod IDs (e.g.,
731604991) - File Manager and Console access on the server
- 5 minutes to stop/start the server properly
Detailed steps
-
Stop the server cleanly
Log in to your Oxygenserv panel and open your Ark server page. Click the red “Stop” button and wait for a full shutdown. In the console, you should see “Server shutdown complete” and the status go to “Offline”. Don’t edit anything until it’s fully stopped to avoid overwrites. -
Open Startup/Variables
Go to the “Startup” or “Variables” tab. Look for the field holding the mod list: commonlyActiveModsorGameModIds. If you see something likeActiveMods=731604991,889745138, that’s your load order. Rule of thumb: the first ID loads first and takes priority when files overlap. -
Reorder the mod IDs
Edit the field and arrange IDs in the exact order you want, comma-separated, no spaces. Correct example:ActiveMods=731604991,889745138,1404697612. Put frameworks/base mods first, big overhaul/content mods next, QoL/tweaks last. Common mistakes: spaces or trailing commas (like...,) break loading; only digits and commas are valid. -
Save and start the server
Click “Save”. Go to the Console and hit the green “Start” button. Watch the logs: you should see “Downloading Mod” followed by “Installed mod”. If you get “Mod Mismatch” or download failures, double-check each ID, remove spaces, and ensure the ID is a valid Workshop mod. -
(Optional) Edit via GameUserSettings.ini
If there’s no startup variable for mods, use the file. Open File Manager and browse toShooterGame/Saved/Config/WindowsServer/GameUserSettings.ini(orLinuxServeraccordingly). Under[ServerSettings], add or editActiveMods=731604991,889745138,1404697612. Save, then restart; the console should show “Server started” with no errors. -
Verify in-game and fine-tune
Join the server and test one item/feature per mod (e.g., a unique engram). If a mod isn’t applied, move it earlier in the list (earlier = higher priority) and restart. If a mod blocks startup, temporarily remove its ID, start the server, then re-add after updating. As a last resort, back up and refreshShooterGame/Content/Modsto force a clean download on boot.
Tips & optimization
– Recommended order: 1) frameworks/base mods, 2) big overhauls, 3) content add-ons, 4) QoL/tweaks. This reduces file conflicts.
– Keep it lean: beyond 25–30 mods, watch RAM and boot time. Remove redundant overlap mods.
– Save a text snippet of your working list: ActiveMods=... for quick restores/rollbacks.
– After major order changes, do a cold restart (full stop, wait 10–15s, then start) to avoid cache issues.
– Invalid IDs halt the chain: grab the number after ?id= in the Steam Workshop URL (e.g., https://steamcommunity.com/sharedfiles/filedetails/?id=731604991).
FAQ
Where do I find an Ark mod ID?
On the mod’s Steam Workshop page, copy the number after ?id= in the URL. Example: .../filedetails/?id=731604991. Use only that number in ActiveMods, comma-separated.
My list reverts after restart. Why?
You may be editing the wrong place. If a startup variable (ActiveMods/GameModIds) is set, it will override the file. Edit the startup field (not just GameUserSettings.ini) or remove duplication. Save, full stop, then start.
Mods won’t download (timeout)?
Validate IDs (no spaces, no duplicates). Perform a cold restart. If it persists, back up and clear ShooterGame/Content/Mods, then start to force fresh downloads. If the console shows no “Downloading Mod”, the ID is invalid or Workshop is down.
Do clients need the same mod order?
No. The server enforces required mods and the client downloads them. If you see “Mod Mismatch”, re-check server IDs, order, and ensure all mods are up to date.
Nice work. With a clean mod order, your Ark server gets stable and predictable. Keep your ID list handy and tweak as updates roll in.