Modding guide

Load order and name collisions: when two mods touch the same thing

9 min readASA DevKit as of November 2026 (UE 5.8.1)

Your mod works alone. On a server with forty other mods, something stops working, and nobody gets an error. This page explains why.

It covers what load order is, which things the first mod wins and which the last mod wins, and the names that clash when two mods pick the same one. It ends with a way to test your mod against others before players do.

  • You'll learn: where load order comes from, what it decides, which names have to be unique, and how to make your mod a good neighbor
  • Time: 15 minutes to read; half an hour to run a two-mod test
  • Level: intermediate; you've published a mod or are about to
  • You'll need: a registered mod; for the test, a local dedicated server (testing)

What load order is

A server loads its mods in the order of its mod list: -mods= on the command line, or ActiveMods in its settings. The first ID in the list loads first. Clients don't choose. When a player joins, the server sends its list and the player's game loads the mods in that same order.

Only the order of mods that register something matters here. When the game starts, it walks the list front to back. For each mod with a PrimalGameData:

  1. The first one becomes the game's PrimalGameData. Every later mod's game data is merged into it.
  2. Each mod's Mod Data Asset is merged in turn. Lists add up; other fields follow the rules below.

Nothing in the game sorts the list. If an owner moves your mod from first to tenth, the result can change.

What the order decides

Most of what a mod registers stacks: both mods' entries apply, in any order. That's the point of the Mod Data Asset. But a few things have a single winner.

Who wins What What it means for you
Everyone (stacks) Every list: engrams, items, structures, default buffs, spawn additions, singletons Order doesn't matter. Use these whenever you can.
The first mod Remaps of the same vanilla class Two mods remapping raw meat: the first one's meat spawns.
The first mod Some other remaps, which only work at all from the first mod If your remap only works when you're first, that's why.
The first mod The mod icon on menus, and the custom loading screen Only one mod gets to show them.
The first mod Baby setups for a creature tag A later mod can't replace one.
The last mod Default game mode and photo mode class Two total conversions can't run together.
The last mod Named map entries with the same key: explorer notes, milestone trees The later mod's entry replaces the earlier one.
Anyone, for the whole server On/off switches like Prevent Photo Mode One mod turning it on turns it on for every mod.

Every Mod Data Asset field gives the rule for each field.

Remaps don't undo themselves

A remap swaps which class the game creates. It doesn't convert things that already exist. If a server ran another mod's remap for a week, players hold that mod's meat. Moving your mod first now only changes the meat created from then on.

The same goes for removing a remap. The swapped things stay what they were, until they're used up or replaced.

When stacking fails, it may be a bug

Two lists have failed to stack before, and Wildcard fixed both:

  • Default buffs only applied from the first mod that added one to a class. Fixed in version 36, in March 2024.
  • Structures added to the same crafting station only showed from the first mod. Fixed in version 59, in July 2024.

Both were found the same way: two small mods, swapped order, and a clear report. If a list stops stacking, do that and post it.

Names that must be unique

Every class in Unreal has a full path, like /MyMod/Items/PrimalItem_MyPick.PrimalItem_MyPick_C. Two mods can't have the same path, because each mod has its own root folder.

Many places in ARK don't use the full path, though. They use a short name: just PrimalItem_MyPick_C, or a name you typed into a field. Those can clash.

Your mod's root folder

The root folder is the start of every path in your mod. Two mods with the same root folder can't run on one server. Only the first in load order loads. Pick a folder name nobody else will pick, before you make anything else. Your first mod covers naming it.

Class short names

Server owners name classes by short name in their ini settings: crafting cost overrides, stack sizes, crate contents, creature replacements, damage multipliers, taming bans. So do some Mod Data Asset fields that take a class as text, like container additions by name.

If two mods each have a PrimalItem_Pick_Better_C, a line naming it can't tell them apart. Which one it finds isn't something to rely on.

Vanilla shows how easy this is. The DevKit has 28 short names used by two or three classes in different folders. Some examples:

  • Buff_Frozen_C is in three places: Crystal Isles, Valguero and the main game.
  • PrimalItemResource_CommonMushroom_C is in two: Aberration and the base game.
  • IceGolem_Character_BP_C and ChalkGolem_Character_BP_C each exist twice, once for Valguero.

So give every class a short name that carries your mod's mark. I follow the convention in Wildcard's own mods:

  • A new asset gets a short mod infix: StructureSkinBP_MM_ArmChair or M_MM_Laser for a mod called My Mod.
  • A child of a vanilla class gets the vanilla name plus a mod suffix: PrimalItem_WeaponBow_SOTF, from Wildcard's Survival of the Fittest mod.

Code that finds classes by name has the same problem. If you search the asset registry for a class name, check the path too. Vanilla paths start with /Game/ or a map's folder, and mod paths start with the mod's folder.

Your PrimalGameData and Mod Data Asset

Name them after your mod: PrimalGameData_BP_MyMod and ModDataAsset_MyMod. They're in your own folder, so a shared name isn't a real clash. But plenty of mods still ship PrimalGameData_BP_BlankMod, and in a log full of mods you can't tell which one is yours.

Modders disagree on whether other names cause trouble. One early tip said the name must start with PrimalGameData_BP_; others report odd names working. Starting with PrimalGameData_BP_ costs nothing, so I do.

