Modding guide

What modding ARK means

7 min readASA DevKit as of November 2026 (UE 5.8.1); CurseForge's cloud cook as of 2026

Before you install anything, it helps to know what an ARK mod is, where it ends up, and where its limits are. This page is the map. It has no steps, and it takes about ten minutes to read.

  • You'll learn: what a mod is, how it reaches every platform, what it can and can't change, and how mods stack
  • Time: about ten minutes
  • Level: complete beginner
  • You'll need: nothing yet

What a mod is

An ASA mod is a folder of content you make in the ARK DevKit. The DevKit is Studio Wildcard's free version of the Unreal Engine 5 editor, with the whole game's content inside. It's Windows only, and you get it from the Epic Games launcher.

Your mod holds Blueprints, meshes, sounds and data, all in its own folder. Almost every mod is built from children of Wildcard's classes. A new club is a child of the vanilla club, with your changes on top. Two small assets register the mod so the game can find it (How ARK finds your content).

How a mod reaches players

  1. You upload the source, not a finished build. The DevKit's Share Mod window sends CurseForge your mod's uncooked files.
  2. CurseForge cooks it for every platform. Cooking turns editable assets into the files a game loads. The cloud cook builds PC, Xbox and PlayStation 5 versions from that one upload.
  3. You publish it, and it goes through review. After approval it appears in the game's mod list on every platform.
  4. Players get it when they join. A player must have every mod the server runs. The game downloads them as the player joins, so a smaller mod joins faster.

So console players use the same mods as PC players, on the same cross-play servers. You build on a PC; they never need one.

When you upload, you choose Cross-Platform or PC Only. Of 117 mods I checked in the DevKit, 114 chose Cross-Platform. PC Only is for mods that need something consoles lack, and it splits servers: console players can't join a server that runs it.

There are also premium mods: paid mods from studios and selected creators, reviewed by both CurseForge and Wildcard. Everything in this guide works the same for a free mod. README §2 has the history and the numbers.

Publishing and updating walks through every stage, from upload to live.

What a mod can and can't change

A mod adds and changes content: Blueprints, data and assets. It can't touch the game's engine or its C++ code.

A mod can A mod can't
Add creatures, items, weapons, structures, buffs, cosmetics, maps and whole game modes Ship C++ or any native code. Everything in a mod is Blueprint and content
Make children of Wildcard's classes, including the C++ ones at the root Change the C++ classes themselves, or the engine
Override many of the game's built-in events, once their switch is ticked Override functions Wildcard didn't open to Blueprint
Change vanilla classes indirectly: default buffs, edits at server start, remaps Edit Wildcard's assets in place. Changes to /Game stay on your PC and never ship
Read the server's ini settings Ship ini files to players. The upload has no config folder
Run logic on the server, on clients, or both Rely on PC-only features in a Cross-Platform mod

A native class is one written in C++ by Wildcard or Epic. You'll build on them all the time. You just can't change them. Most "can my mod do X?" questions come down to whether X lives in C++ or in Blueprint.

One more thing: everything in your upload is public. Every player downloads it, so a key or a web address in a Blueprint is readable by anyone (lessons §5).

Where your mod's logic runs

Every player has your whole mod. What differs is where its logic runs. Your test in the editor hides this, because the server and your client share one process there.

Runs on What lives there What it means for you
The server only The game mode, your mod's singletons, the ini settings Clients can't read these directly. Values players see must be sent to them
Each client The HUD, menus, sounds, effects One player's screen. Nothing here should decide the game
Both Creatures, structures, items and buffs, as server and client copies The server's copy counts. Clients get what the server sends

A singleton is one actor your mod spawns once per server. It runs logic for the whole world. Many "server-side" mods are mostly a singleton: they change rules, rates or vanilla values and add little you can see. Players still download them.

Modders report that console players in single player can't edit ini files at all. So if your mod has settings, think about an in-game way to change them too. Global logic and ini settings covers both.

Works in PIE, not on a server explains the split in depth. You don't need it for your first mod.

Kinds of mods

