Modding guide

Testing your mod: PIE, then a local dedicated server

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

I test a mod in four steps. First quick checks in Play In Editor (PIE), then PIE as real clients. Then a local dedicated server with a cooked build, and last the CurseForge build itself.

  • You'll do: set up PIE for real multiplayer tests, test saving, run your mod on a local server, and check it off
  • Time: minutes per PIE run; an hour to set up the local server the first time
  • Level: beginner (you've made your first mod)
  • You'll need: a mod set up and registered, and a CurseForge project for the server stages

The four stages

Each stage catches mistakes the one before can't see.

Stage What it is What it catches What it hides
PIE, Standalone Single player inside the editor Logic errors, Accessed None, missing registration Everything about servers and clients
PIE, Play As Client A hidden server plus client windows, in one process Replication, ownership, late joiners Loading, real stasis, the cooked game
Local dedicated server Your local cook on a real server program Soft references, cooking, restarts, real logs Problems only CurseForge's cooker finds
CurseForge build with -dev The real cloud cook, unpublished (the -dev method) Everything players will get Nothing; this is the final check

I use the first two all day. The last two come before every release.

The process

  1. Test on your own test map, and reset the cache after registry edits. Its World Settings must name your PrimalGameData. After any Mod Data Asset edit, clear and restore that field.

    Show me how
    • Use the test map the Create Mod wizard made. The stock test map loads no mod content.
    • The cache reset: World Settings → clear Primal Game Data Override → Play → Esc → put it back → Play. The cache trap explains why.
    • Clear the Output Log before each run, so what you read belongs to this run.
  2. Do quick checks in Standalone, then switch to Play As Client. Standalone is single player. Play As Client with two players is the mode I leave on.

    Show me how
    • Play button menu (the three dots) → Net Mode = Play As Client, Number of Players = 2.
    • Editor Preferences → General → Experimental → Allow late joining. An Add another client button appears during PIE. Use it for anything that binds to player events.
    • The log calls the server world UEDPIE_0 and the clients UEDPIE_1 and up.
    • Recheck the net mode after an editor crash; it has been known to reset.
    • Works in PIE, not on a server explains what each mode hides.
  3. Know what PIE can't tell you. It runs server and clients in one process that shares the editor's memory. Some behavior there never happens live.

    Show me how
    • Everything is already loaded, so soft references and missing cooks never show.
    • Every PIE player is an admin, and each run logs in as a new player.
    • Items the server gives may not show in a Play As Client window.
    • Sessions decay after a long run or many spawns, roughly 10 to 16 creatures. Restart PIE before you decide something is broken.
    • The editor runs big maps slowly, so frame rate in the kit means nothing.
  4. Test saving in the kit with two launch flags. By default PIE never loads a save. Add -ForceSave -ForceLoad to RunEditorSDK.bat and tick Play Persistent Player on your test map.

    Show me how
    • Edit <DevKit>\RunEditorSDK.bat and add the two flags to the end of the editor's command line. Start the kit with the batch file from then on.
    • World Settings → Play Persistent Player (bPlayPersistentPlayer). It keeps player data between PIE runs.
    • Run cheat saveworld, stop PIE, start it again, and check your SaveGame values.
    • Modders report tribes aren't kept between sessions even with persistence.
    • A PIE save sometimes corrupts, and the kit then crashes when PIE starts. Delete your map's save under <DevKit>\Projects\ShooterGame\Saved\SavedArks and SavedArksLocal.
    • Some modders leave -ForceSave off and save by hand with cheat saveworld, so a bad run can't overwrite a good save.
    • How to save your mod's data lists what should survive.
  5. Read the log while you test. Search for your mod's folder name first. Then search for Accessed None.

    Show me how
    • Window → Output Log, or the file <DevKit>\Projects\ShooterGame\Saved\Logs\ShooterGame.log.
    • An Accessed None line names its world. UEDPIE_0 means the server did it; UEDPIE_1 means a client.
    • Log your own lines with Print Message in Shipping Build and a [MyMod] prefix. Print String disappears in cooked builds.
    • The game client only writes a log when started with -log. A server writes one every run.
    • Reading ARK's logs covers every file and the noise to skip.
  6. Cook locally and run it on a local dedicated server. This is the first test of the cooked game. Your project must already exist on CurseForge.

    Show me how
    • Cook with the cooking-pot button or <DevKit>\ModTools\Scripts\CookMod.bat, for Windows Client and Windows Server.
    • Start the server once with -mods=<ProjectID>-dev so it downloads your project, stop it, then copy your local cook over the downloaded files.
    • The full steps, file paths and the log lines to look for are in Test it properly: a local dedicated server. I don't repeat them here.
    • Start the server with -log. Its log is in <Server>\ShooterGame\Saved\Logs\. It prints the admin password, so never post it unedited (redacting a log).
  7. Join with two players, one of them not an admin. One player on a server proves very little. The second player shows you replication, relevance and permissions.

    Show me how
    • Use a second PC, or a friend added as a member of your CurseForge project. Only members can join an unpublished -dev mod.
    • Leave one player without admin. Admin-only checks hide bugs.
    • Join the second player late, after the first has used your feature.
    • Walk far away and come back, so your actors go through stasis.
    • Restart the server and check that saved values return.
    • Try a gamepad as well as a mouse, if your mod has UI.
  8. Finish on the CurseForge build. Once it's "ready for review", test it with -dev or from My Mods. Testing on a server before you publish has every step. Then publish.

    Show me how
    • Local cooks and cloud cooks can differ. Only this build shows reference problems CurseForge's cooker found.
    • Linking your game account to CurseForge puts unpublished projects in the game's My Mods list.
    • Test custom cosmetics this way, in single player. A server shows only the custom cosmetics its CosmeticWhitelistOverride setting allows (custom cosmetics).
    • Your first mod walks through both routes.

Test commands worth knowing

In PIE every player is an admin, so type cheat before each command. On a server, an admin logs in first with enablecheats and the admin password.

Command What I use it for
giveitem, gfi Spawn your item without the engram
summon, spawndino Spawn your creature or actor
summontamed A tamed copy for saddle and ride tests
forcegivebuff, listmybuffs Add your buff, and see which buffs you have
scriptcommand Call your singleton's admin commands

These change the world, the clock or you.

Command What I use it for
saveworld Save now, then restart to test persistence
settimeofday, slomo Test day and night, or speed up timers
ghost, fly, walk Move around a test map fast
god, infinitestats Stay alive while you watch something
destroymytarget, destroywilddinos Clear clutter, or force a respawn of wild creatures
leveluptarget, setstatontarget Test stat changes on a creature
giveengrams, addexperience Check engram levels and unlocks
togglehud Check your UI survives the HUD being hidden

For an item's path, right-click it in the Content Browser and pick Copy Reference.

Game time in PIE starts at 200,000,000 seconds

The world clock doesn't start at zero. I checked 25 of my own DevKit PIE crash reports, from September to November 2026. Each read 200,000,000 seconds plus the time since PIE started. A single-player crash in the shipping game read about 100,000,040.

So never assume a starting value. Store "now plus the delay" and compare against now. A timestamp saved in one session and read in another is only safe if the clock starts the same way. I haven't checked a dedicated server's start value.

Known PIE crashes

  • Opening the inventory while holding anything but fists, in PIE. It's a long-standing bug (a StopFire loop), but none of my own 517 kit crash reports show it, so it may not hit every weapon or every kit version. Putting the weapon away first costs nothing.
  • Stopping PIE while a widget with a virtual cursor is open. Close your menu first.
  • Compiling a Blueprint while PIE runs.
  • Saving an asset whose actor is in the running PIE level.
  • Switching levels with Blueprint editors open.
  • An audio hang when PIE exits. Starting the kit with -nosound avoids it.

Reading a crash report covers the rest.

Before you publish: a short checklist

  1. The mod name is real, not cfeditor, in both the PrimalGameData and the Mod Data Asset.
  2. No compile errors or warnings in your files, and no Print String left in.
  3. Tested as two clients in PIE, one joining late.
  4. Tested on a local dedicated server: a restart, stasis, and a player who isn't an admin.
  5. The server log shows LoadGameMods with your mod and no Accessed None naming your folder.
  6. Every ini key is documented with its default.
  7. Textures are capped; 1024 is plenty for icons.
  8. The CurseForge build passed the same tests with -dev.

lessons §9 has the long version.

Common mistakes

My test map loads none of my content

Its Primal Game Data Override is empty or wrong. Set it to yours (step 1).

My changes to the Mod Data Asset don't show in PIE

That's the cache. Clear and restore the override (step 1).

My save never loads in PIE

The kit started without -ForceSave -ForceLoad. Or Play Persistent Player is off (step 4).

My test server won't start with my unpublished mod

The project ID needs -dev. Without it the server looks for a published file and logs "Detected an unavailable mod".

It worked in PIE and does nothing on my server

Start with Works in PIE, not on a server. It's usually the wrong machine. Or the cooked game never loaded something.

My PIE session gets strange after a while

PIE sessions decay. Restart PIE, and the kit if it persists.

Watch

Go deeper

Sources

  • DevKit files, read on 2026-11-06 (UE 5.8.1): RunEditorSDK.bat and its editor command line; APrimalWorldSettings.bPlayPersistentPlayer; the cheat commands above, all in the kit's code (the /ark/browse/commands pages list each one). The kit root also holds GameDedicatedServer.bat and GameClient.bat, which start an uncooked server and a client from the editor build. A 2023 community guide pointed to them before Play As Client worked; modders then reported they don't load mods. I haven't tested them.
  • Game time: the TimeSeconds line in the footer of 25 DevKit .crashstack files (September to November 2026, all PIE runs, game mode "Dedicated Server"), every one between 200,000,000 and 200,002,429; and one shipping single-player client crash (October 2026) at 100,000,040. Lessons §3 gives 100,000,000 for PIE; on the current kit, PIE starts at 200,000,000.
  • My other pages: lessons §3 and §9 (PIE limits, known PIE crashes, -ForceSave -ForceLoad, -nosound, the release checklist) and tutorials §4 (-dev and My Mods).
  • What modders report: -ForceSave -ForceLoad and Play Persistent Player (November 2023 to March 2026); tribes not kept and corrupt PIE saves (November 2023, March 2026); saving by hand instead (June 2024); the batch files (October and November 2023); stopping PIE with a widget open; compiling during PIE.
  • Videos under Watch are creators' tutorials, not checked against the kit.
  • Community knowledge from the ARK Modding Community Discord (discussions from October 2023 to March 2026), found with Overseer. Threads (they open for server members): persistent saves in the kit (November 2023), persistence and tribes (March 2026), corrupt saves and saving by hand (June 2024), the server and client batch files (October 2023), the batch files don't load mods (November 2023).
Where this page's information comes from

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

the DevKit's own files, my own crash reports and logs, the community Discord and creators' videos (see Sources)

Esc

↑ ↓ move↵ openCtrl ↵ new tab