Reading ARK's logs
17 min readASA DevKit as of November 2026 (UE 5.8.1); ASE where noted
The DevKit rarely tells you in a popup what went wrong. A Blueprint that does nothing, a PIE session that closes itself, an editor that vanishes: the reason is almost always in a log file. Usually it's one line that names your Blueprint, the function and the node.
This page shows which log to open, how to read a line, and which lines to skip. Search the log for your mod's folder name first, because every line about your mod contains it.
The short version
- Something misbehaves in the editor or in PIE? Open Window > Output Log, or the file
<DevKit>\Projects\ShooterGame\Saved\Logs\ShooterGame.log. PIE (Play In Editor) is the Play button's test session. - Search for your mod's folder name,
/<YourMod>/. Then search forBlueprint Runtime Error,Accessed None,Runaway loop,LogBlueprint: Errorand[Compiler]. - Read the first error, and the one that repeats most. A None that fires every tick floods the log. The first one usually causes the rest.
- Skip the noise every launch prints, unless it names your files.
- The editor crashed? Go to Reading a crash report.
- A cook or upload failed, or "succeeded" with a broken mod? Go to When a cook or upload fails.
- Redact a log before you post it. Server logs print the admin password.
Where every log lives
<DevKit> is the folder with RunEditorSDK.bat, Engine\, Projects\ and ModTools\ in it. <Game> is your ASA
install, the folder that holds ShooterGame\. <Server> is a dedicated server install.
| Log | Folder | Written by | Open it when |
|---|---|---|---|
ShooterGame.log |
<DevKit>\Projects\ShooterGame\Saved\Logs\ |
The editor, plus PIE's server and client, all in one file. | Anything in the editor or PIE. |
ShooterGame-backup-<date-time>.log |
same | Earlier editor sessions. | The editor crashed and you've restarted it. |
ShooterGame_2.log |
same | A second editor open at the same time. | You ran two editors. |
Cook-<date>_Worker<N>.txt |
<DevKit>\Engine\Programs\AutomationTool\Saved\ |
A local cook, one file per cook worker. | A local cook failed. |
Log.txt |
%APPDATA%\Unreal Engine\AutomationTool\Logs\<Drive>+<Folder>\ |
The AutomationTool (UAT), which runs cooks and the upload's prepare step. Overwritten every run. | An upload or local cook stopped with an ExitCode |
UnrealPak.log |
<DevKit>\Projects\ShooterGame\Saved\Logs\ |
The pak step of a local cook. | The cook got as far as packing. |
| CurseForge log zip | CurseForge, under Notifications | The cloud cooker, one set per platform. | CurseForge rejected your file, or the mod is broken live. |
ShooterGame.log (client) |
<Game>\ShooterGame\Saved\Logs\ |
The game, only when started with -log |
A cooked mod misbehaves in your own game. |
ShooterGame.log (server) |
<Server>\ShooterGame\Saved\Logs\ |
A dedicated server. | A mod misbehaves or crashes on a server. |
FailedWaterDinoSpawns.log |
same as the server log | The server's wild spawner. | Your spawn mod's creatures don't appear. |
All of these are plain text. The exception is the .crashstack files beside the editor log. They're UTF-16: Notepad
opens them fine, but grep-style tools show spaced-out letters.
The editor log (ShooterGame.log)
What you see: a file of about 1 MB per session, even if you only had the editor open. It's the same text the Output Log window shows.
Where to look: each time the editor starts, it renames the old log to ShooterGame-backup-<date-time>.log. So after
a crash and a restart, the crashed session is the newest backup. My DevKit keeps about ten.
What to do: mind the clock when you match times. Backup names and every log line use UTC. The file's first
line (Log file open, <date> <time>) and .crashstack names use your local time. In UTC-6, a crash at 00:22 shows
as 06.22 in the log.
Cook logs
Where to look: a local cook starts several cook workers through the AutomationTool. Each writes its own
Cook-<date>_Worker<N>.txt of around 640 KB. You start a local cook with the cooking-pot button in the toolbar, or with
<DevKit>\ModTools\Scripts\CookMod.bat.
What to do: read the end of each file; that's the useful part. The upload's prepare step writes only UAT's
Log.txt. The full walk-through is on When a cook or upload fails.
The CurseForge log zip
Where to look: when the cloud cook fails or ends with errors, CurseForge offers the logs under Notifications. There's one set per platform: Windows, Windows server and the consoles. Modders find the new site the more reliable place to download them. A very early rejection sometimes comes with no log at all.
What to do: the zip holds Cook-<date>.txt (the main one), Log.txt, Cooker_Output.log, UnrealPak-<date>.txt
and the pak and IoStore command lists. Read Cook-<date>.txt and Log.txt for each platform. They differ slightly.
The game client's log
What you see: crash files in <Game>\ShooterGame\Saved\Logs\, but no ShooterGame.log. My own game folder has 80
crash files and no log at all.
What it means: the shipping game only writes a log when you ask for one.
What to do: add -log to the game's launch options. In Steam that's Properties > Launch Options. A second console
window then shows the log live. Type it carefully: one modder crashed the game with a stray space there. Modders also
report that single-player leaves no file behind, so read the window while you play.
The dedicated server log
What you see: a short file, about 11 KB a run on my test server. A shipping server only writes key lines.
What it means: these are the lines to look for.
| Line | What it tells you |
|---|---|
ARK Version: <n> and Commandline: … |
The build and every launch option: map, ports, -mods=, -log, -servergamelog. This line contains the admin password. |
UShooterEngine::LoadGameMods with N mods |
How many mods the server actually loaded. |
LogCFCore: … |
The CurseForge mod library: where mods live, downloads, Detected an unavailable mod |
Initialize Primal Game Data Override. then No Primal Game Data Override, using default PrimalGameDataAsset. |
Whether a map mod's PrimalGameData loaded. That's the asset that registers a mod's content. |
Full Startup: N seconds and Server: "<name>" has successfully started! |
The server finished loading. If the last one is missing, it died during load: read the last lines and the .crashstack |
LogBlueprintUserMessages: … |
Your own messages, if you use Print Message in Shipping Build (below) |
How a log line is built
A normal line looks like this:
[2026.11.04-22.48.32:095][374]LogBlueprint: Error: [AssetLog] ...\<YourBlueprint>.uasset: [Compiler] ...
└ date and time (UTC) ms └ frame └ category └ verbosity └ message
- Timestamp: year.month.day-hour.minute.second:milliseconds, in UTC.
- Frame: the engine's frame counter. It's three characters wide and rolls over every 1,000 frames.
[ 0]means start-up or a blocking load. Lines that share a frame number happened in the same tick. That helps you tie a warning to the event that caused it. - Category: the part of the engine or game that wrote it, such as
LogBlueprint,LogScript,LoadErrorsorPIE. - Verbosity:
Fatal,Error,Warning,Display, then a plain level that isn't printed. A line with noError:orWarning:after the category is just information.
The first dozen lines of a log have no brackets. They're written before the timestamps switch on. Some messages run on to the next lines, indented with a tab or with no prefix at all. Accessed None does this.
The lines that matter
"Accessed None"
What you see: two linked messages during PIE.
[…][443]LogScript: Warning: Accessed None
<YourBlueprint>_C /<YourMod>/UEDPIE_0_<TestMap>.<TestMap>:PersistentLevel.<YourBlueprint>_C_0
Function /<YourMod>/<Folder>/<YourBlueprint>.<YourBlueprint>_C:<FunctionName>:<offset>
[…][443]PIE: Error: Blueprint Runtime Error: "Accessed None". Node: Branch Graph: <FunctionName> Function: <Function Name> Blueprint: <YourBlueprint>
Some versions say Accessed None trying to read property <VariableName>. That one names the empty variable too.
What it means: a node used an object reference that was empty, "None" in Unreal's words. An object reference is a variable that points at an actor, a component or a widget. The second line names the Blueprint, graph, function and node.
UEDPIE_0 in the first line means the PIE server world. UEDPIE_1 means the client. That alone often explains it.
A widget reference is None on the server, because widgets only exist on clients.
What to do: open Window > Message Log and its PIE section. Each Blueprint Runtime Error there links to its node. In UE5 the Message Log no longer pops up on its own. Then fix the order of things, so the reference is set before you use it. Or guard the node with an Is Valid check.
How bad it gets: the 507 log copies in my DevKit's crash folders hold 5,981 "Accessed None" lines. One node made
3,964 of them in a single session. It was a material update on a creature that ran every tick, before the creature's
mesh existed. That's why you read the first one and the most repeated one. Vanilla content throws a few too. A None
that doesn't name /<YourMod>/ isn't yours.
Blueprint compile errors
What you see: LogBlueprint: Error lines that end in a [Compiler] message.
LogBlueprint: Error: [AssetLog] <DevKit>\Projects\ShooterGame\Mods\<YourMod>\Content\<Folder>\<YourBlueprint>.uasset: [Compiler] In use pin Target no longer exists on node <SomeNode> . Please refresh node or break links to remove pin.
LogBlueprint: Error: [AssetLog] …\<YourBlueprint>.uasset: [Compiler] Could not find a function named "<SomeFunction>" in '<YourBlueprint>'.
Where to look: these lines appear whenever a Blueprint loads, not only when you press Compile. So after you start PIE, the log lists every broken Blueprint PIE touched. That includes ones you haven't opened today. They show up in cook logs too.
What it means and what to do: here are the messages I see most. My last 12 editor sessions hold 836 compiler lines.
| Message (shortened) | Cause | Fix |
|---|---|---|
Could not find a function named "<X>" in '<Other>_C' |
The function was renamed or deleted in another Blueprint. | Refresh the node, or pick the function again. |
In use pin <X> no longer exists on node <Y> |
The node's source changed: a dependency, another mod's library, an engine update. | Right-click the node > Refresh Node, then reconnect. |
Can't connect pins … Only exactly matching structures are considered compatible |
Two structs that look the same but are different assets, after one was duplicated or moved. | Use one struct everywhere. |
The current value of the 'In Array' pin is invalid: Array inputs must have an input wired into them |
An array pin left unwired after a change. | Wire it. |
Cannot find appropriate promotion from 'Wildcard' to '<Type>' |
A math or compare operator that UE 5.8 can't re-resolve. | Replace it with the typed function node. |
'' is not a valid enumerant of '<Enum>' |
An enum pin lost its value, often after an update. | Pick the value again. |
The variable UberGraphFrame cannot be declared in FunctionLibrary |
An event graph ended up in a function library. | Move the events out. |
Warning: Input pin X … no longer exists |
A renamed parameter. The pin silently keeps its default. | Reconnect it. Read warnings, not only errors (lessons §2) |
Warning: Usage of 'ItemIcon' has been deprecated, 'RequiresDLC' … Use RequiresDLC_Class |
ARK's API changed. | Switch to the new property. |
Warning: Blueprint /<YourMod>/<X> is missing GeneratedClass asset tag |
Saved without a compiled class. | Open, compile, save. |
Warning: missing NodeGuid … please resave package |
An old package. | Resave it. Most are vanilla; ignore those. |
The Compiler Results panel under the Blueprint graph lists the same messages as links. Clicking an "Unknown" entry there still jumps to the faulty node.
"Failed to load" and missing dependencies
What you see:
LoadErrors: While trying to load package /Game/…/<SomeAsset>, a dependent package /Game/…/<MissingAsset> (…) was not available.
LogUObjectGlobals: Warning: Failed to find object 'Class /Script/ShooterGame.<SomeClass>'
What it means: the LoadErrors line only matters when the first package is yours. Then the second package is
something you referenced that isn't there. It may be deleted, moved, another mod's asset, or DLC the DevKit doesn't
ship. In my logs, all 208 of these lines are vanilla content pointing at assets the DevKit lacks. They're noise.
The Failed to find object line means a native class your asset used is gone after an update.
What to do: right-click your asset > Reference Viewer. Everything it points at should be in your mod folder or the base game. References into other mods or DLC also break cooks: see When a cook or upload fails.
Runaway loops and endless recursion
What you see:
LogScript: Warning: Runaway loop detected (over 10,000,000 iterations) - see log for stack trace
PIE: Error: Infinite loop detected. Blueprint: <YourBlueprint> Function: <Node> Call Stack: Show
LogScript: Warning: Infinite script recursion (120 calls) detected
Where to look: if PIE closes on its own with no crash window, this is the usual reason. Read the yellow lines just before the end. The PIE line names the Blueprint and function.
What it means: a loop that never ends, or a function that calls itself. Think of a While with no exit, or a ForEach whose array grows as you add to it.
What to do: add an exit condition, or a counter that bails out. Sometimes the "loop" is a chain of events that rightly runs long in one frame. Spreading it over a timer stops the detector.
Corrupted assets
What you see:
LogSerialization: Error: Invalid boolean encountered while reading archive /<YourMod>/<Asset> - stream is most likely corrupted.
LogLinker: Fatal: … <Asset>: Serial size mismatch: Got 87, Expected 83
What it means: the saved file doesn't match what the engine expects. It usually ends in a crash, and opening that asset crashes every time.
What to do: follow Reading a crash report.
Other script messages worth knowing
| Line | Meaning |
|---|---|
Script Msg: A null object was passed as a world context object / No world was found for object (… Default__<X>_C) |
Code ran on a class default object, the copy of a Blueprint that holds its starting values. It has no world. Typical in skins and function libraries. |
Switch statement failed to match case for index property … |
A Switch on Int or Enum got a value with no pin. |
Script Msg: Divide by zero: Divide_DoubleFloat |
Exactly that. |
Script Msg: Attempted to set an invalid index on array … [0/0] |
Writing to an empty array. |
UNetDriver::ProcessRemoteFunction: Remote function <RPC> called from actor <X> while actor is being destroyed |
An RPC, a function sent across the network, aimed at an actor that's going away. |
Networking warnings in PIE
What you see: LogNetPlayerMovement: Warning: ServerMove: TimeStamp expired and
LogNet: Warning: Took too long to receive packets. I have over 10,000 of them in my logs.
What it means: they appear whenever PIE is paused, the editor stalls or you sit at a breakpoint.
What to do: ignore them, unless movement is visibly wrong.
The noise every launch prints
These lines appear in all 12 editor sessions I checked. They mean nothing for your mod, so learn to skip them.
| Category | What it says (shortened) |
|---|---|
LogWindows |
Failed to load 'aqProf.dll', 'VtuneApi.dll', 'WinPixGpuCapturer.dll': profiler DLLs you don't have. |
LogConsoleManager |
Console object named 'r.…' already exists but is being registered again |
LogClass: Error |
<Struct>::<Property> is not initialized properly, for about 19 engine and game structs. LogAutomationTest echoes it. |
LogRedpointEOSFriends: Error |
… not the EOS online subsystem |
LogDiscordVoice: Error |
Rich Presence update failed No application ID set |
LogStreamlineAPI, LogDLSS |
Upscaler errors on hardware or settings that don't use them. |
LogSimplygon: Error |
Simplygon DLL not present |
LogLiveCoding: Error |
Unable to start live coding session |
LogVirtualization |
Failed to connect to revision control server |
LogTargetPlatformManager |
Failed to load module 'IOSTargetPlatform', Mac, TVOS… |
LogPluginManager: Warning |
Plugin '<X>' requires engine version … |
LogBlueprint: Warning |
ExposeOnSpawn ambiguity, over 1,400 lines a session. |
LogLinker |
FLinkerLoad::FixupExportMap(): vanilla animation notifies being remapped. |
LoadErrors |
Vanilla packages whose dependencies aren't in the DevKit, like Atlas sounds and DLC engrams. |
LogScript: Error |
Script Msg: /Game/…/<VanillaAnim> : Unable to retrieve bone index for track, from vanilla animations. |
LogStreaming: Warning / LogShooter |
Failed to read file …/SavedArks/<Map>/….arktribe, ….gamedata, Unable to load tribe data. There's no saved PIE data yet; normal on a fresh test map. |
To put a number on it: in those 12 sessions, most Error-level lines were LogScript. Of its 302 errors, 300 were the
vanilla bone warning. LogAutomationTest and LogClass came next, at start-up. The only errors about mod content were
LogBlueprint errors and PIE runtime errors.
Some vanilla Blueprints also fail to compile in every kit. The PIE warning that lists them is ARK's own. Ignore it unless your file is in the list. My beginner guide video shows that first-PIE popup at 21:12.
Filtering the Output Log
Window > Output Log shows the same text as ShooterGame.log, live.
- Search box: type your mod's folder name, a Blueprint name or
Error. Other lines stay hidden until you clear it. - Filters: switch Messages, Warnings and Errors on or off, and pick Categories. To see only your own Print
String and Print Message output, show just
LogBlueprintUserMessages. That's Unreal's standard category for Blueprint prints. - Clear: clear the log before you press Play, so what you read belongs to this run. The Output Log's settings, under the gear, can also clear it on each PIE start.
- Long logs: open the file in a text editor instead. Notepad++ and VS Code handle a 1 MB log fine. They let you search, count matches and jump to the first one.
The window and the file are the same stream. The file is easier to search. The window shows colors: yellow for warnings, red for errors.
Adding your own messages
When the log doesn't say enough, make it say more. These nodes matter, and the difference catches everyone once:
| Node | Where its text goes | In a cooked mod (live game, server) |
|---|---|---|
| Print String | Screen and log, in the editor and PIE. | Gone. It's development-only, so shipping builds strip it. |
| Print Message in Shipping Build | The log of whichever side ran it. | On the server, it lands in the server's ShooterGame.log. On a client, it's in the -log window. |
| Log Print to Server Game Log (on the game mode) | The server game log. | Writes nothing unless the server runs with -servergamelog (lessons §3) |
Both ARK functions are in the DevKit's game code. Where their output lands comes from the community. One modder saw Print Message lines in a live server log.
I use this pattern, and the community recommends the same:
- Use one logging function. Put it in a Blueprint function library, with inputs for a level (Info, Warning, Error) and the message. Every Blueprint calls it; nothing calls Print String directly. To change how logging works, you change one function.
- Put a prefix on every line:
[<YourMod>][<Level>] <where>: <message>. A search for[<YourMod>]then finds every line you wrote, on any machine. Starting the text withWarning:orError:reportedly colors it in the Output Log too. - Add a debug switch. Your mod reads a setting from the server's ini file, say
bDebugLogging, off by default. Info lines print only when it's on; warnings and errors always print. You can then ask a server owner to switch it on and send you the log, without shipping a chatty mod. - Say which side you're on. PIE puts
Server:orClient 1:in front of prints, but cooked builds don't. If it matters, add it yourself with a Switch Has Authority before the print.
A line from that pattern looks like this in the log:
[2026.11.03-21.06.01:802][363]LogBlueprintUserMessages: [<YourBlueprint>_C_0] Server: [<YourMod>][INFO] Boot: settings loaded
The ini setting is on How to run global logic, and the server-side test is on Testing your mod.
Redacting a log before you share it
Logs say more about you than you'd think. Before you paste one into Discord or a bug report, open it in a text editor and search for these:
| Search for | Why |
|---|---|
Commandline, ServerAdminPassword, Password |
A server log prints its full command line, admin password included |
key, token, Sentry |
Server logs also print service keys in clear text. |
Your public IP, Multihome, ports |
Server and client logs carry addresses. |
C:\Users\ |
Paths include your Windows user name. |
| Your PC's name | Editor crash footers include it, like <PC name>-PIE-1 |
| Your Steam or EOS name and IDs | Login lines in client and server logs. |
Replace each with a placeholder like <password>, <user> or <ip>. Don't delete the line: helpers can then still
see that the value was set. Your mod's folder and asset names are fine to leave in. They're what the helper needs.
Send the right part, too: the 30 to 50 lines before the first error. Not just the one red line, and not the whole 1 MB file pasted into a chat.
Watch
No video in my library teaches log reading; that's why this page exists. Related:
- How to Make an ARK ASA Mod (Complete Beginner Guide) (my video, 21:12: testing in PIE, the first-PIE error popup about assets that aren't yours, and the ModDataAsset cache reset)
Go deeper
- Reading a crash report: the
.crashstack, the crash folder and the five crash families - When a cook or upload fails: cook logs, the summary block and the known killers
- Works in PIE, not on a server: why a clean PIE log doesn't prove a server works
- Modding lessons §2 and §3: the silent Blueprint failures that never reach the log
- Testing your mod: PIE, then a local dedicated server
- Symptom index: start from what you see when you don't know which page covers it
Sources
- My own logs, read-only on 2026-11-05: 12 recent DevKit editor sessions (2026-10-20 to 2026-11-05), the 507 log copies in the DevKit's crash folders (May 2025 to November 2026), the ASA client's log folder and a local dedicated server's logs. Every count on this page comes from those files. Example lines are rebuilt with placeholders.
- Checked in those files on 2026-11-05: the
.crashstackencoding (UTF-16); the number of editor backups; UTC versus local time (compared a crash file with its session log); the frame counter; the server log's size and key lines; the 208LoadErrorslines; the 836 compiler lines in 12 sessions; the 10,000+ networking warnings; and the noise table (12 of 12 sessions). - Print Message in Shipping Build and Log Print to Server Game Log: found in the DevKit's game module, 2026-11-05.
- Modding lessons §2 and §3: the PIE worlds (
UEDPIE_0,UEDPIE_1) and-servergamelog. - From the community, not yet confirmed in the DevKit by me:
- the Message Log no longer popping up in UE5, "Unknown" Compiler Results entries still jumping to the node, runaway
loops closing PIE, vanilla Blueprints failing to compile in every kit, and the
Warning:/Error:prefix coloring a print (2025); - CurseForge log downloads from the new site, and early rejections with no log (June and September 2026);
- client logs needing
-log, single-player leaving no file, and the stray-space crash (January 2025 and May 2026); - filtering to
LogBlueprintUserMessages(2024); - Print Message lines in a live server log (July 2024 and March 2026);
- the one-function, prefix and debug-switch logging pattern (May 2026), and cooked builds not adding
Server:orClient 1:(2026); - the meaning of the invalid-array-index message.
- the Message Log no longer popping up in UE5, "Unknown" Compiler Results entries still jumping to the node, runaway
loops closing PIE, vanilla Blueprints failing to compile in every kit, and the
- Community knowledge from the ARK Modding Community Discord (discussions from July 2024, January 2025, mid-2025,
March 2026, May 2026, June 2026 and September 2026), found with Overseer.
Threads used (they open for server members):
- Accessed None lines and the Message Log in UE5 (June 2025)
- Print Message in Shipping Build, a prefix and a debug flag (May 2026)
- Server log nodes and
-logfor clients (November 2023) - Filtering the Output Log to LogBlueprintUserMessages (June 2024)
- Single-player and client logs need
-log(January 2025) - Cook issues: basic troubleshooting (CurseForge log downloads) (June 2026)
Where this page's information comes from
Applies to: ASA DevKit as of November 2026 (UE 5.8.1); ASE where noted
my own DevKit, game and server logs; the modding Discord (see Sources)