Coming from ASE: what changed for modders, and moving an old mod across
12 min readASA DevKit as of November 2026 (UE 5.8.1), compared with the ASE ModKit (UE4)
If you modded ARK: Survival Evolved, most of what you know still works. You still make children of vanilla classes, register them through your game data, and build logic in Blueprints. What changed is the tool around all of that: a new engine, a new mod platform, a new way to register content, and no local cook to upload.
This page lists what changed, then walks you through moving an old mod into the ASA DevKit and fixing what breaks.
- You'll learn: which ASE habits still hold, which don't, the three ways to bring an ASE mod across, and the fixes nearly every ported mod needs
- Time: 15 minutes to read; porting takes an evening for a small mod and much longer for a big one
- Level: you've made an ASE mod before
- You'll need: the ASA DevKit (install) and a backup of your ASE mod's folder
What still works
The ideas carry over. Your ASE skills aren't wasted.
- The core method still holds: make a child of the vanilla asset and change only what you need.
- Blueprints: The graph editor, events, casts and replication work the way they did. Most of your node knowledge transfers.
- The game's classes: Items, structures, buffs, creatures and multi-use menus keep most of their names and settings. A few gained settings, and a few lost the ones they no longer use.
- Most of ZenRowe's Wildcard Workshop series still applies. It was made in the ASE ModKit, and modders still point newcomers at it. Skip part 1 (setup) and part 7 (cooking and uploading); both describe the old tool. The rest teaches ideas that still apply. Check each class or node name in the DevKit before you trust it.
What changed
| Area | ASE | ASA |
|---|---|---|
| The tool | ARK ModKit, Unreal Engine 4, on the Epic Games launcher (mods went to the Steam Workshop) | ARK DevKit, Unreal Engine 5 (5.8.1 as I write), on the Epic Games launcher |
| Where a mod lives | a folder under the ModKit's Content/Mods |
a mod plugin, made from the UGC menu and shown under Plugins in the Content Browser |
| Registering content | your PrimalGameData (PGD) holds everything | a PGD that's a child of PrimalGameDataARKNX_BP, plus a Mod Data Asset that lists what to add (registration) |
| Cooking | you cooked locally, then uploaded | you upload source with UGC → Share Mod; CurseForge cooks it in the cloud (publishing) |
| Platform | Steam Workshop | CurseForge, for PC and, if you choose Cross-Platform, Xbox and PlayStation |
| Testing a build | the local test ID trick | -dev after the mod ID on a server, or My Mods in the game (the -dev method) |
| Maps | World Composition; map extensions | World Partition only; no map extensions (maps) |
| Power | cables and junctions | wireless power by inventory tags (powered structures) |
| Singletons | any Actor child | must be a SaveGameActor child (singletons) |
| Particles | Cascade | Niagara; old Cascade systems can fail the cook |
| Female characters | a separate female skeleton | one shared skeleton and a merged female mesh |
| Writing your own files | not supported; save through the game's save systems |
Two of those catch almost every returning modder. The first is the PGD parent; it gets its own section below. The second is the cloud cook: what you upload is source, and CurseForge's cooker decides whether it builds. Read the cook log on every upload, even a successful one.
Three ways to bring a mod across
Before any of them, copy your whole ASE Mods folder somewhere safe. Porting can corrupt files, and the DevKit
install is big enough that you may need to remove the ModKit to make room.
| Route | Best for | What can go wrong |
|---|---|---|
| Legacy Import | most mods; it keeps references intact | it can crash on classes that no longer exist |
| Manual import | mods Legacy Import can't swallow | slower; you find the broken files one by one |
| Rebuild | small mods, or old mods you'd write differently today | it takes time, but you finish with a clean mod |
Wildcard's own advice is that no one route fits every mod. If one fails, try the next.
Legacy Import
Open UGC → Import Legacy Mod in the ASA DevKit. It asks whether the mod is a map.
Let it finish. It puts the mod at its old ASE path, under the old
Modsfolder, not in a new plugin. That's on purpose: every reference inside the mod still points at the old path, so nothing breaks yet.Make a new mod with UGC → Create Mod, from the blank template. This gives you a fresh PGD and Mod Data Asset with the right parents.
Move your assets into the new mod's folder inside the editor. Drag them in the Content Browser and pick Move. The editor rewrites references as it goes.
Show me how
- Move, never copy. Copying keeps every reference pointing at the old folder. The mod tests fine in the kit, because the old folder is still there, and then breaks once it's cooked.
- Never copy the folder in Windows Explorer either. Same problem.
- For a big mod, move it in batches. One modder ran out of video memory moving a 10 GB mod in one go.
- Close any Blueprint you're moving into before you move. Moving over a loaded Blueprint can crash the kit.
Bring your settings across. Copy your mod name, description and registrations into the new Mod Data Asset. Or reparent your old PGD instead (next section) and keep using it.
Delete the empty old folder only after the new one loads, compiles and tests cleanly.
Legacy Import is only for ASE mods. To restore your own ASA mod after a reinstall, copy its folder back into
ARKDevkit\Projects\ShooterGame\Mods\. Legacy-importing an ASA mod lost its engram connections for one modder.
Manual import
Use this when Legacy Import crashes.
- Copy your ASE mod folder into the DevKit at the same relative path it had in the ModKit, with the editor closed. Wildcard's page words this step loosely; the point is that references keep resolving.
- Open the DevKit and make a new blank mod from UGC → Create Mod.
- Open your old files one at a time, starting with the base classes. A file that crashes the editor almost always has a parent class that no longer exists.
- Once a file opens cleanly, move it into the new mod's folder.
- Keep the ASE ModKit open next to it if you can. Where something differs, compare the two.
Two shortcuts help:
- Meshes: export them to FBX from the ModKit and import them fresh.
- Settings and graphs: many assets can be copied as text in the ModKit editor and pasted into the DevKit, which keeps their settings. Graph nodes paste the same way.
Rebuild
For a mod with a handful of assets, rebuilding is often faster than fixing an import. You end up with ASA-native files and none of the leftovers. Follow the first mod page, then the how-to page for each asset.
Fix the PGD parent first
ASE PGDs are children of PrimalGameData_BP. That's the wrong parent for ASA. Wildcard's migration page says to
reparent every one of them to PrimalGameDataARKNX_BP.
- Open your PGD.
- File → Reparent Blueprint, then pick
PrimalGameDataARKNX_BP. - Compile and save.
PrimalGameDataARKNX_BP is a child of PrimalGameData_BP, and it carries ASA's version of the game's data. A PGD
on the old parent misses that. One modder with the wrong parent saw the player level cap
drop to 60 in single player and 75 on a dedicated server.
A fresh PGD from UGC → Create Mod already has the right parent, which is why many modders make a new mod and move their assets into it.
Then move your registrations to the Mod Data Asset. ASE mods listed their engrams and structures by editing the PGD's master lists. On ASA you add them through the MDA's Additional lists instead, which stacks cleanly with other mods. Registration covers every list.
What breaks after an import
Work through these in order. Each one shows up in the compiler results or the log.
- "Parent: None". A Blueprint opens but says it has no parent, and its variables are gone. Its ASE parent no longer exists, or came through broken. Reparent it to the closest vanilla class with File → Reparent Blueprint. Early imports hit this with a few vanilla structure parents too; the fix was the same.
- Stale pins. UE5 doesn't drop pins that no longer exist on a node. It keeps them and reports "In use pin ... no longer exists on node". Right-click the node and refresh it, or break the link and reconnect.
- Properties you can't set any more. "... is not blueprint writable" means a setting you used to set at runtime is now read-only. Find another route, usually a function on the class, or set it in the defaults.
- Type changes. In UE5, Get Game Mode returns the base game mode type. A node that wanted ARK's game mode
won't connect. Cast it to
PrimalGameModefirst. - Macro and function libraries. Big ASE libraries often import with broken macros. A macro library's parent should be Object. If a macro still won't compile, rebuild it from standard nodes.
- Singletons that won't register. Server Extra World Singleton Actor Classes only accepts
SaveGameActorchildren now. Reparent your old Actor singleton. - First-person rigs. Ported weapons can warn that the default rig has bones yours lacks, and offer to add them. The player skeleton changed, so first-person animations may need redoing.
- Cascade particles. Some old Cascade modules don't cook in this engine (Legacy particles). Rebuild the effect in Niagara, or start from a vanilla Niagara system that looks close.
Particles converted to Niagara can look fine in the kit and wrong in the game. A material used by Niagara needs its Niagara usage flag. The kit sets that flag on the fly when you preview, so you never see the problem. On a vanilla material it can't be saved, so the game shows the default material. Make your own material for the effect.
Then test in this order: open every Blueprint, compile all, play in the editor, run a local cook, and finish with a
CurseForge build on a server with -dev (testing). A port that's fine in the kit can still fail the
cloud cook, so don't skip the last step.
Maps
ASE maps don't come across one to one. ASA builds maps with World Partition and doesn't support World Composition at all. An ASE map may open in the DevKit, but its sublevel layout won't load.
What does come across is the landscape:
- Export the heightmap from the ASE ModKit.
- In the DevKit, make a new map mod from the empty map template, then File → New Level → Open World.
- Save the level into your mod plugin with File → Save Current Level As. Don't move it afterwards; a World Partition level keeps hidden files next to it that the move won't take along.
- Import the heightmap. Set the landscape scale to 1, 1, 1 before you import, then scale and center it afterwards. Modders found that importing at a custom scale tiles the landscape proxies wrongly.
Everything else (foliage, actors, lighting, weather) is rebuilt. The map page covers that, along with the replacement for map extensions: a level your mod loads at runtime.
Armor and the female body
ASA game update 36.4 changed the female character. Male and female now share one skeleton, and the female body is a merged mesh. Armor made for the old female body doesn't fit any more, and the old female skeleton is missing parts.
Wildcard published a Blender converter for it. You import the armor FBX into their converter file, run its script on the mesh, export a new FBX, and reimport it over your armor in the DevKit. The result roughly fits the new proportions; expect to tidy it by hand. The steps are on Wildcard's legacy female armor page.
Body shapes changed too, for both bodies. ASA's character sliders don't scale bones; the player's material reshapes the body, reading a second UV layout and a delta map texture. An ASE armor mesh has neither, so it ignores the sliders and the body pokes through on bigger survivors. The armor page covers the fix, in step 5, and the rest of making armor.
Publishing is different
- You upload source, not a cooked mod. CurseForge cooks every upload. Read the cook log zip each time.
- A tiny upload means nothing was cooked. A 12 KB upload, from a mod still in the old
Modsfolder, got rejected. Move the mod into its plugin first. - Cross-platform is a choice per upload. Cross-Platform builds also cook for Xbox and PlayStation and go through manual review, which takes hours or days. PC-Only builds publish straight away once your project has passed its first review. Wildcard recommends that a mod, once cross-platform, stays cross-platform.
- Size matters more: CurseForge rejects a cross-platform cook over 5 GB, the consoles' limit. PC-only uploads allow 15 GB. Check CurseForge's current numbers before you port a big mod.
- No file writing: Wildcard doesn't support mods that create files outside the game's save systems, because of the console rules. Port any "save to file" logic to save data.
Publishing covers the whole flow.
Common mistakes
- Copying instead of moving: References keep pointing at the old folder. The kit hides it; the cooked mod breaks.
- Leaving the PGD on
PrimalGameData_BP: Odd level caps, missing engrams, broken menus. - Editing the PGD's master lists, the ASE way: Use the Mod Data Asset's Additional lists.
- Testing only in the kit: The cloud cook is stricter. Test the CurseForge build with
-devbefore publishing. - Following ASE setup and cooking videos: Parts 1 and 7 of the Wildcard Workshop series, and any video about the Steam Workshop, describe a tool you no longer have.
- Using the old docs site: ASA's docs are at devkit.studiowildcard.com. The older ARK modding docs site is for ASE.
Check it worked
- Every Blueprint opens, has a parent, and compiles with no errors.
- Your PGD's parent is
PrimalGameDataARKNX_BP, and your content is in the Mod Data Asset. - Nothing in the mod lives under the old
Modspath any more. The Reference Viewer shows no links into it. - A local cook finishes, and the CurseForge cook log has no errors that name your files.
- The CurseForge build, loaded with
-devon a server, behaves the way your ASE mod did.
Go deeper
- How ARK finds your content: the PGD, the Mod Data Asset and every Additional list.
- Testing your mod: local cooks,
-devand My Mods. - Publishing and updating: Share Mod, the cook log and review.
- Inheritance and default objects: what reparenting changes, and why a missing parent breaks a child.
- Load order and name collisions: ported mods often keep ASE-era names that now clash.
- Tutorial videos: which videos are ASE-era, and what still applies from them.
Sources
- CurseForge, read 2026-11-08: uploading a new mod via ARK's DevKit (size limits).
- Wildcard's DevKit docs (devkit.studiowildcard.com, read 2026-11-07): migrating mods from ASE to ASA (Legacy Import, manual import, maps, reparenting the PGD), creating new maps, testing, cooking and publishing and the legacy female armor conversion.
- The DevKit's files, read on 5.8.1: the PGD parent chain.
- My notes from modding both games: what carries over, and the testing order.
- Discord threads (open for server members):
- Legacy Import using the old folder, why copying breaks it, and the PGD parent (2023-11, 2023-11);
- making a new mod and moving assets in batches, or reparenting the PGD (2025-04);
- the wrong PGD parent and the lowered level cap (2026-01);
- Legacy Import being for ASE mods only (2026-02);
- "Parent: None" after import, and casting Get Game Mode (2023-10);
- stale pins on imported nodes (2023-12);
- singletons as
SaveGameActorchildren (2023-11); - World Composition no longer supported, and the heightmap scale trick (2023-10, 2023-10);
- converted particles and the Niagara material flag (2024-05);
- the merged female mesh and shared skeleton (2023-12);
- cross-platform size limits changing over time (2023-12, 2024-05);
- the ASE local test ID, and no ASA equivalent (2024-04);
- no file writing, because of console rules (2026-02);
- the old ASE tutorials, which parts to skip, and the old docs site (2024-10).
Community knowledge from the ARK Modding Community Discord (discussions from October 2023 to February 2026), found with Overseer.
Where this page's information comes from
Applies to: ASA DevKit as of November 2026 (UE 5.8.1), compared with the ASE ModKit (UE4)
Wildcard's DevKit docs, the DevKit's own files, my notes from modding both games, and the community Discord (see Sources)