DevKit and modding
DevKit and modding
Last researched November 4, 202610 min read
Sources for this page
Applies to: ASA DevKit as of November 2026 (UE 5.8.1); ASE where noted
Epic Games Store: ARK DevKit; ark.wiki.gg: Mod:DevKit; Microsoft Game Dev: cross-platform modding (2023-11-21); Game Developer: premium mods on console (2024-05-22); CurseForge support: buying premium mods on PC; my own modding guides (not published; see where these pages come from); Jeremy Stieglitz's official DevKit and custom cosmetics overview (video, 2024) and creators' DevKit tutorials (transcripts read 2026-11-04; listed in What the video tutorials teach)
Confidence:AOfficial: Studio Wildcard, patch notes or in-game textBRead from the game or DevKit filesCInferred by comparisonDCommunity-measuredEUnverified
Learning to mod? Start with the guide
If you want to make something, start with the modding guide. It walks you through the process step by step, in plain words:
- First steps: what modding ARK means, installing the DevKit, finding your way around the editor and Unreal words you'll meet. Coming from ASE? Read what changed, and moving an old mod across
- The core method: start from a vanilla asset: find the vanilla thing that already does it, make a child, compare. Every how-to page builds on it
- Your first mod, start to CurseForge
- How ARK finds your content: why things "don't show up", and the fix; then every Mod Data Asset field and how each stacks with other mods
- How to make a custom structure
- How to make a custom creature, or a creature from scratch with your own mesh and skeleton
- Works in PIE, not on a server
- When something breaks: the symptom index, reading ARK's logs, reading a crash report and when a cook or upload fails
- More things to make: an item or resource, an engram, a weapon and its ammo, a buff, new creatures in the spawns and loot crates; worlds: a map or a sublevel mod
- Creatures, further: a saddle, taming, breeding and behavior and AI; structures: a crafting station and a multi-use menu and power; gear: armor and cosmetics
- Systems: global logic and ini settings, saving your mod's data and UI
- Testing your mod, testing on a server before you publish and publishing and updating it
- Your own assets: which program does which job, meshes and animations, materials and dye regions and sounds and effects
- Changing vanilla content without replacing it; then, going deeper, inheritance and default objects, sparse class data, load order and name collisions, performance on busy servers and timers, delays and the other nodes that remember
- What each asset offers: the reference behind the how-to pages, from items, weapons, engrams and inventories to structures, buffs, creatures, creature stats, creature AI, game data and world settings and the game mode
The rest of this page is the reference behind the guide.
About this section
What the ASA DevKit is, how a mod gets from it to players on every platform, and what a mod can and cannot do. Much of it comes from my own modding guides, which I keep private. The general lessons from those guides are collected in Modding lessons, and what the public video tutorials teach (Wildcard's official overview and creators' tutorials, with where they differ from my way) is in What the video tutorials teach.
1. The DevKit
What it is: The ARK DevKit is a custom build of the Unreal Engine 5 editor that ships with the game's content, for making ASA mods (conf. A; Epic Games Store, read 2026-11-03). The ASE equivalent was the UE4-based "ARK ModKit", which is a different tool (conf. A; ark.wiki.gg: Mod:DevKit, read 2026-11-03).
How you get it: It is free, Windows only, and distributed through the Epic Games Store and launcher as "ARK DevKit", including for players who own ASA on Steam (conf. A for the store listing; the Steam-owner point is conf. E, from a 2023 Steam forum thread). It is a very large download because it carries the whole game's content (conf. A, store page); I have no current official size figure (gap).
How it updates: The DevKit is updated with the game, through the launcher; when its content is damaged the fix is to re-acquire it through the updater rather than repairing files by hand (conf. C; my own workflow notes). The upload window checks that the cloud cooker matches the DevKit's version and refuses to upload, with a "cooking tools ... have not yet been updated" message, when the DevKit is newer (for example on a beta branch) (conf. B, from the upload window's text; exact behavior untested).
Inside it: The editor's mod tooling is CurseForge's editor plugin (by Overwolf) plus Wildcard's ModTools
scripts: a Create Mod wizard with templates (blank, creature, flyer, buff, outfit, structure, ranged weapon), a
CookMod script and a DuplicateSampleIsland script that is the official way to start a World Partition map
(conf. B; from Wildcard's own mod layout). The ASA mapping tutorials of 2023 to 2025 instead start from an
Empty Open World level and copy The Island's actors by hand (conf. D); I keep the script as the route, since it is
Wildcard's and the hand-built method is probably from before it existed (my inference, conf. E). Their notes on
water, spawns, minimaps and the landscape material still help: What the video tutorials teach §9.
Unreal Engine version history
| When | Engine | Source |
|---|---|---|
| Oct 2023, launch | UE 5.2 | conf. D; PC Gamer describes the 2025 move as 5.2 to 5.5 |
| 5 Jun 2025 (patch 66.0, 10th anniversary) | UE 5.5 | conf. A; wiki patch 66.0 and ARK Status, 2025-06-05 give the live day, as does the release history. First planned for 15 Apr to 15 May, then announced for 2 Jun (RPG Gamers) |
| 2026 (GDC) | UE 5.7 announced as the next step; never shipped | conf. D; 80.lv |
| announced for 30 Sep 2026 | UE 5.8, replacing the 5.7 plan | conf. D; PCGamesN, Gamewave |
| DevKit build of 2026-09-26 | UE 5.5.4 | conf. B; my snapshot of that build |
| DevKit build of 2026-10-08, in use from 2026-10-09 (the beta DevKit for the 5.8 PTR) | UE 5.8.1, CL 830809 | conf. B; same. The guides and the database were checked on this build |
| DevKit update of 5 Nov 2026 (beta DevKit line) | UE 5.8.3 | conf. B; the version my DevKit's engine reports. I haven't re-checked the guides on it yet |
I have not confirmed the live client's and official servers' 5.8 date from patch notes (gap). The 5.5.4 to 5.8.1 move broke two Blueprint overrides and silently dropped five ship-ramming properties; see Modding lessons §6.
2. CurseForge: the mod platform
- One platform for every device: Studio Wildcard, Grove Street Games and Overwolf built ASA modding on CurseForge. Creators upload platform-agnostic source from the DevKit and CurseForge "cloud cooks" it for PC, Xbox and PS5, so one upload reaches every platform and cross-play servers can run mods (conf. A; Microsoft Game Dev, 2023-11-21). That article counted 17 million mod downloads and over 550 PC mods from 300 contributors a month after launch.
- The upload is a zip of the uncooked mod: the
.uplugin, asettings.cfg(UTF-16 JSON withIsCrossPlatformandVersion), the.uasset/.umapcontent and the icon. NoConfig/folder ever ships, so a mod cannot hand players ini files (conf. B). - Cross-Platform or PC Only: The upload window offers the two ("Cross-Platform includes PC"). 114 of 117 mods in my DevKit census chose Cross-Platform. PC Only is for mods that need something consoles lack, and it splits servers (conf. B; same guide §2.3).
- Joining a modded server: Players must have every mod the server runs; the CurseForge integration installs or updates them as the player joins, so smaller mods join faster (conf. B, from the plugin's own documentation).
- Premium mods: Paid mods "between official DLCs and traditional mods", made by studios and selected creators. Nine reached Xbox on 22 May 2024 (PS5 was in certification), priced $2 to $10 with 50% of revenue to the creator (conf. A; Game Developer press release). The first ones launched on PC earlier in 2024, alongside the Love Ascended event (conf. D; press-release headline, date not checked). They are bought in game or through CurseForge, separately per platform (conf. A; CurseForge support).
- Review: Premium mods are reviewed by both CurseForge and Wildcard; Overwolf's stated criteria are quality, the creator's reputation, value for the price and whether the mod adds to the game (conf. A; Microsoft article and CurseForge support). How free mods are moderated is not public (gap).
- The Official cosmetic whitelist (partly known): In February 2024 Wildcard said it checks a custom cosmetics mod for soft-reference mesh components, the correct item-skin flag and acceptable content (nothing obscene or infringing), and that the whitelist is per mod, so a cosmetic that could be unfair in PvP goes in its own mod (one was whitelisted for PvE only) (conf. A, dated Feb 2024; Jeremy Stieglitz, "ARK Dev Kit GameFramework & Custom Cosmetics Overview" (video, 2024; transcript read 2026-11-04)). Wildcard's current Official Cosmetic Whitelist page (read 2026-11-18) says only a mod's author can ask for a released cosmetic to be whitelisted, through a form, and that staff check each one for exploits and approve it for PvP and PvE or for PvE only (conf. A). It lists no other criteria. What the video tutorials teach §1 has the whole system.
- Announced in February 2024 and checked in November 2026: custom cosmetics downloading in the background shipped (Wildcard calls it dynamic download; premium cosmetics download this way on every platform, but on consoles a non-premium cosmetic over 700 MB doesn't), the separate menu for total conversions shipped, and session search inside a mod is only partly there, as a mod filter in the server list (conf. A and B; tutorials §3).
3. Cooking and testing, in brief
- Local cooks are Windows only.
CookModand the editor's UGC Local Cook window build Windows client and server for testing; console builds exist only after the cloud cook (conf. B). - Play In Editor runs the dedicated server and the client in one process. That hides replication bugs, cannot simulate a relog, and cannot prove async loading. Mod content runs only on a map whose World Settings "Primal Game Data Override" names the mod's own PrimalGameData, and PIE can keep stale mod data after a ModDataAsset edit (conf. B, verified in PIE). Real tests need a dedicated server and a remote client. Details: Modding lessons §3.
- Testing a cooked build before publishing (conf. D, from a creator's tutorial). A build that shows "ready for
review" on CurseForge can be played in single player through linked game accounts, or loaded on a test server as
the project ID plus
-dev(corrected 2026-11-05:-devper the official testing page and modders on the community Discord, 2023-10 to 2025-12); the mod's author and name (no spaces) cannot be changed after creation (conf. D). Details and the 2023 Share Mod requirements: What the video tutorials teach §4. - Publish metadata:
Preview/mod_settings.inicarries runtime switches (DisableInSingleplayer,DisableNonDedi,MinMajorVersion); after publishing, the.uplugin's description carries the CurseForge ID (conf. B).
4. What mods can and cannot do
| Mods can | Mods cannot (or should not) |
|---|---|
| Add creatures, items, weapons, structures, buffs, cosmetics, maps and whole game modes (Survival of the Fittest ships as two mods, map and logic) | Ship C++ or native code: everything in a mod is Blueprint and content; the upload has no code modules (conf. C, from the upload format and my census) |
| Register content through the PrimalGameData + ModDataAsset pair, which merges with other mods' (arrays append, maps overwrite by key, booleans OR) | Ship ini files to players (no Config/ folder in the upload) |
Replace vanilla classes everywhere with remaps (Remap_NPC, Remap_Items, Remap_Engrams, ...) and attach logic to every instance of a vanilla class (AdditionalDefaultBuffs) |
Edit or shadow /Game assets: none of Wildcard's own mods do, and every change goes through subclasses, remaps and the Additional* arrays (convention, conf. B) |
Run server logic in a world singleton and take admin commands through cheat ScriptCommand |
Add gene traits through the ModDataAsset (there is no field; code must give them) |
Read the server's Game.ini and GameUserSettings.ini (GetIniArray, Get*OptionIni) |
Read a player's platform on the server from Blueprint, or another player's PlayerState on a client (owner-only in ARK) |
Call HTTP and WebSocket services from the server, only through Wildcard's BPSecureNetworkingInterface (since game version 47.1 the older Blueprint HTTP nodes do nothing; custom cosmetics can't make calls; consoles need wss) |
Rely on anything that exists only on PC (Steam helpers, keyboard-only controls) in a cross-platform mod |
Override many native events, each behind its bUseBP* gate flag |
Override Final or plain callable functions, only events |
| Add custom cosmetics that apply as client-side class remaps, with no setup by the player (conf. A, Feb 2024; tutorials §1) | Swap a weapon's actor class through a weapon skin (same source) |
| Replace ARK's login, spawning, camera, input and respawn with Wildcard's Simple Game Framework for a total conversion (conf. A, Feb 2024; tutorials §2) |
Sources: my guides, conf. B unless marked; the ModDataAsset merge rules are read from the compiled
UPrimalGameData::MergeModData.
Where these pages come from
Much of this section rests on my own modding guides. I keep them private, along with my own mods, frameworks and analyses of other people's mods. I wrote them against the 5.8.1 DevKit (CL 830809), mostly offline: Blueprint bytecode, class defaults, debug symbols and the compiled game code, plus Play In Editor tests. They cover setup, testing and publishing; registration and ModDataAssets; networking, replication and saving; creatures, items, weapons, cosmetics, structures, maps, buffs, skill trees, game modes, UI and input; and a generated reference of every overridable native event. Each fact in them carries an evidence tag. On these pages, a fact verified in game or Play In Editor, verified offline, read from native code or counted across mods is class B, and an unverified pattern from other mods is class E.
Gaps
- The live game's UE 5.8 release date, from patch notes.
- The DevKit's download size and system requirements (one mapping tutorial calls 64 GB of RAM the minimum for map work, conf. D; no official figure).
- How free mods are moderated on CurseForge, and why Wildcard turns down a cosmetic for the Official whitelist beyond its exploit check (the whitelist page names nothing else).
- Whether
settings.cfgor the.upluginwins when their platform choice disagrees ([needs test] in my guides). - Whether a mod can run a session search from its own UI, the one part of Wildcard's February 2024 announcements still unknown (tutorials §3).