Modding guide

Start here

7 min readASA DevKit as of November 2026 (UE 5.8.1); ASE where noted

This is my guide to making mods for ARK: Survival Ascended with the ARK DevKit, Studio Wildcard's free Unreal Engine editor on the Epic Games launcher. New to modding? Start with the learning path below. Something broken? Go to Stuck?.

Start with these

What do you want to make?

Pick the closest thing. Each card opens its how-to page.

If yours isn't written yet, the core method still works. Find a vanilla asset that already does what you want, make a child of it (not a copy), and compare.

Items and gear

Structures

Creatures

World and loot

Logic and systems

Your own assets

Looking up a vanilla class name or value? The database has every creature, item and engram the DevKit ships: /ark/browse/creatures, /ark/browse/items.

Your first mod: the learning path

If this is your first mod, go through these in order. You don't need to know Unreal: every term is explained the first time a page uses it. Every step has its own page. If you'd rather watch first, my beginner guide video walks through the whole path: How to Make an ARK ASA Mod (Complete Beginner Guide). It's on my channel, Hypernatrema Mods, and runs 47 minutes.

  1. What modding ARK means: what a mod can change, and how mods reach every platform.
  2. Installing and launching the DevKit: the download, the first launch, and keeping it fast.
  3. Finding your way around the editor: the Content Browser, the Details panel, and saving.
  4. Unreal words you'll meet: Blueprint, class, child, class default object, data asset, component, cook, PIE and more.
  5. The core method: start from a vanilla asset, make a child, compare. Your first mod uses it on a Wooden Club.
  6. Your first mod, start to CurseForge: the Create Mod wizard, a first item, testing and uploading.
  7. How ARK finds your content: PrimalGameData and the Mod Data Asset. Read it before anything in part 2. It fixes "it doesn't show up in game". When you need a field it doesn't cover, every Mod Data Asset field lists them all and says how each stacks with other mods.
  8. Testing your mod: PIE, then a local dedicated server.
  9. Publishing and updating: CurseForge, updates, and living with ARK and DevKit updates.

Then pick something from the list above.

Understand it: for when it works and you want to know why

These go deeper than the how-to pages. Read them once your first mods work.

Stuck? Start here

The DevKit rarely shows a clear error. The answer is almost always in a log, and these pages show you where.

Before you ask for help

The community Discord is generous with help. People answer faster when your question already has what they'd ask for. Bring these.

1. The right log

Problem File
Editor or PIE <DevKit>\Projects\ShooterGame\Saved\Logs\ShooterGame.log is the current session. Older ones are ShooterGame-backup-<date>.log.
Editor crash the newest <date>.crashstack in that same folder, and the ShooterGame.log copy inside the newest <DevKit>\Projects\ShooterGame\Saved\Crashes\UECC-… folder
Local cook <DevKit>\Engine\Programs\AutomationTool\Saved\Cook-<date>_Worker<N>.txt
CurseForge cook Cook-<date>.txt from the build log zip CurseForge gives you
Dedicated server <Server>\ShooterGame\Saved\Logs\ShooterGame.log, plus the .crashstack if it crashed
Game client crash the .crashstack in <Game>\ShooterGame\Saved\Logs\. Start the game with -log if you need a full log.

Don't paste the whole file into a chat. Find the first error that names one of your own files. Post that line with about twenty lines above it, and attach the full log as a text file if someone asks.

2. Redact it first

Logs carry more than you'd think.

  • A server log prints its whole command line. That includes the admin password and the Sentry and CurseForge keys, in plain text. Replace them before posting.
  • Logs also hold your PC's name, your Windows user name and IP addresses. Swap those for placeholders like <PC> and <user>.
  • Don't post your mod's secrets either. A webhook URL or key in a Blueprint is public the moment you upload. More in lessons §5.

3. What to say

  • What you're making, in one sentence, and the class you started from.
  • Your DevKit version, shown top right of the editor window.
  • Where it fails: PIE (which net mode), single player, your own dedicated server, or a hosted one.
  • What you expected, and what happened instead.
  • The log lines from step 1, and a screenshot of the Blueprint graph if it's logic.
  • What you've already tried.

Search first, too. Most questions have been answered before, and the Discord's archive is searchable through Overseer.

Credits

Every page says which DevKit version it was checked against. Where a fact comes only from what modders report, the page says so in plain words.

This guide stands on other people's work:

  • The ARK Modding Community Discord, where most of what modders know about the ASA DevKit was worked out in public. Overseer makes that archive searchable and kindly allowed guides like this one to draw on it. Discord knowledge here is paraphrased, credited by month in each page's Sources, and checked in the DevKit where I could.
  • Wildcard Workshop, ZenRowe's official series for the ASE ModKit (#1: Getting Started). It's from 2018, and the basics it teaches still hold: replication, config options, class default objects and SaveGame.
  • Studio Wildcard's DevKit documentation and Jeremy Stieglitz's GameFramework and Custom Cosmetics overview.
  • The tutorial creators whose videos the guide links with timestamps: SlayerXtreme, Quellcrest, Mist3r Trixt3r, WM Plays, ButtMan, Temptress Lagoon and Exilog.
  • ark.wiki.gg for reference (CC BY-NC-SA 4.0).
  • The server-log redaction advice comes from my own server logs (checked November 2026).

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

Where this page's information comes from

Applies to: ASA DevKit as of November 2026 (UE 5.8.1); ASE where noted

my own logs and the community Discord (see Credits below)

Look something up in creatures

1,551 rows, each with its own page. Search by name or any detail, or start from a category.

Browse all creatures

Look something up in items

3,192 rows, each with its own page. Search by name or any detail, or start from a category.

Browse all items

Esc

↑ ↓ move↵ openCtrl ↵ new tab