Kind What it does Where to start
Content mod Adds items, creatures, structures or weapons beside vanilla. Most mods are this. Your first mod
Change to vanilla Rebalances or reworks what Wildcard made, without replacing it. Changing vanilla content
Cosmetic Skins and outfits players apply over their gear. A cosmetic or skin
Map A new world, built from Wildcard's sample island. A map or a sublevel mod
Server logic Rules, events and settings run by a singleton. Global logic
Total conversion A different game on ARK's engine: its own login, spawning, camera and rules. tutorials §2

Wildcard's own Survival of the Fittest is a total conversion. It ships as two mods, the map and the game logic, so either can update alone. That split is a good habit for any big project.

How mods load and stack

A server can run many mods at once. The game merges every mod's registration into one set, in load order: the order of the server's mod list.

  • Additions from every mod stack. Engrams, structures, spawns and default buffs are all added together. That's why the "Additional…" fields are the safe way to add things.
  • Single values go to one mod. Where two mods set the same keyed value, the mod merged last wins. I haven't confirmed that "last" always means last in the list.
  • Switches go on for everyone. If any mod turns a server-wide switch on, it's on for the whole server.
  • Two mods that replace the same vanilla class clash, and only one wins. Modders report some replacements only work from the first mod in the list.
  • Names must be unique. Two mods with the same folder name can't run together; only the first loads.

So when two mods change the same thing, the one that adds wins over the one that replaces. That shapes how I build: add where you can, and replace only when nothing else works. The full rules are in How mods stack.

What you need to start

  • A Windows PC with plenty of RAM: 64 GB is comfortable, 32 GB workable and 16 GB painful. Plan for an SSD with about 2 TB free. Installing the DevKit has the details.
  • The DevKit, and accounts: You need an Epic Games account for the kit and a CurseForge account to publish. You also need ASA on PC to try your mod in the real game.
  • Time: The download takes hours, and the first launch is long. Your first mod takes an afternoon.
  • No C++: You don't need to program. Blueprints are logic drawn as nodes and wires, and many mods need very little of it.

The skill that matters most comes early in this guide. Find a vanilla asset that already does what you want, make a child of it, and compare.

Where to go next

Go through the learning path in order:

  1. What modding ARK means: this page.
  2. Installing and launching the DevKit
  3. Finding your way around the editor
  4. Unreal words you'll meet
  5. The core method: start from a vanilla asset
  6. Your first mod, start to CurseForge
  7. How ARK finds your content
  8. Testing your mod
  9. Publishing and updating

Then pick something to make from Start here. When you get stuck, the symptom index is the fastest way in.

Watch

Sources

  • Wildcard, Overwolf and Microsoft on cross-platform modding: the Microsoft Game Dev article (November 2023) for the cloud cook to PC, Xbox and PS5 from one upload; the Game Developer press release (May 2024) and CurseForge support for premium mods and their review. Summarized in README §2.
  • My DevKit notes, checked against the 5.8.1 kit: the upload's contents (no config folder, no code modules), Cross-Platform against PC Only and the 114 of 117 figure, players needing every mod a server runs, what mods can and can't do (README §4), the merge rules read from the game's compiled merge function, Survival of the Fittest as two mods, and uploads being public (lessons §1 and §5).
  • Jeremy Stieglitz's official overview (February 2024) for the Simple Game Framework and total conversions (tutorials §2).
  • My beginner guide video, 7TwjI7TCE_w (September 2025, UE 5.5 DevKit), for the PC figures.
  • What modders report, from the ARK Modding Community Discord: console single player can't edit ini files (2024); some replacements working only from the first mod in load order, and load order following the server's mod list (2024).

Community knowledge from the ARK Modding Community Discord (discussions from 2024), found with Overseer.

Where this page's information comes from

Applies to: ASA DevKit as of November 2026 (UE 5.8.1); CurseForge's cloud cook as of 2026

Wildcard's and CurseForge's own announcements, my DevKit notes and my beginner guide video (see Sources)

Esc

↑ ↓ move↵ openCtrl ↵ new tab