Names you type into fields

These are matched by the text you type, across every mod on the server:

Name Where What a clash does
Color names Mod Data Asset color definitions The first mod's color stays; a later one with the same name is dropped, unless it has override priority
Creature name tags Baby setups The first mod's setup wins
Explorer note names Named explorer note entries The later mod's note replaces the earlier one
Milestone tree keys Additional milestone trees The later mod's tree replaces the earlier one, even a vanilla tree
Skill row names Skill data tables The vanilla row is found first
Custom item data names SetCustomItemData on items Two mods read and overwrite each other's data
Admin command words cheat ScriptCommand <word> Both mods answer the same command
Multi-use index numbers Entries you add to a radial menu One mod's entry replaces the other's (multi-use)

The fix for the names is the same for all of them: start every name with your mod's prefix. MyMod_Ember, not Ember. For multi-use, pick a less obvious number.

Color IDs have a related trap. A mod color's number depends on which mods loaded before it. Change the mod list and the numbers move. Store colors by name.

Hooks with one winner

A few hooks only ever call one handler. Two mods using them collide without an error.

The clearest is the item drop hook that 5.8.1 added to buffs. It replaces "Drop All" for the player who has the buff. The game asks the player's buffs in order and gives the drop to the first one that opted in. If two mods each give a player such a buff, the second mod's handler never runs.

If you use a hook like this:

  • Opt in only while your feature is active. Add the buff when it starts and remove it when it ends.
  • Handle only what's yours. For anything else, do the normal thing.
  • Say so on your mod page. Server owners can then spot the clash themselves.

Being a good neighbor

What I check before I publish:

  1. Additions, not replacements. Prefer the Additional… lists to remaps and CDO edits. They stack.
  2. No server-wide switches in a general mod. Prevent Photo Mode, Force Server Use Dino List and PhysX substeps change every mod on the server, and nobody else can undo them.
  3. No default game mode unless it's a total conversion.
  4. Every name prefixed: classes, colors, keys, item data names, admin words.
  5. The mod page lists what you remap and which single-winner hooks you use.
  6. No dependence on being first. If your mod only works first, say so plainly, and expect owners to move it.

Testing with other mods

A two-mod test catches most of this. You need a local dedicated server (testing) and one other mod that touches the same thing as yours.

  1. Load your mod first and the other second. Check both features work.
  2. Swap the order and check again.
  3. Start the server with -log and read the log. Each mod's PrimalGameData is listed as it's used or merged. If yours isn't there, it didn't register.
  4. Write down the order and what you saw. If something only works in one order, it's a "first wins" or "last wins" field, or a bug to report.

Common mistakes

My remap only works when my mod is first

Another mod remaps the same class, or this remap only works from the first mod. Use an addition or a default buff instead if you can. If not, say "load first" on your mod page.

My mod's structures don't show up next to another mod's

Two mods adding to the same crafting station once failed to stack. It was fixed in version 59. If it happens again, test with two small mods in both orders and report it.

A server owner's ini line hits the wrong item

Two mods share a short class name. Rename yours with your mod's mark, and tell owners the new name.

Players' colors changed after a mod was added

Color IDs follow load order. Anything that stored a color by number now points at a different color. Store colors by name.

My game mode doesn't run on a server with another big mod

Only the last mod's default game mode runs. Two total conversions can't share a server.

My mod stopped working after the owner reordered mods

Something in your mod depends on order: a remap, a single-winner hook, or a key another mod also uses. Run the two-mod test in both orders to find it.

Go deeper

Sources

  • The compiled game module in the DevKit, read with the editor closed: the game walking the mod list front to back with no sorting, the first mod's PrimalGameData becoming the game's, later ones merged, only mods with a PrimalGameData taking part, clients using the server's list order, and the drop hook picking the first matching buff.
  • The DevKit's files, read on 5.8.1: the 28 vanilla short names used more than once, and Wildcard's naming convention in its own mods.
  • My notes from building mods: the merge rule for each field, color IDs moving with load order, and the prefixes for item data and admin commands.
  • The ARK Wiki (ark.wiki.gg, server configuration page): the old GameModIds option and -mods replacing it on ASA.
  • Discord threads (open for server members):
    • the first remap of a class winning, and remapped items staying remapped (2023-11, 2023-11);
    • some remaps only working from the first mod (2023-11);
    • load order following the server's settings, and the loading screen going to the first mod (2025-10);
    • default buffs not stacking, fixed in version 36 (2024-03);
    • structures added to the same station not stacking, fixed in version 59 (2024-07);
    • PrimalGameData names, for and against a required prefix (2023-11, 2024-12);
    • unique PrimalGameData names per mod, and checking the log for the merge (2026-03);
    • checking the path when finding classes by name in the asset registry (2024-03).

Community knowledge from the ARK Modding Community Discord (discussions from November 2023 to March 2026), found with Overseer.

Where this page's information comes from

Applies to: ASA DevKit as of November 2026 (UE 5.8.1)

the compiled game module in the DevKit, the DevKit's own files, my notes from building mods, and the community Discord (see Sources)

Esc

↑ ↓ move↵ openCtrl ↵ new tab