Modding guide

Your first mod, start to CurseForge

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

A real mod on CurseForge, start to finish: a stronger Wooden Club with its own name and engram. You'll test it in the editor and on a server, cook it for every platform and publish it. The change is tiny on purpose. The first time through, the hard part isn't the club; it's the path around it.

This page follows my beginner guide video, so each step has a timestamped "Watch" link. If you only want the steps, read the numbered list and skip the rest.

  • You'll make: a Wooden Club that hits twice as hard, with its own name and engram, published on CurseForge
  • Time: an afternoon, plus the DevKit download and a cloud cook of 30 minutes to several hours
  • Level: complete beginner
  • You'll need: a Windows PC, an Epic Games account, a CurseForge account and ASA on PC

Give the PC as much RAM as you can. 64 GB is comfortable, 32 GB workable and 16 GB painful. You'll also want a fast SSD with about 1 TB free for the DevKit. Those are my video's figures; there's no official number.

The DevKit is free on the Epic store. You'll need ASA on PC to try the mod in the real game.

The process

  1. Install the DevKit from the Epic Games launcher. Pick ARK DevKit on the normal branch, not the beta.

    Show me how
    • The DevKit carries the whole game's content, so the download is huge.
    • Pick the non-beta branch. The upload window refuses to upload from a DevKit newer than CurseForge's cooker (README §1).
    • Keep it updated through the launcher. Modders report an out-of-date kit as one cause of an upload window stuck on "checking version of cooking tools".
    • Watch: 1:44.
  2. Launch it with RunEditorSDK.bat. It's in the DevKit folder. Use it instead of the launcher, and let the first launch finish.

    Show me how
    • The launcher sometimes still thinks the kit is running after a crash, and won't start it again. The batch file doesn't care.
    • The first launch compiles and loads for a long time. Wait until the content browser has finished loading the asset tree before you click around.
    • Memory use creeps up through a session. Save often (Ctrl+Shift+S saves all) and restart the kit before it reaches your RAM limit.
    • Busy or crashed? Right-click the DevKit's taskbar entry. If the little Restore/Move/Size menu appears, it's busy, not crashed. Use the wait to note which assets have the unsaved-asterisk.
    • Watch: 3:28, 11:50.
  3. Create the mod with UGC → Create Mod → Blank Mod. Pick a name you'll never need to change.

    Show me how
    • UGC is in the top menu bar. The wizard offers templates: blank, empty, creature, flyer, default buff, outfit, structure and ranged weapon.
    • I always pick Blank Mod. The others are worth opening in a throwaway mod to see how things are built. In a real mod you spend more time deleting from them than you save.
    • Name becomes your mod's root folder. The mod lives in <DevKit>\Projects\ShooterGame\Mods\<YourMod>\, and its assets load from /<YourMod>/ (lessons §1).
    • Use letters, numbers and underscores only. No spaces, dots, dashes or brackets. A dot or dash in a package name is fatal at PIE start, and the cook rejects invalid characters.
    • The name can't be changed later. The display name on CurseForge can; this can't. To "rename", you make a new mod and move your assets into it.
    • Make it unique. Two mods with the same root folder can't run on one server; only the first in load order works. Load order and name collisions covers the other names to keep unique.
    • Author, description, URL and "is beta version" don't matter. Leave them blank.
    • Before Create Mod, click the Blank Mod template once more. An older bug made an empty folder if you didn't. It may be fixed by now, but the click costs nothing. Creation takes 30 seconds to 3 minutes.
    • Watch: 8:10.
  4. Open your test map and fix the template's leftovers. The wizard made four assets, and two need a look.

    Show me how

    The Blank template creates four files:

    File What it is What to do
    <YourMod> (a level) An empty level Delete it unless you're making a map
    TestMapArea_<YourMod> Your test map, with your PGD already set in World Settings Double-click it now; use it for every test
    PrimalGameData_BP_<YourMod> (blue) The PrimalGameData: tells ARK your mod exists Set Mod Name; leave the rest
    ModDataAsset_<YourMod> (pink) The Mod Data Asset: where you register content You'll use it in step 6
    • Always work from your own test map. It's yours to change, and it keeps your PGD set across DevKit updates.
    • Every template sets Mod Name to cfeditor in both the PGD and the MDA. Change it to your mod's name (lessons §1).
    • Keep the PGD's name starting with PrimalGameData_BP_. Modders saw PGDs with other names fail to load live. Keep one PGD per mod.
    • I add a short mod tag to the end of every asset name, a suffix like _ABC, so I can see at a glance which assets are mine. The video shows a batch rename.
    • Right-click the PGD → Reference Viewer. The MDA should hang off it. That proves the pair is linked without opening the slow PGD.
    • How registration works in detail: How ARK finds your content.
    • Watch: 12:25, 15:09.
  5. Make a child of the vanilla club with more damage. Give it its own item and a new engram.

    Show me how

    A child Blueprint is a new class that inherits everything from its parent and stores only what you change. Never copy a vanilla Blueprint and never edit one. Copies freeze on the day you made them, and edits to /Game assets don't ship with your mod at all.

    In a Weapon folder inside your mod, right-click → Blueprint Class → All Classes. Make three classes:

    New class Parent Change
    WeapStoneClub_<Tag>, the weapon you hold WeapStoneClub Melee Damage Amount (MeleeDamageAmount): vanilla is 5; try 10
    PrimalItem_WeaponStoneClub_<Tag>, the inventory item PrimalItem_WeaponStoneClub Descriptive Name Base: "Heavy Club"; Weapon Template: your weapon class
    EngramEntry_HeavyClub_<Tag>, how players unlock it PrimalEngramEntry Blue Print Entry: your item
    • Make the engram a new PrimalEngramEntry, not a child or copy of EngramEntry_StoneClub. The vanilla entries rely on setup you can't see in the kit. Modders who based theirs on a vanilla entry ended up with engrams they could learn but not craft.
    • The engram fields you'll use:
      • Required Character Level: use 1 or more. Level 0 engrams sort to the very bottom of the list.
      • Required Engram Points.
      • Can Be Manually Unlocked: on, or players can't click it.
      • Auto Unlock Engram and Force Is Tek Engram.
      • Engram Requirement Sets: engrams needed first.
      • Extra Engram Description: text shown on the engram, not the item.
    • Name your classes clearly. Server admins use your class names in their configs, and good names save you answering "what's it called?" forever.
    • Watch: 15:58, 17:08.
  6. Register the engram in the Mod Data Asset. Add it to Additional Engram Blueprint Classes, then save all.

    Show me how

    Open ModDataAsset_<YourMod> and search "additional engram". Click + on Additional Engram Blueprint Classes (AdditionalEngramBlueprintClasses) and pick your engram entry.

    The item and weapon need no entry of their own. The engram points at the item and the item at the weapon, so the cook follows the chain. Which array takes which content is the whole subject of How ARK finds your content. Watch: 20:24.

  7. Test in Play In Editor (PIE). Reset the Mod Data Asset cache first, then press Play and craft your club.

    Show me how
    • PIE runs the server and your client inside the editor. It's quick, but it hides network bugs (lessons §3).
    • Reset the cache after any MDA or PGD edit. The DevKit keeps the Mod Data Asset it loaded first in a session. To reset it: World Settings → clear Primal Game Data Override → Play → Esc → put your PGD back → Play.
    • Edits to the club itself don't need the reset. Details: the cache trap.
    • The first PIE of a session is slow and may pop up a list of Blueprint errors. If none of them are in your mod's folder, ignore them and continue.
    • In game, open the engrams and find "Heavy Club" at your level. Unlock it, craft it and hit something.
    • cheat giveitem with your item's path tests the item without the engram. Right-click the item → Copy Reference gets the path.
    • When you save, the dialog may list vanilla assets you opened. Untick everything outside your mod folder.
    • Watch: 21:12, 22:30, 23:40.
  8. Upload with UGC → Share Mod. Sign in with your CurseForge email, pick your mod and choose Cross-Platform. Fill in the page and click Continue.

    Show me how
    • Sign in on curseforge.com first and note which email the account uses.
    • In the DevKit, UGC → Share Mod, and type that email. Then type the code CurseForge emails you. Don't paste it: pasting into that box breaks.
    • Pick your mod from the dropdown. A new one is often at the bottom of the list.
    • Choose Cross-Platform (PC, Xbox and PlayStation) or PC Only. Pick once and stick with it; switching later causes problems for some mods.
    • Fill in the page:
      • a Name, changeable later, any characters;
      • a square image at least 400×400;
      • a category: custom cosmetics have their own, and for the rest it only affects search;
      • a summary, shown when the link is shared;
      • a description of at least 100 characters that really says what the mod does.
    • Click Continue. The window shows the upload. The mod's uncooked source is zipped and sent, and CurseForge cooks it for every platform. That's the "cloud cook" (README §2). A local cook can't be uploaded.
    • Watch: 25:01, 26:10, 27:20.
  9. Wait for the cook and test the cooked build on a server. Then publish it.

    Show me how
    • On curseforge.com, your project's Files tab shows the status of each platform's file: processing → cooking → ready for review. The bell icon notifies you as it changes.
    • A small mod cooks in minutes. Big ones take hours, and maps take longest.
    • Test before you publish. Add your project ID with -dev to a test server's mod list: -mods=<ProjectID>-dev on the command line, or in ActiveMods.
    • Only the project's members and testers can join that server. Add testers under the project's Members.
    • In single player, link your game account to CurseForge. The unpublished mod appears in the game's My Mods tab. Test custom cosmetics this way; a server shows only those its CosmeticWhitelistOverride setting allows.
    • Steps for a local server are under Check it worked.
    • Publish: on a "ready for review" file, the orange publish button sends the build to CurseForge's moderators. The first time, also press Publish project at the top of the project page, once.
    • Moderators check content and platform rules, for example no currency sold for real money. Approval arrives without a notification; the mod simply goes live.
    • Watch: 29:35, 37:33, 38:26, 39:53.
  10. Update by running Share Mod again. Change things in the DevKit, run Share Mod for the same mod and write a changelog. Then wait for the cook and publish the new file.

    Show me how
    • The DevKit remembers which CurseForge project your mod is linked to. Share Mod uploads a new file to the same project. Leave the platform choice as it was.
    • The Release Options let you publish the file automatically once approved, or by hand.
    • Old files can stay; players get the newest published one.
    • After a DevKit or game update, reopen your Blueprints and read the compile warnings. Test again before you upload (lessons §6).

