Works in PIE, not on a server
19 min readASA DevKit as of November 2026 (UE 5.8.1); ASE where noted
After "it doesn't show up in game", this is the question modders ask most. The mod works when I press Play in the editor. On a real server the effect is missing, a variable never changes for players, or nothing happens at all. Almost every case is one of three things: the test didn't run the way a server does, the code ran on the wrong machine, or the shipped (cooked) game doesn't load something the editor had lying around.
This page is symptom first: find what you see, read why, do the fix. If your content doesn't appear at all, start with How ARK finds your content. If something crashes, see Reading a crash report.
The short version
Check these in order. The first two catch most cases.
- Test with Net Mode set to "Play As Client", not the default Standalone, which has no networking at all. Recheck the setting after an editor crash; it has been known to reset.
- Ask "which machine runs this node?" Game mode, ini settings and anything spawned with authority live on the server. Widgets, sounds and particles only matter on clients.
- The server changes things; clients get told. Replicated variables carry state, with RepNotify for anything players see. A multicast called on the server carries one-off effects.
- Run on Server only works from an actor the client owns: its controller, its character, a buff on it. A structure or a wild dino isn't owned.
- Send server-only data to clients on purpose. Read the ini once on the server, and replicate it from a singleton every client has.
- Class default object edits must run on the clients too, and again every time the server starts.
- The shipped game is not the editor. Print String is stripped,
BPLoadClassandBPLoadObjectdo nothing, and soft references stay unloaded until you load them. - Before you publish, test on a local dedicated server with a local cook. One good PIE run proves very little.
Why your PIE test lied
PIE (Play In Editor) is the Play button in the DevKit. Its menu, the three dots next to it, sets the net mode:
| Net Mode | What it really is | What it hides |
|---|---|---|
| Play Standalone (the default) | Single player. One machine is server and client at once; nothing is replicated | Everything about replication, ownership and server-only data |
| Play As Listen Server | One window is a host that also plays; other windows connect to it | Most server/client mistakes for the host's own window; the host behaves like single player |
| Play As Client | A hidden dedicated server plus one or more client windows | Much less, but still runs in one process (below) |
Even Play As Client isn't a real server. In ARK's PIE, the server and client worlds run in one process that
shares the editor's memory. The log calls them UEDPIE_0 and UEDPIE_1. So:
- Everything is already loaded, so a missing load never shows. That's the cooked-build trap below.
- There's no latency, and both worlds tick in step.
- Every PIE player is an admin, with no switch to turn that off.
- The client connects almost instantly, often before your singleton has bound the game mode's events, such as
OnShooterCharacterSpawned. Those events then look broken in PIE but work on a real server. A late-joined client fires them; step 1 of the last section shows how. - PIE sessions decay. After a long run or many spawns things go strange, and eventually you're kicked to the main menu. Restart PIE before you decide something is broken.
What I do: two clients for everyday work, a late joiner for anything that binds to player events, and a local dedicated server before every release.
Who runs what on a dedicated server
A dedicated server is a separate program with no screen and no local player. Every player's game is a client. Each machine has its own copy of every actor it knows about, and only the server's copy is the truth.
| Thing | On the server | On a client | Notes |
|---|---|---|---|
Game mode (ShooterGameMode) |
yes | no | Get Game Mode returns None on a client, so casts to it fail there |
ini settings (GameUserSettings.ini, Game.ini) |
yes | no | Reads on a client return the default |
| Your singleton | yes | only if it replicates (below) | Spawned on the server from the Mod Data Asset's ServerExtraWorldSingletonActorClasses |
| A player's controller | yes | only that player's own | Other players' controllers never exist on your client |
| Characters, dinos, structures | yes | when near enough (relevant) | Far away or in stasis: no copy, or an old one |
| Buffs | yes | where relevant | A buff with Only Relevant To Owner exists only on its owner's client |
| Items in inventories | yes | as data | Items aren't actors: replicated variables and events on them do nothing |
| Widgets, HUD, sounds, particles | pointless | yes | A dedicated server has nobody to show them to |
| Class default objects (CDOs) | its own | each client its own | An edit on one machine doesn't reach any other |
To find out where a node runs, put one of these in front of it:
- Switch Has Authority: Authority is the machine that spawned the actor. For anything that replicates, that's the server (or the only machine, in single player), and Remote is a client's copy. An actor a client spawns for itself has authority on that client: the green placement preview of a structure is one.
- Is Running On Server: True on the server and in single player.
- Can Run Cosmetic Events: True wherever someone can see the result (clients, single player, a listen host). False on a dedicated server. Buffs use both of these a lot.
One thing trips people up. In single player and on a listen host, one machine is both server and client, so both branches run there. My singleton video covers this (see Watch).
Symptoms
Clients don't see a variable change
What you see: the server's value is right, but players see the old value, or see it once at spawn only.
Why: the variable or the actor doesn't replicate, or the change was made on a client and never traveled up. Or ARK is holding it back: it sends most state once, when an actor first reaches a client. Many actors, structures above all, then sit dormant until something wakes them.
What to do:
- Tick Replicates on the actor, and on the component if the variable lives on one.
- Set the variable to Replicated, or RepNotify if clients must react visually. Do that work in the
generated
OnRep_function, which runs on every client when the value arrives, late joiners included. In Blueprint it also runs on the server when the server sets the variable, so don't double the work there. Setting the variable inside a function or macro that takes it by reference doesn't fire it at all. - Set it on the server only. A value set on a client stays there.
- On a structure, call Flush Net Dormancy before you set the value. That's the working idiom in the 5.8.1 code (lessons §4).
- Replicated arrays and object references have been reported to lag or miss updates. The workaround: a RepNotify byte you change whenever the array changes, with the client work in its notify.
- A replicated variable sends its latest value, not every change. If the server turns it on and back off between two updates, clients never see it. To signal something that happened, raise a counter instead (Epic's networking talk, general Unreal).
My effect, sound or animation plays only for me, or only in single player
What you see: a sound, particle or montage works in Standalone. On a server only the triggering player sees it, or nobody does.
Why: it was spawned on the server, which has no screen or speakers, or on one client. A multicast called from a client runs only on that client.
What to do: call a Multicast custom event from the server and spawn the effect inside it. Pass the values it needs as inputs of the multicast, so they arrive together. Two limits:
- A multicast only reaches clients for whom the actor is relevant: near enough, and not in stasis.
- Late joiners never get it. Anything that must stay true, like an open door, is state. Use RepNotify for it (lessons §4).
For effects that should play whenever the actor appears on a client, spawn them from Begin Play on the client side.
My Run on Server event never fires
What you see: a button in your widget or a multi-use entry calls a Run on Server event. Nothing happens on the server, and there's no error.
Why: Unreal drops a client's Run on Server call unless the client owns the actor. ARK's C++ sets each actor's owner. Your controller, your character and buffs on your character are yours. A structure, a wild dino or the singleton isn't (tutorials §6).
What to do: route the call through something you own.
- Net exec through the player controller: Call
ClientSendNetExecCommandToServeron your controller with the target actor, a command name and its parameters. Handle it on the server inBPServerHandleNetExecCommand. This is ARK's own route for structures and singletons. - A buff on the player: Its Run on Server events work because the player owns it.
- Multi-use already goes to the server. Do the work in the server side of the use; my multi-use video shows how.
Whatever the route, the server must check the caller again. A client can call any server event on an actor it
owns, with any arguments. Check admin with IsPlayerAllowedToCheat, check tribe, distance and price, and clamp every
value (lessons §5).
Dinos turn invisible after they come out of stasis
What you see: players leave an area and come back, and some dinos or other actors are invisible to every client until a restart. It never happens in PIE with one player.
Why: stasis is ARK putting actors far from every player to sleep: they stop ticking and replicating. One modder found that a multicast called from a repeating timer or delay loop stops actors setting up on clients when they wake. It happened even with a 10-second loop and Reliable off, but not on the older UE 5.2 DevKit. Two people reproduced it; nobody has found the engine cause.
What to do: don't multicast on a timer. Do the repeating work in an authority-only event on the server, and send clients state through RepNotify. If something visual must repeat, run its timer on each client locally.
My timer stops after nobody has been nearby for a while
What you see: a looping timer on a structure or dino, like a generator or a nanny, works while you watch and stops when you leave.
Why: stasis again. Modders disagree on whether looping timers resume or vanish, but agree they're unreliable through stasis. Also, a timer started in Begin Play without an authority check runs on every client too.
What to do:
- Start server logic timers behind Switch Has Authority.
- Restart them in the unstasis event,
BPUnstasis. If it never fires, check thatbTriggerBPUnstasisis on in the class defaults. I haven't checked that flag class by class. - For resource generation, don't count on the timer. Save the time, and on waking, work out how many intervals passed. Modders say the vanilla Achatina makes its paste this way.
Casting to the game mode fails, or my ini settings come back empty
What you see: your settings work in Standalone. On a server players get the defaults, or the cast to the game mode fails.
Why: the game mode and the ini exist only on the server. A client that reads them gets None or the default.
What to do: read ini values once, on the server, usually in the singleton's authority branch, and clamp them. Store them in replicated variables on an actor every client has (next symptom). Reads are cheap, since the game mode caches the file, but don't read every tick.
Console single player can't edit an ini at all. Mods that must work there keep settings in a SaveGame object, or in SaveGame variables on the singleton, with a menu.
My singleton works on the server, but clients never see it
What you see: the server log shows the singleton running. But its replicated variables and multicasts never reach clients, and Get All Actors Of Class on a client finds nothing.
Why: clients only get a copy if it replicates, and every client only if it's relevant everywhere.
What to do: set these in its Class Defaults. Its parent must be SaveGameActor; the singleton list has required
that since the move to ASA (lessons §1).
| Setting | Property | Why |
|---|---|---|
| Replicates | bReplicates |
Gives clients a copy at all |
| Always Relevant | bAlwaysRelevant |
Every client gets it, wherever they are on the map |
Those two are all a singleton needs. Many guides, this one included until now, also tick Net Load on Client and set Rep Graph Behavior to Relevant All Connections. A modder who reviewed this page pointed out that neither does anything here. Net Load on Client makes clients load an actor that was placed in a map as part of that map, so it matters to map makers, not to an actor the game spawns. To send something to the singleton from a client, use the net exec route above.
My class default object edits work for the host, not for clients
What you see: you change a vanilla class's defaults at runtime. That's a CDO edit: changing the class default object, the copy of a class that holds its starting values. It works in single player and for a listen host, but dedicated-server players see old values or odd mismatches.
Why: every machine has its own CDOs. A server-side edit changes nothing on clients, and edits reset when the game restarts. Wildcard's own Workshop episode on CDOs says the same (see Watch).
What to do:
- Make the edit from something that runs on every machine, such as a singleton set up as above. If it depends on ini values, replicate them first and edit in their RepNotify.
- Re-apply it every server start. Nothing saves a CDO edit.
- Items re-initialize from their class often, so existing items may need a re-init.
- Prefer add and remove on arrays over Set, so you don't wipe other mods' or the server owner's entries.
- Know the risk. Vanilla CDO edits stay in a player's game after they leave your server, until they restart ARK. Joining another game in that state can misbehave; modders split on how much that matters. If a child class plus a remap, or a default buff, can do the job, I use those instead.
It works in the DevKit and is dead in the cooked game
What you see: everything works in PIE, even as a client. After the CurseForge cook the feature does nothing, a cast fails, or a class comes back None. The Discord calls it "works in the kit, fails live".
Why: a cooked (shipped) build only contains and loads what it must. PIE had everything in memory, so it never noticed.
- Soft references aren't loaded. A soft reference is a path to an asset that loads only when you ask. The automatic convert-to-hard-reference only works if the class is already loaded (lessons §2). String Reference to Class and Make Soft Class Path don't reliably load it either.
BPLoadClassandBPLoadObjectare disabled in shipping builds. They exist for editor tools.- Assets outside your mod folder aren't uploaded. The CurseForge cooker takes your mod folder and cooks all of it, referenced or not. A local cook can still see the rest of your DevKit, so it can pass where the real one quietly leaves a file out.
- References into other mods or an old mod folder cook "successfully" and break live. The cook log shows "Skipping non mounted imported package" or compile errors naming your file, even when CurseForge says Success.
- Content changed under you. Since the January 2026 cooker update, supply crate item entries hold soft class references, so old wiring fails to compile.
What to do:
- Load soft references yourself. Class Asset Request is asynchronous and may return None until the class has loaded. Class Asset Resolve loads it now. For another mod's classes, resolve once at start and cache them.
- Replace
BPLoadClassin runtime code with String Reference to Class. It takes the same path string and works in the shipped game. When the class must be loaded right then, turn the path into a soft reference (Make Soft Class Path, then To Soft Class Reference) and pass it to Class Asset Resolve. Objects loaded withBPLoadObjectgo through the asset versions of the same nodes. - Keep every asset your mod uses inside your mod folder.
- Read the cook log every time, not just the status (When a cook or upload fails).
My Print String shows nothing on the server
What you see: your debug prints work in PIE, but a server or the live game logs nothing.
Why: Print String is Development Only and stripped from shipping builds. And the "Server:" and "Client 1:" prefixes exist only in PIE.
What to do: use Print Message in Shipping Build. It writes to the log of whichever side calls it; start the
game with -log to see a client's. Prefix messages with [YourMod] and a side, like [YourMod][S], and gate them
behind an ini debug flag. PrintToServerGameLog writes nothing unless the server runs with -servergamelog
(lessons §3). Reading ARK's logs says where the logs live.
It works for the first player and not for the next one
What you see: the first player, or the PIE player, is fine. Later joiners miss a buff, a value or a UI change.
Why: usually one of two causes. Multicasts never reach late joiners, so use RepNotify for state. Or an event
bind: the singleton binds OnShooterCharacterSpawned on the server, and players already in the world never trigger
it. That's the listen host, the single-player player, or a fast PIE client.
What to do: after binding, sweep the players who already exist and run the same setup on each. Then test with a late-joined client (lessons §1).
Test it properly: a local dedicated server
A local dedicated server running a cooked build catches what PIE misses: real loading, real stasis, real logs. It runs on the same PC as your game.
Get your test PIE right first. Use Play As Client, two players, and late joining on.
Show me how
- Play button menu (the three dots): Net Mode = Play As Client, Number of Players = 2.
- Editor Preferences, General, Experimental: tick Allow late joining. During PIE an Add another client button appears. Start as a client, wait ten seconds, then press it.
- In the log,
UEDPIE_0is the server world andUEDPIE_1and up are clients. "Accessed None" lines name the world, so you can tell which side failed.
Upload the mod to CurseForge once. A local build replaces files of a mod the game already has, so the project must exist. It needn't be published: an unpublished project loads with
-devafter its ID, for members whose game accounts are linked (the-devmethod). Your first mod covers the upload.Cook locally, for Windows Client and Windows Server.
Show me how
- The local cook button on the editor's top toolbar looks like a cooking pot. It opens the UGC Local Cook window. Pick the mod, tick Cook Windows Client and Cook Windows Server, and set the number of cook processes. Each takes several GB of RAM, so go low if unsure.
- Or run
<DevKit>\ModTools\Scripts\CookMod.bat, which asks the same questions. - You get two zips, client and server, in
<DevKit>\ModTools\Output\<YourMod>\. Check both have today's date. In early 2024 a bug skipped the server cook silently; v38 fixed it. - Cook logs go to
<DevKit>\Engine\Programs\AutomationTool\Saved\Cook-<date>_Worker<N>.txt. Read the summary at the end before testing.
Let the server and the game download the mod once, then stop them. Start the server with your project ID in
-mods=, plus-devif unpublished, and open the mod once in the game.Replace the downloaded files with your local cook. The Local Cook window prints these steps too.
Show me how
- Back up the mod's folder first.
- Client: the game keeps mods under
<Game>\ShooterGame\Binaries\Win64\ShooterGame\Mods\83374\<ModID>\. Server: the server log'sLogCFCore: SetSettings called:line names its mods directory. - Extract the matching zip and replace the mod's files except the
.uplugin. - If the server re-downloads your files on every start, you replaced more than it expects. One modder only ever
swaps the
.pakfiles.
Start the server, join with the game, and read the server log. It's in
<Server>\ShooterGame\Saved\Logs\.Show me how
UShooterEngine::LoadGameMods with N mods: N should count your mod.Initialize Primal Game Data Override.and the lines after it: for a map mod, whether your Primal Game Data loaded.Server: "<name>" has successfully started!: if it's missing, the server died while loading. Read the last lines and the.crashstacknext to the log.- Your own
[YourMod]lines from Print Message in Shipping Build. - For the client side, start the game with
-log.
More in Reading ARK's logs.
Test like a release. Walk far away and come back (stasis), restart the server (persistence), and join late with a second client. Try your feature as a client that isn't an admin. My release checklist is in lessons §3.
Once it works locally, test the real CurseForge build once more, with -dev or My Mods, before you press Publish.
Only that build shows reference problems the CurseForge cooker found.
Watch
- Ark Survival Ascended - Dev Kit - Replication (Quellcrest). 17:10 custom replicated events. 24:15 RepNotify. 29:32 structures and net exec through the player controller.
- Ark Ascended Devkit: The Ultimate CCA (Singleton) Tutorial (my video). 8:55 Switch Has Authority at server start, and why single player runs both branches. 14:17 reading ini values from the game mode. 37:52 replicating a counter to players.
- Modding Replication fix (Mist3r Trixt3r). 1:30 a server setting clients didn't see, fixed with RepNotify.
- ARK:SA Modding — Ultimate Multi-Use Guide (my video). 24:55 doing a multi-use entry's work on the server.
- How to Make an ARK ASA Mod (Complete Beginner Guide) (my video). 39:53 testing a build on a server before publishing.
- Wildcard Workshop #4: Replication Overview and #5: Replication In Practice (ZenRowe). Made for the ASE ModKit in 2018, but the basics still hold. One exception: #4 says Reliable is only about the order of calls. In Unreal a reliable call is also guaranteed to arrive, resent if lost, and too many fill a buffer (performance). 24:02 in #5: a buff on the player to talk to the server.
- Wildcard Workshop #12: Class Default Objects (ZenRowe, ASE). 2:36 what a CDO is and why edits need care.
Go deeper
- lessons §4: Networking and replication: the replication graph, what replicates once,
MulticastProperty, dormancy budgets. For when you want the numbers. - lessons §5: Server trust and security: checking every server call.
- tutorials §5 and §6: sparse class data, custom item data, ini settings and the net exec route.
- Reading ARK's logs, Reading a crash report, When a cook or upload fails.
- Testing your mod, How to run global logic (singletons and the ini settings your mod reads) and Changing vanilla content without replacing it.
Sources
- DevKit, read offline on 2026-11-05 (UE 5.8.1): Every class, function and property name here is in the kit's
code:
ServerExtraWorldSingletonActorClasses,SaveGameActor,ShooterGameMode,ClientSendNetExecCommandToServer,BPServerHandleNetExecCommand,IsPlayerAllowedToCheat,PrintMessageInShippingBuild,PrintToServerGameLog,BPLoadClass,BPLoadObject,ClassAssetRequest,ClassAssetResolve,BPUnstasis,bTriggerBPUnstasisandRepGraphBehavior(ShooterGame module);IsRunningOnServer,CanRunCosmeticEvents,bAlwaysRelevant,bNetLoadOnClientandEReplicationGraphBehavior::RelevantAllConnections(engine module);bOnlyRelevantToOwnerandbDestroyOnTargetStasis, set on/Game/PrimalEarth/CoreBlueprints/Buffs/Buff_Base_OnlyRelevantToOwner. How each behaves at runtime is from the community where listed below. - My own DevKit PIE logs and a local dedicated server's logs (2026-10 and 2026-11): the one-process PIE worlds,
the server log lines,
CookMod.batand the cook log location. - Modding lessons §1 to §5 and What the video tutorials teach §4 to §6 on these pages, including the "items aren't actors" row (tutorials §5) and Run on Server ownership (tutorials §6).
- What modders report on the ARK Modding Community Discord: PIE players are admins (2024-09); late joining for
event binds (2023-11, 2025-09); PIE sessions decaying (2024); what Is Running On Server and Can Run Cosmetic Events
return per mode; lagging replicated arrays and the RepNotify byte (2024-05); Run on Server ownership (2024 to
2025); the net exec route in use (also Quellcrest's video at 29:32); the multicast loop and invisible dinos, where
the multicast added a buff (2025-07, one thread); timers through stasis and the Achatina (2023 to 2026); cheap ini
reads (2024); console settings (2023 to 2024); the singleton settings as a set (2024-01); CDO edits (2024 to
2026); soft references and
BPLoadClassin shipping (2023-11 and since); supply crate soft references (2026-01); the local cook steps (2023-11 to 2026-07) and swapping only.pakfiles (2026-07). - Videos: Quellcrest, "Ark Survival Ascended - Dev Kit - Replication" (2024-11); Mist3r Trixt3r, "Modding Replication fix" (2023-11); ZenRowe, Wildcard Workshop #4, #5, #12 (ASE, 2018); my own singleton, multi-use and beginner videos (2025), all on my channel, Hypernatrema Mods.
- Discord threads (open for server members): singleton multicast settings and the net exec route (January 2024), multicast loop makes dinos invisible (July 2025), replication limits and the RepNotify byte (May 2024), CDO edits on items and clients (March 2025), BPLoadClass dead in shipping; request vs resolve (December 2023), late joining in PIE (September 2025), testing a local cook (November 2023), ini reads are server-only (May 2024).
- Community knowledge from the ARK Modding Community Discord (discussions from November 2023 to October 2026), found with Overseer.
- Corrections from a reader's review, November 2026, checked against the Discord: the cooker takes the whole mod folder (December 2024), files outside the mod folder don't upload (January 2026), String Reference to Class instead of BPLoadClass (April 2025). Authority on client-spawned actors and the singleton settings are the reviewer's.
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 code, my own logs, the community Discord and tutorial videos (see Sources)