ARK Mods & Provider IDs

← All guides · GAME GUIDE

ARK: Survival Ascended and ARK: Survival Evolved use different mod systems. Synix manages the supported ordered provider ID lists; the game/provider delivers the content.

Ascended versus Evolved

	ARK: Survival Ascended (ASA)	ARK: Survival Evolved (ASE)
Mod provider used by Synix	CurseForge	Steam Workshop
ID to enter	CurseForge project ID	ASE Workshop item ID
Activation managed by Synix	Launch argument -mods=ID1,ID2	ActiveMods plus ModInstaller / ModIDS, with -automanagedmods
Recognized package descriptor	ASA .uplugin with required provider identity and cooked WindowsServer content	ASE .mod with matching prepared content
Who downloads/updates	ARK's provider integration	ARK/Steam's supported download mechanism

Steam distributing the game server does not mean both editions use Steam Workshop mods. ASA's CurseForge IDs and ASE's Workshop IDs are not interchangeable.

Use the ID list directly

1. Stop the server and make a full backup.
2. Open Server Options → Mod & Plugin Manager.
3. Select the appropriate ARK add-on system.
4. Open Manage Mod IDs where available and enter/review the ordered IDs.
5. Keep the author's required load order and dependencies.
6. Save the reviewed list, then start manually.
7. Watch ARK's log while it downloads/updates the content, and test with matching clients.

For ASE, the managed Windows configuration is under ShooterGame/Saved/Config/WindowsServer: GameUserSettings.ini contains ServerSettings/ActiveMods; Game.ini contains ModInstaller/ModIDS. Do not maintain a conflicting duplicate list elsewhere.

Changing the list does not start the server automatically.

Choose a downloaded ZIP or extracted folder

You can start with Import ZIP / folder, then choose a downloaded ARK server package.

Synix inspects its descriptor and content, detects the edition and supported provider IDs, then shows those IDs for review. Extra wrapper folders are handled where the reader can identify a valid package; the ZIP filename alone is not treated as authoritative metadata.

This workflow does not copy/register the package as an offline mod installation. It adds the detected IDs to the provider workflow; ARK downloads content on its next start. It does not pin the precise version in your ZIP.

If you need a fully offline/local ARK deployment not represented by this workflow, follow the game/provider's supported procedure. Do not use an arbitrary destination-folder rule as a substitute for registration.

What package inspection expects

For ASA, a .uplugin alone is insufficient. The package must include the supported ASA/CurseForge identity and a cooked WindowsServer build under the expected Content/Paks structure. Client-only, incomplete, ambiguous, or wrong-edition packages are rejected.

For ASE, the reader checks the .mod descriptor and matching content/metadata. An ASA .uplugin archive is not an ASE mod package.

A valid mod that uses metadata/layouts outside the reader's supported formats may need its provider ID entered directly. Do not rename it or invent metadata to force acceptance. Report a reproducible unsupported layout without redistributing private/commercial content.

Updates, removing IDs, and backups

Order matters; preserve the old list before changing it. Adding/removing an ID can change world content and dependencies.

Remove Selected removes the configured ID, not the provider's downloaded cache or a mod's persisted world data. It cannot restore the provider's old version. Preserve full backups and follow the author's update/removal instructions.

A package scan cannot certify content ARK downloads later. Premium/account/client requirements still apply. A successful ID save is not proof the game downloaded or loaded the mod.

For config edits such as passwords, ports, or player limits, use the Configuration Editor; its mapped Save workflow updates Synix's common fields.

References bundled with the support catalog: ASA CurseForge · CurseForge installation methods · ASE Workshop

Related: Mods & Plugins · Game Mod Support · Backups