How the pieces connect

This asset Field Points at
TestMapArea_<YourMod> World Settings Primal Game Data Override PrimalGameData_BP_<YourMod>
PrimalGameData_BP_<YourMod> Additional Mod Data Asset ModDataAsset_<YourMod>
ModDataAsset_<YourMod> Additional Engram Blueprint Classes EngramEntry_HeavyClub_<Tag>
EngramEntry_HeavyClub_<Tag> Blue Print Entry PrimalItem_WeaponStoneClub_<Tag>
PrimalItem_WeaponStoneClub_<Tag> Weapon Template WeapStoneClub_<Tag>

The settings that matter

Setting Where it lives Why you'll look for it
Mod name (root folder) The Create Mod wizard Permanent. Letters, numbers and underscores only.
Mod Name PGD and MDA, top of the Details panel Templates leave it as cfeditor.
Primal Game Data Override Test map → World Settings Without it, PIE loads no mod. Clearing it resets the cache.
Melee Damage Amount The weapon class (WeapStoneClub child) Damage lives on the weapon, not the item.
Descriptive Name Base, Weapon Template The item class The name in game, and which weapon it equips.
Required Character Level, Can Be Manually Unlocked The engram entry Level 0 sorts to the bottom. Unticked means nobody can unlock it.
Platform (Cross-Platform / PC Only) Share Mod window Don't switch later.
Release Options Share Mod window Publish automatically or by hand.

