Installing and launching the DevKit
8 min readASA DevKit as of November 2026 (UE 5.8.1); ASE where noted
Get the ARK DevKit installed, open and set up to stay fast. The DevKit is Studio Wildcard's free Unreal Engine editor for making ASA mods. The download takes hours and the first launch a long time, so start it before you plan to work.
- You'll have: the DevKit installed, a shortcut that launches it reliably, and a sense of what "busy" looks like
- Time: the download (often several hours), then a long first launch
- Level: complete beginner
- You'll need: a Windows PC, an Epic Games account, and a fast drive with plenty of free space
What your PC needs
There's no official requirement list I trust, so these are my own figures from my beginner guide video.
| Part | What I recommend |
|---|---|
| RAM | As much as you can. 64 GB is comfortable, 32 GB workable, 16 GB painful. |
| Disk | An SSD with about 2 TB free. My install was about 1 TB, and your mods and the cache grow on top. |
| CPU | Any recent mid-range or better desktop CPU is fine. |
| GPU | Matters less than RAM. If ASA runs on medium to high at 30 fps or more, the DevKit will run. |
RAM matters most. The editor's memory use creeps up through a session, and running out is one of the most common crashes I see.
The process
Install the Epic Games launcher and sign in. The DevKit is only distributed there, and it's Windows only.
Show me how
- Get the launcher from the Epic Games website and make an account if you don't have one.
- You don't buy ASA on Epic to use the kit. As far as I know, it doesn't matter where you own the game. You do need ASA on PC to try your mod in the real game.
Get "ARK DevKit" from the store, on the normal branch. Don't pick the beta, and don't pick the old UE4 "ARK Mod Kit": that one is for ASE. Bringing an ASE mod across? See coming from ASE.
Show me how
- Search the store for "ARK DevKit". The page shows two versions: the DevKit and its beta.
- Pick the one without "beta". The beta is where Wildcard tests new tools, so it's less stable. The upload window also refuses to upload from a kit newer than CurseForge's cooker, and a beta kit always is.
- The store goes through a checkout screen as if you were buying it. It's free; confirm and it lands in your library.
Install it to a fast drive with room to spare, and note the folder. I call that folder
<DevKit>in this guide.Show me how
- Click Install on the library tile and choose the drive. An SSD makes a big difference to load times.
- Size: about 1 TB on my install. It was much smaller at launch, and it grows as content is added. There's no official figure.
- Check the install options for DLC content. A kit update in early 2026 stopped installing DLC packages by default to save space. If you'll reference a DLC creature or map asset, tick it there.
- When it's done,
<DevKit>holdsRunEditorSDK.batand the foldersEngine,ProjectsandModTools.
Launch it with
RunEditorSDK.bat, not the launcher. Put a shortcut to it on your desktop.Show me how
- Right-click
<DevKit>\RunEditorSDK.bat→ Send to → Desktop (create shortcut). - The launcher sometimes thinks the kit is still running after a crash, and won't start it again. The batch file doesn't care.
- The batch file starts the editor with the flags Wildcard ships. One of them,
-log, opens a second window of scrolling log lines beside the editor. That's the live log. Leave it open. - Later pages have you add flags to this file, such as
-ForceSave -ForceLoadfor testing saves. That's another reason to launch from it.
- Right-click
Let the first launch finish before you touch anything. It compiles shaders and builds its asset list, and that takes a long time the first time.
Show me how
- First you get a splash screen with a percentage. It can sit on one number for a long time. That's normal on the first launch and after every update.
- Then the editor opens on a gray test map. A bar near the middle says it's loading or building the asset hierarchy, and a counter at the bottom right shows shaders compiling. Wait for both to finish.
- A message log and other windows may pop up with yellow and red lines. On a fresh kit they're vanilla noise; Reading ARK's logs lists the usual ones.
- A creator's tip I agree with: press Play once, walk around, then stop. That gets the slow first load of the game's assets over with.
- The first Blueprint you open in a session is slow too. It loads a lot of the game in the background.
Open the documentation once. The page icon on the toolbar opens Wildcard's DevKit documentation in your browser.
Show me how
It covers joining CurseForge, creating mods and maps, the UGC settings, cooking, account linking and testing. It's the official word.
Busy or crashed?
The DevKit freezes for minutes at a time while it loads or compiles. I tell a busy editor from a dead one like this:
- Right-click its taskbar entry. If the little Restore/Move/Size menu appears, it's busy, not crashed.
- Watch the log window. If lines are still scrolling, it's working.
- Open Task Manager.
ShooterGameEditor.exeusing CPU, or severalShaderCompileWorkerprocesses, means it's working. - A real crash closes the editor, usually with a crash reporter window. It writes a
.crashstackfile to<DevKit>\Projects\ShooterGame\Saved\Logs. Reading a crash report explains it.
While it's busy, don't click around. Note which assets show an unsaved asterisk, in case it does crash.
Keeping it fast
- Save often and restart before memory runs out. Watch memory in Task Manager. Near 98% the editor slows right down, and around 99% it usually crashes. Save all (Ctrl+Shift+S), close it and start it again.
- Lower the scalability. Settings → Engine Scalability Settings → Low. Turn off Realtime in the viewport's menu.
- Close what you aren't using. Every open map and Blueprint editor holds memory. Close Blueprint editors before you switch maps; switching with them open is a known crash.
- Close other programs, especially the game and big browser sessions.
- Give Windows a large page file on a fast drive. It turns some out-of-memory crashes into slowdowns.
- Leave the derived data cache alone. It's the editor's store of processed shaders and assets, so the next launch
doesn't redo the work. With the stock launch flags it lives in
<DevKit>\Engine\DerivedDataCache. Delete it only as a repair step, with the kit closed; the next launch is then as slow as the first.
Updating it
The DevKit updates through the Epic launcher, with the game. The short version of the full routine:
- Copy your mod folder first. It's
<DevKit>\Projects\ShooterGame\Mods\<YourMod>. - Update on the normal branch, and recheck the DLC install options.
- Check
RunEditorSDK.bat. If you added flags, make sure they're still there. - Let the first launch finish. It recompiles shaders, just like the very first time.
Your kit's version is at the top right of the editor window and on the launcher tile.
Common mistakes
The launcher says the DevKit is already running, but it isn't
The launcher lost track after a crash. Start the kit from RunEditorSDK.bat. If that fails too, end any leftover
ShooterGameEditor.exe in Task Manager first.
It's stuck at a percentage on the splash screen
On a first launch or after an update, it's almost always compiling shaders and filling the cache. Check Task Manager:
if ShaderCompileWorker processes are busy, wait. I don't have a reliable list of what each percentage means.
It crashes on start, or a few seconds after the map appears
Usually it's the GPU or memory, not your mod. Close overlays such as MSI Afterburner's stats overlay, update or roll back the GPU driver, and lower the scalability. Details: the GPU and out of memory.
Everything I open from my mod crashes the kit
Verify the kit: in the launcher's library, the tile's menu → Manage → Verify. Then delete the derived data cache, as above. Modders report that verifying gets the kit opening again, but it doesn't repair a broken asset. For that, see a corrupted asset.
The upload window sits on "checking version of cooking tools"
Restart the kit and update it in the launcher. A beta kit is refused outright. More in Your first mod.
My drive filled up
The kit, its cache and its Saved folder all grow. Every crash leaves a folder under
<DevKit>\Projects\ShooterGame\Saved\Crashes, and those add up. Once you've read them, old crash folders can go.
Check it worked
- The editor opens on the gray test map, and the bottom-right counter no longer shows shaders compiling.
- Pressing Play drops you into the test map as a survivor. Esc stops it.
- The UGC menu is in the top menu bar. That's where Create Mod and Share Mod live.
- The log window is open, and
<DevKit>\Projects\ShooterGame\Saved\Logs\ShooterGame.logexists.
Next: Finding your way around the editor, then Your first mod.
Watch
- How to Make an ARK ASA Mod (Complete Beginner Guide) (my video, 0:00: hardware; 1:44: installing and which branch; 3:28: launching with the batch file; 5:08: watching memory and restarting).
- ASA Modding | How to get the ARK DevKit | Episode 1 (SlayerXtreme, 1:01: installing, and why not the beta; 5:14: the first launch and pressing Play once).
- Modding in ASA: Getting the ARK Devkit (Mist3r Trixt3r, 0:10: finding the kit and avoiding the old UE4 Mod Kit; 2:40: the documentation button).
- ASA Modding | Putting the correct SETTINGS on your DEVKIT (SlayerXtreme, 0:01: scalability settings; 1:42: turning off Realtime).
Go deeper
- README §1: what the DevKit is and how its versions have changed.
- Reading a crash report and Reading ARK's logs.
- Publishing and updating: why the kit, the game and the cooker get out of step.
Sources
- My beginner guide video, 7TwjI7TCE_w (Sept 2025, UE 5.5 DevKit): hardware figures, branch choice, install size, launching with the batch file, the memory creep and the busy-or-crashed check. There's no official hardware figure.
- DevKit files, read on 2026-11-06 (UE 5.8.1):
RunEditorSDK.batand its editor command line (-logand the local cache flags); the editor log'sLogDerivedDataCachelines namingEngine/DerivedDataCacheas the local cache; the root folder layout. - My own crash reports and logs for the GPU and out-of-memory crashes and the
Saved\Crashesfolders; see Reading a crash report. - Creators' videos: SlayerXtreme, Episode 1 (Dec 2023) and Episode 7 (Jan 2024); Mist3r Trixt3r, "Getting the ARK Devkit" (Oct 2023, when the download was about 285 GB).
- The launcher not starting a crashed kit, the kit update that dropped DLC packages (2026-02), verifying and clearing the cache (2025 to 2026), and the stuck upload window (2024-02, 2025-06): modders on the community Discord, as gathered for Reading a crash report and Publishing and updating.
- Not confirmed: whether owning ASA on Steam matters for the kit (a 2023 Steam forum thread says it doesn't); what each splash-screen percentage means; how long a first launch takes on typical hardware.
Community knowledge from the ARK Modding Community Discord (discussions from February 2024 to May 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 launch files and logs, creators' videos and community knowledge (see Sources)