When a cook or upload fails
15 min readASA DevKit as of November 2026 (UE 5.8.1); CurseForge's cloud cook as of 2026
Cooking turns your editor assets into the packed files the game loads, once per platform. CurseForge does it in the cloud after you upload. You can also cook on your own PC to test, which is called a local cook.
When a cook goes wrong, you get a line like ExitCode=3, or a CurseForge notification that just says "Rejected".
Neither tells you why. The reason is in a cook log, almost always in a line that names one of your own files.
This page shows where those logs are, how to find that one line, and the handful of problems behind most failures. It also covers the worse case: CurseForge says the cook succeeded, and the mod is broken anyway.
For logs in general, see Reading ARK's logs. If the cooker itself crashed, read its stack as in Reading a crash report.
The short version
- Treat any
ExitCodebut 0 as "look in the log". Don't search the web for the number. - Get the cook log. For a local cook, it's
Cook-<date>_Worker<N>.txtin<DevKit>\Engine\Programs\AutomationTool\Saved\. For CurseForge, download the log zip under **Notifications**. ReadCook-<date>.txtandLog.txtfor each platform. - Jump to the end. Read the
Warning/Error Summary (Unique only)block, and search for=== Critical error: ===. - Search for your mod's folder name. Only lines that mention
/<YourMod>/or your files count. The standard noise doesn't. - Check the known killers: a path over 260 characters, a folder named
Windows, references outside your mod or into DLC, old Cascade particles. - Cook "succeeded" but things are missing in game? Read the log anyway. CurseForge accepts cooks full of errors.
ExitCode lines mean "look in the log"
What you see: a line like these at the bottom of the cook window or the UAT output.
UnrealEditor-Cmd.exe … ExitCode=3
AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)
Where to look: the real cause is earlier in the log, usually above a stack dump.
What it means: the cooker stopped with a failure, and the AutomationTool passed it on. That's all. The AutomationTool (UAT) is the program that runs cooks and the upload's prepare step. Nobody on the community Discord has pinned down what 3 means beyond "the cooker reported failure".
A few codes do carry information, because they're Windows crash codes rather than cook results. The negative number is the Windows status code, written as a signed integer.
| Exit code | Hex | Meaning |
|---|---|---|
0 |
Success. That still doesn't mean the mod works (see below) | |
3 (cooker), 25 (UAT) |
The cook failed; read the log. | |
-1073741819 |
0xC0000005 |
The cooker crashed with an access violation. Read the Critical error block. |
-1073740940 |
0xC0000374 |
Heap corruption inside the cooker. It's a crash, not a content message as such. Read what it was cooking just before. |
-1073741571 |
0xC00000FD |
Stack overflow in the cooker. |
One historical case: in early 2024, local cooks stopped after the Windows Client job with No project file specified
and ExitCode=1. The server zip was never rebuilt. DevKit v38 fixed it. If the server zip in your output folder has an
old date, check you're not on an ancient kit.
Where the cook logs are
A local cook
What you see: the cooking-pot button in the toolbar and <DevKit>\ModTools\Scripts\CookMod.bat run the same thing.
It's UAT's BuildPlatformUGC for Windows Client and/or Windows Server, with your mod's folder name and a number of cook
workers. The script's default is 3 workers, and it recommends 1 to 5 on a home PC. Modders estimate about 5 GB of RAM
per worker.
Where to look:
| File | Where | What it holds |
|---|---|---|
Cook-<date>_Worker<N>.txt |
<DevKit>\Engine\Programs\AutomationTool\Saved\ |
One per cook worker, about 640 KB each, named by the cook's start time. The summary block is at the end. Read every worker's file: an error is only in the log of the worker that cooked that asset. |
ResponseFiles\PakList_<YourMod>pakchunk0-Windows.txt and PakListIoStore_… |
same folder | The exact list of files that went into the pak. |
Log.txt |
%APPDATA%\Unreal Engine\AutomationTool\Logs\<Drive>+<Folder>\ |
UAT's own log, overwritten every run: the commands it ran and the final ExitCode. The folder is your DevKit path with :\ turned into +, like D+ARKDevkit. |
UnrealPak.log |
<DevKit>\Projects\ShooterGame\Saved\Logs\ |
The pak step. |
<YourMod>-Windows.zip, server zip |
<DevKit>\ModTools\Output\<YourMod>\ |
The result. |
What to do: use the pak list to check that an asset really made it in. The cooker packs everything inside your mod
folder, referenced or not, so a missing file usually lives outside it: in another mod's folder, an old folder you
renamed, or /Game (lessons §1).
What it means for the cloud: a local cook sees everything in your DevKit, including other mods' folders. The cloud cooker only has the game's own files. So a local cook can pass, or quietly pull in another mod's file, where the cloud cook fails. Treat a clean local cook as a good sign, not proof.
The upload's prepare step
What you see: when you upload, the DevKit first runs UAT's PackageUGC -Prepare=true for your mod. It packs your
source into <DevKit>\ModTools\Output\<YourMod>-Source.zip.
Where to look: if the upload fails before it ever reaches CurseForge, read UAT's Log.txt.
What it means: a clean run takes about a second. It ends with BUILD SUCCESSFUL and
AutomationTool exiting with ExitCode=0 (Success). Lines like Unable to find valid SDK(s) for Android/IOS/Linux are
normal.
CurseForge's cloud cook
What you see: your file's status goes processing, cooking, ready for review, approved. A cook takes from half an hour to many hours. Maps take longest.
Where to look: when a cook fails or ends with errors, the logs are in CurseForge's Notifications. Modders recommend downloading them from the new site. The zip holds these files:
| File | Use |
|---|---|
Cook-<date>.txt |
The main one: everything, with the warnings and errors summarized at the end. |
Log.txt |
UAT's log. Check it as well; it differs slightly. |
Cooker_Output.log |
The cooker's console output. Read it from the bottom up after a rejection. |
UnrealPak-<date>.txt, PrePak_*, PakCommands.txt, IoStoreCommands.txt |
The packing steps. They only matter when the failure is there. |
What to do: read the set for the platform that failed. Windows, Windows server and each console get their own set. So a Cross-Platform mod can fail on one platform and not another.
Reading a cook log
The Warning/Error Summary block
What you see: this block near the end of each cook log.
LogCore: Engine exit requested (reason: Commandlet CookCommandlet_0 finished execution (result 0))
LogInit: Display: Warning/Error Summary (Unique only)
LogInit: Display: -----------------------------------
LogInit: Display: LogDerivedDataCache: Error: Cloud: Missing required parameter 'Host'
LogInit: Display: LogSimplygon: Error: Simplygon DLL not present(Simplygon.dll) - disabling
LogInit: Display: LogBlueprint: Error: [AssetLog] …\<YourMod>\Content\<Folder>\<YourBlueprint>.uasset: [Compiler] … ← this one is yours
...
What it means: every unique warning and error of the whole cook, listed once. result 0 in the exit line means the
cook commandlet finished. It doesn't mean there were no errors.
What to do: read the summary top to bottom, and pick out the lines that mention your mod. Then search the full log for that line to see its context: what was being cooked just before. Don't just search the file for "fail". Modders point out that this lands on harmless lines and misses the summary. One experienced helper's rule of thumb: more than about three unique errors in the summary means real trouble.
Critical error blocks
What you see:
LogWindows: Error: === Critical error: ===
LogWindows: Error: Assertion failed: <condition> [File:…\<Something>.cpp] [Line: N]
LogWindows: Error: [Callstack] 0x… <module>!<Function>() […]
What it means: the cooker crashed, and this is its crash report. Read it like a .crashstack
(Reading a crash report): the error line, then the first real frame. The
source file in the assertion names the subsystem.
| File in the assertion | Where it broke |
|---|---|
BlueprintGraph, K2Node_…, Kismet… |
A Blueprint node. |
LinkerLoad, CoreUObject |
Loading or saving a package, often a corrupted asset. |
IoStoreUtilities, PackageStoreOptimizer |
The packaging step after cooking. |
ShooterGameState and other Shooter… |
ARK's own game code. |
AnimMontage, AnimSequence… |
Animation assets. |
Map.h with Pair != nullptr |
A lookup that found nothing. One helper's theory is memory pressure from Nanite or Control Rig assets, since non-map mods cook with a lower memory limit. Check for garbage collection (GC) lines just above. |
What to do: scroll up from the block. The last asset named before it is your suspect.
Not every assert stops the cook. LogOutputDevice: Warning: Script Stack or Handled ensure: with a callstack is a
logged warning: the cooker noted something odd and carried on. Only an Assertion failed or Fatal error under
=== Critical error: === stops it.
Lines that name your own files
What to do: search the log for each of these, in this order. It's the list modders on the Discord settled on, plus my own.
| Search for | Finds |
|---|---|
your mod's folder name, /<YourMod>/ |
Everything about your files. |
[Compiler] |
Blueprint compile errors: LogBlueprint: Error: [AssetLog] <path>\<YourBlueprint>.uasset: [Compiler] <message>. They're the same messages as in the editor (table) |
Critical error |
A cooker crash. |
Couldn't save package |
Usually a path that's too long. |
SkipPackage: /<YourMod> and Skipping non mounted imported package |
A file that references another mod. It's left out of the cook. |
missing, dependenc, Failed import |
References to files that aren't there. |
LogShaderCompilers |
A material that won't compile for the target, with the material's name. |
If an error or warning doesn't mention anything of yours, you can almost always ignore it.
The standard noise
These appear in every cook, including perfectly good ones:
LogDerivedDataCache: Error: Cloud: Missing required parameter 'Host'LogUObjectGlobals: Error: Ignored DoNotCreateDefaultSubobject for BrushComponent0 …LogSimplygon: Error: Simplygon DLL not presentLogTemp: Warning: Plugin 'OnlineSubsystemRedpointEOS' is disabled in PIE.LogPluginManager: Warning: Plugin '<X>' requires engine version …, for a dozen pluginsLogConfig: Warning: Found a deprecated '…/Base<Plugin>.ini'LogCoreRedirects: Warning: AddRedirect(Engine) found duplicate redirects for …, dozens of themLogWindows: Failed to load 'aqProf.dll'and the other profiler DLLs at the top- Map cooks:
LogCook: Warning: Could not resolve package /Game/Maps/TheIslandSubMaps/…_WP/_Generated_… - A
Failed importon a vanilla material that points at an old font texture. A modder confirmed it didn't stop a cook. - Locally,
UnrealPak.logfailing on a missing console plugin (XB1Zlib). The public DevKit doesn't ship console platform plugins.
Errors inside the base game's own files are normal in every cook. If nothing after the noise mentions your files, the cook log isn't where your problem is.
The known killers
A path over 260 characters
What you see: Couldn't save package, filename is too long (290 >= 260), naming one of your assets.
What it means: Windows' classic path limit is 260 characters. It counts the whole path, including the cloud
cooker's own long working-folder prefix in front of …\Mods\<YourMod>\Content\…. The length the editor's tooltip shows
is not what the cooker sees. So you can be "under 260" in the editor and still fail.
What to do: shorten folder and asset names, and nest fewer folders. Short mod-tag prefixes keep you well clear:
<Tag>_Item_Sword rather than <YourModFullName>_Items_Weapons_Melee_Sword. Rename inside the editor, then
right-click your mod folder > Update Redirector References. Never do that on the whole Content root: one modder had to
reinstall their kit.
A folder named "Windows"
What you see: a rejected cook, often only on Cross-Platform, with nothing obviously wrong.
What it means: Unreal's packaging reserves some folder names, because it uses platform names as folder names inside
the cook. One modder's folder called Windows, holding window meshes for a building set, broke the cook. Renaming it
fixed it. An earlier report found reserved names only hurt Cross-Platform cooks, not PC-only ones.
What to do: don't name folders after platforms or build words: Windows, WindowsServer, Linux, PS5, XSX,
Android, IOS. I haven't found the full list documented anywhere. Only Windows is confirmed; the other platform
names are my inference.
References outside your mod
What you see: this line in the cook log:
LogStreaming: Display: ImportPackages: SkipPackage: /<YourMod>/<Asset> … - Skipping non mounted imported package /<OtherMod>/<Asset>.
In game, the asset that referenced the other mod is simply missing. You get no multi-use entries, a buff that never
applies, or a Blueprint that fails to compile on CurseForge.
What it means: your asset has a hard reference to a file in another mod's folder: a variable type, a cast, a struct or an enum. The cloud cooker only has the game's files. It can't mount that mod, so it skips your asset.
The same happens after you move files from an old mod folder to a new one, if references still point at the old path. The cook passes, and the class is broken.
What to do: right-click the Blueprint > Reference Viewer. Hover over everything on the right, which is what
your asset references. Each path must be in /<YourMod>/ or in the base game (/Game/…). Copy what you need into your
own folder and re-point the references. Don't hard-reference other mods at all: a dependency on another mod breaks
whenever that mod changes.
References into DLC or content the client doesn't ship
What you see: the mod cooks, but players without a DLC can't use it, or CurseForge marks it as requiring a DLC. Or textures and materials are missing in the live game, though they look fine in the kit.
What it means: the DevKit contains content the game doesn't ship to everyone. That's DLC maps and creatures, plus unused or developer assets that aren't in the client at all. Referencing DLC content can make your mod require that DLC. Referencing an asset that isn't in the client leaves a hole where it should be. Even vanilla packages in my editor logs point at Atlas sounds and DLC engrams the DevKit doesn't have.
What to do: check with the Reference Viewer, as above. For a vanilla asset you're unsure about, check the game's manifest of shipped files; my video below shows how. Or copy the mesh, texture or material into your mod. The February 2026 kit update removed DLC packages to save space, so re-enable the DLCs you need in the Epic launcher's install options.
Legacy particles (Cascade)
What you see: an error naming an old particle system, such as Name … is not mapped when saving … on a
ParticleModuleColorOverLife. It's typical in assets ported from ASE.
What it means: Cascade, Unreal's old particle system, has modules that don't cook deterministically in this engine. Old particles also cause load crashes in the kit.
What to do: remove the named particle system, or rebuild the effect in Niagara, the current particle system.
A backend type changed under you
What you see: compile errors in the cook log for Blueprints that compiled fine last week. For example, an array of Primal Item Class References isn't compatible with an array of Primal Item Soft Class References.
What it means: a game, kit or cooker update changed a type your Blueprint uses. The January 2026 cooker update, for example, switched supply crate item entries to soft class references. The cooker on CurseForge can be newer than your DevKit for a while.
What to do: compare your DevKit version with the cooker version CurseForge reports. Yours is at the top right of the editor, and on the Epic launcher tile. Rewire to the new type, or wait for the matching kit update. After any update, check lessons §6.
CurseForge says success but the mod is broken
This is the worst one, because nothing tells you. CurseForge only rejects a cook when the cooker crashes. A cook full of compile errors, skipped packages and missing references is reported as a success. Many modders see "File cooked successfully" and never read the log.
What you see: it works in the DevKit and PIE, but not in the live game. Items, engrams or multi-use entries are missing. Textures or materials are missing or gray. The mod suddenly requires a DLC. Or a Blueprint's logic doesn't run at all.
Where to look: download the cook logs from CurseForge's Notifications, even after a success. Then run through Lines that name your own files.
What it means: a [Compiler] error on one of your Blueprints means that Blueprint shipped broken. And a broken
Blueprint often does nothing at all, not just the broken part (lessons §2).
If the log is clean: it may not be a cook problem. Look at what the shipping game does differently. BPLoadClass
and BPLoadObject don't work in shipping builds. Soft references the kit had already loaded aren't loaded live. Print
String is stripped. Those are on Works in PIE, not on a server.
Rejected, and no log
What you see: a Notification that your file was "Rejected", sometimes only "Started Cooking from Source File", and no log link.
What it means: modders report that very early rejections can come without logs. Some are on CurseForge's side rather than the mod's. In one case, a comment-layout plugin saved its data into an asset, and that caused rejections. Duplicating the asset and deleting the original fixed it.
What to do: run a local cook. It shows errors the notification doesn't. If the local cook is clean, try the upload once or twice more. Then contact CurseForge support with the file name and date.
Watch
No video in my library walks through a failed cook. These help with the parts around it:
- How to Make an ARK ASA Mod (Complete Beginner Guide) (my video, 25:01: the upload, Cross-Platform versus PC Only; 29:35: CurseForge statuses and where the files are; 37:33: cook times and publishing)
- How to Find Blueprint Paths Using Manifest Files (Mods & Base Game) (my video: checking which game files actually ship, before you reference one)
- Modding: Publishing a mod (Mist3r Trixt3r, 23:15: Share Mod, the upload, "processing" and cook times)
Go deeper
- Reading ARK's logs: the log line format, compile errors and the editor's noise
- Reading a crash report: when the cooker or your test server crashes, and testing a local cook on a local dedicated server
- Your first mod, start to CurseForge: the upload, step by step
- Works in PIE, not on a server
- Modding lessons §1 and §6:
ExtraResources, package names, engine updates - Symptom index: start from what you see, such as an
ExitCodethat isn't 0 or a mod that works in the kit but not live
Sources
- My own DevKit, read-only on 2026-11-05:
ModTools\Scripts\CookMod.bat, a local cook's worker logs and pak lists (2026-10-19), UAT'sLog.txtfor an upload prepare,UnrealPak.log, theModTools\Outputfolder and 12 recent editor logs. Lines are rebuilt with placeholders. - Checked in those files on 2026-11-05: the cook script's default and recommended worker counts; the local cook's log
files and folders; the upload prepare step;
result 0in the summary's exit line; the first group of standard noise (from my local cook of 2026-10-19); the missing console plugin inUnrealPak.log; and the vanilla packages pointing at content the DevKit lacks. - Windows status codes: Microsoft's NTSTATUS values (
0xC0000005,0xC0000374,0xC00000FD). - Modding lessons §1, §2 and §6.
- Cook times and statuses: my beginner guide video, 29:35 and 37:33.
- From the community, not yet confirmed by me:
- the meaning of
ExitCode=3(2023 to 2026), and theNo project file specifiedbug fixed in DevKit v38 (March 2024); - about 5 GB of RAM per cook worker (2023);
- why a local cook can pass where the cloud cook fails (February 2024);
- the CurseForge zip's contents (2023 to 2026), and downloading logs from the new site (June 2026);
- not searching for "fail", and the three-errors rule of thumb (2024);
- which assertion file means what, the memory-limit theory, and non-fatal ensures (2023 to 2026);
- the search list for your own files (June 2026);
- map-cook noise (2024 to 2025), and the harmless failed import (January 2024);
- paths over 260 characters (2025 and June 2026), and Update Redirector References on the Content root (2024);
- reserved folder names (January 2024 and June 2026);
- references into other mods (2024 to March 2026), and into DLC or unshipped content (2024 to 2026);
- the February 2026 kit update removing DLC packages;
- Cascade modules that don't cook (2025);
- supply crate entries switched to soft references (January 2026);
- CurseForge accepting cooks with errors (2024 to 2026);
- rejections with no log (December 2024 and September 2026), and the comment-layout plugin case (December 2024).
- the meaning of
- Community knowledge from the ARK Modding Community Discord (discussions from November 2023 to September 2026, chiefly
2024 to 2026), found with Overseer. Threads used (they open for server members):
- Cook issues: basic troubleshooting (June 2026)
- Search the log for Error and Critical error; the memory-limit theory (December 2024)
- Filename too long and a non-deterministic particle module (March 2025)
- CurseForge accepts cooks with errors; read every log (February 2025)
- The summary block and the standard noise lines (March 2026)
- Which file in the CurseForge zip; read from the bottom up (March 2026)
- Skipping non mounted imported package: a reference into another mod (March 2026)
- Local versus cloud cook: why a local cook can pass (February 2024)
- Reserved folder names and a harmless failed import (January 2024)
- Loot sets changed to soft references by a cooker update (January 2026)
- Rejected with no log (September 2026)
Where this page's information comes from
Applies to: ASA DevKit as of November 2026 (UE 5.8.1); CurseForge's cloud cook as of 2026
my own cook, UAT and pak logs; the modding Discord (see Sources)