Common mistakes

The engram isn't in PIE, but cheat giveitem gives me the club

It's the MDA cache: reset it (step 7). If it's still missing, it's not in Additional Engram Blueprint Classes, or Can Be Manually Unlocked is off.

I edited a vanilla dodo (or club) and nothing changed in the uploaded mod

Mods only ship what's inside their own folder. An edit to a /Game asset stays on your PC. It also quietly changes the base values every later test is built on.

Undo it, and make a child instead. If you need to, verify the DevKit's files in the launcher.

The cook fails or the mod doesn't load, and my mod name has a dash or a dot

Make a new mod with a clean name and move your assets across. More cook problems are in When a cook or upload fails.

The Share Mod code is rejected

Type the code instead of pasting it.

My test server won't start with my unpublished mod

Without -dev, the server tries to download the published version. It finds none and logs LogCFCore: Error: Detected an unavailable mod. Add -dev to the project ID.

My local cook keeps getting replaced on the server

The server's CurseForge client re-downloads a mod whose files differ from CurseForge's. Start the server once so it downloads your mod, stop it, then copy your cooked files over. Modders who replace only the .pak files report the fewest problems.

The upload window sits on "checking version of cooking tools"

Modders fix this by restarting the DevKit and updating it in the Epic launcher. A beta-branch kit is refused outright.

Check it worked

In PIE: the engram shows at its level, the club crafts, and it hits twice as hard as a normal club.

On a local dedicated server, the closest thing to the real game before you publish. There are two ways. Both are modders' practice, not an official procedure.

  1. The CurseForge build with -dev. It's best for the final check, because it's the real cloud cook.
    • Install ARK: Survival Ascended Dedicated Server, a free Steam tool.
    • Start <Server>\ShooterGame\Binaries\Win64\ArkAscendedServer.exe TheIsland_WP?listen?SessionName=ModTest -mods=<ProjectID>-dev -log.
    • Join it from the game as a project member. Testing on a server before you publish has every step, testers included.
  2. A local cook. It's fast for repeated tests, once the project exists on CurseForge.
    • Use the cooking-pot button on the DevKit toolbar, or <DevKit>\ModTools\Scripts\CookMod.bat.
    • The script asks for Windows Client and Windows Server, your mod's folder name and the number of cook workers. Each worker takes several GB of RAM.
    • The result lands in <DevKit>\ModTools\Output\<YourMod>\.
    • Start the server once with your project ID so it downloads the mod, then stop it. Copy the server zip's contents over the downloaded mod.
    • The server log's LoadGameMods lines print the folder. Modders report it as ShooterGame\Mods\83374\<ProjectID>\; 83374 is ARK's game ID on CurseForge.
    • Do the same for your client. Local and cloud cooks can differ, so finish with route 1.

The server log is <Server>\ShooterGame\Saved\Logs\ShooterGame.log. Look for UShooterEngine::LoadGameMods with 1 mods, then Server: "<name>" has successfully started!.

The log prints your admin password, so blank it before you share it. More in Reading ARK's logs and Works in PIE, not on a server.

After publishing: search for your mod in the game's mod browser, as a player would, and install it from there.

Watch

This page follows my beginner guide video, How to Make an ARK ASA Mod (Complete Beginner Guide). It's on my channel, Hypernatrema Mods, recorded on the UE 5.5 DevKit in September 2025. Each step above links its own chapter.

All chapters
  • 0:00 hardware; 1:44 installing; 3:28 launching with the batch file
  • 5:28 the editor layout and the templates; 8:10 Create Mod and naming
  • 12:25 the test map and the four assets
  • 15:58 item, weapon and engram; 20:24 registering
  • 21:12 PIE and the cache reset
  • 25:01 Share Mod; 29:35 the CurseForge dashboard; 37:33 cook statuses and publishing; 39:53 testing with -dev and My Mods; 41:17 community resources

Other creators' first mods, on older DevKits. Both creators copy vanilla assets, which I don't.

Go deeper

Sources

  • My beginner guide video, 7TwjI7TCE_w (Sept 2025, UE 5.5 DevKit; conf. D as a demonstration). The hardware figures are from it (conf. D; there's no official number).
  • DevKit files, checked 2026-11-05 (conf. B):
    • the Create Mod templates in the cfeditor plugin: BlankMod's four assets, ModName = cfeditor, and the test maps' Primal Game Data Override;
    • ModTools\Scripts\CookMod.bat: Windows Client / Windows Server, the mod folder under Projects\ShooterGame\Mods and the /<YourMod>/ root, output under ModTools\Output\<mod>;
    • the defaults of WeapStoneClub (MeleeDamageAmount 5) and PrimalItem_WeaponStoneClub ("Wooden Club", WeaponTemplate), and the field list of PrimalEngramEntry.
  • Real server logs for the LoadGameMods and "successfully started" lines (conf. B).
  • My own notes: lessons and tutorials.
  • Wildcard's DevKit documentation (devkit.studiowildcard.com, linked from the kit) and CurseForge's cross-platform testing article, both pointed to by modders; not re-read for this page.
  • Discord threads (open for server members; conf. D):
    • local cooks on servers and clients (2023-11, 2026-07), including the "unavailable mod" error without -dev and replacing only the .pak files;
    • -dev versus local cooks (2024-04);
    • publishing the project once (2023-10);
    • updating a mod (2025-11);
    • PGD naming (2023-11);
    • local cook versus Share Mod (2024-02);
    • cook troubleshooting (2026-06);
    • an out-of-date kit stuck on "checking version of cooking tools" (2024-02 and 2025-06).
  • Other creators' videos as listed in Watch (conf. D, older DevKits).

Community knowledge from the ARK Modding Community Discord (discussions from October 2023 to July 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 beginner guide video, the DevKit's own files and community knowledge (see Sources)

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

Look something up in engrams

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

Browse all engrams

Esc

↑ ↓ move↵ openCtrl ↵ new tab