Publishing and updating your mod (and living with ARK updates)
12 min readASA DevKit as of November 2026 (UE 5.8.1); CurseForge's cloud cook as of 2026
Uploading a mod once is the easy part. Your first mod walks through that first upload click by click. This page covers everything after it: what happens between Share Mod and players, how to update without wiping anyone's base, and how to keep a mod alive when ARK, the DevKit or CurseForge's cooker changes under you.
- You'll learn: the path from upload to live, safe and unsafe changes, and a routine for every ARK update
- Time: an hour to read and set up; then 30 minutes to a day per release, mostly waiting
- Level: beginner (you've made your first mod)
- You'll need: a mod that passed testing, and a CurseForge account
From upload to live
Every release goes through the same stages. Most of the waiting is out of your hands.
| Stage | Where you see it | How long |
|---|---|---|
| Upload | the Share Mod window | seconds to minutes, by size |
| Processing, then cooking | your project's Files tab and the bell | minutes for a small mod; up to 12 hours, maps longest |
| Ready for review | Files tab | until you press Publish |
| Under review | Files tab | about an hour for most updates; days for a new project or a flagged file |
| Approved | the file goes live; no notification | servers pick it up on their next restart |
A "Rejected" status during cooking usually means the cook failed. That's When a cook or upload fails.
The process
Run the pre-publish checks. Don't repeat them from memory; use the list.
Show me how
- Before you publish: a short checklist covers the tests, from a real mod name to a
-devrun. - Lessons §9 has the long version: no debug keys, no Print String, textures capped, ini keys documented.
- On an update, add one more check: compare your asset list with the last release. Anything renamed, moved or deleted needs the save rules below.
- Before you publish: a short checklist covers the tests, from a real mod name to a
Upload with UGC → Share Mod. The first upload creates the CurseForge project. Every later upload adds a new file to the same project.
Show me how
- Your first mod, step 8 shows each field of the first upload.
- The project gets a number, the project ID. Servers load your mod by it (
-mods=<ProjectID>). It's on your project page. - The window then says which project the mod is linked to, with a link to change it. Leave that alone.
- Keep the platform you chose the first time. Switching between PC Only and Cross-Platform causes trouble for some mods. If you need the other platform, the upload window's reset mod link starts a new CurseForge project (a creator's walkthrough); some modders keep a PC-only test project that way.
- Write the changelog in the window. It shows on the file in CurseForge.
- Mod Version on upload counts your uploads. After restoring a backup it can show a stale number; modders report it corrects itself.
Wait for the cook, then read its log anyway. A "successful" cook can still ship broken Blueprints.
Show me how
- The bell icon and the Notifications list show each status change, platform by platform.
- Download the cook log zip from Notifications even when it says success. CurseForge only rejects a cook when the cooker crashes.
- Search the log for your mod's folder name and
[Compiler]. Lines that name your own files lists the rest.
Test the cooked file before you publish it. Load it on a server with
-dev, or from My Mods in single player. Testing on a server before you publish has the steps.Show me how
- The CurseForge build is the only one that shows what CurseForge's cooker did. Local cooks can differ.
- The steps are in Testing your mod, step 8 and Your first mod: check it worked.
Press Publish on the "ready for review" file. It goes to CurseForge's moderators. The first time, also publish the project itself.
Show me how
- Manage files on the legacy site: change
wwwtolegacyin your project's address. It has buttons the new site lacks. - On the Files tab, the newest file is at the top. Press the orange Publish button on it.
- A project can only go public with an approved file behind it. The first time, also press Publish project.
- Release Options in the Share Mod window can publish the file automatically once approved.
- Approval arrives without a notification. The file simply becomes the live one.
- Manage files on the legacy site: change
Plan around the moderators' hours. Moderation runs on a weekly schedule, first in, first out.
Show me how
- As CurseForge has posted it to authors, moderation runs Sunday to Thursday in its own time zone, with nothing on Friday or Saturday.
- Updates to an approved project usually clear in about an hour. New projects, and files flagged for a manual look, take one to three working days.
- In my experience approvals land overnight for US time. An update sent Thursday evening can sit until Sunday.
- Moderators check content against CurseForge's and the console platforms' rules. One that catches modders: never sell in-game currency or advantages for real money. CurseForge's support site is the authority, not my summary.
Post your version notes once the file is live. Write them for server owners first: what changed and whether they need to do anything.
Show me how
- I post the notes after approval. Before that, players can't get the update yet.
- Say clearly when an update needs a server restart, changes ini keys, or retires content.
- Edit the description on the new site. The in-game mod browser can show it very differently; if it looks right in game, leave it.
What players and servers see after an update
A server checks CurseForge for mod updates when it starts. A running server keeps the old version until it restarts. Players' games then match the server's version when they join, even if that means an older one.
The client side is less tidy. A player's game sometimes half-applies an update. The mod then fails to load, as if missing: no modded engrams, creatures or icons.
What I tell players:
- Restart the game after any mod update. Returning to the main menu isn't enough.
- Update from the Mods menu → Installed Mods, rather than by joining a server.
- If it's still broken, reinstall the mod: uninstall, restart, install, restart.
- Never play a single-player world without the mod loaded. Modded things in it are lost.
Players moving between servers with different versions of your mod hit bugs. Clusters should update every map at once.
Updating without breaking saves
Saves store your classes by their path, and your variables by name. Change either after release and old saves lose what they held.
| Change | Safe after release? | What happens to existing worlds |
|---|---|---|
| New values, logic, meshes, icons, sounds | yes | the new version loads next restart |
| New assets, engrams and Mod Data Asset entries | yes | they simply appear |
| A new SaveGame variable | yes | old saves load it at its default; don't overwrite it on load |
| Renaming or deleting a SaveGame variable, or changing its type | no | the saved value is gone |
| Renaming, moving or deleting a structure, creature or item class | no | every placed copy and every copy in an inventory disappears |
| Changing a class's parent | avoid | modders disagree on what survives; nobody calls it safe |
| Switching PC Only and Cross-Platform | avoid | trouble for some mods |
| Renaming the mod's root folder | impossible | that's a new mod |
Modders call it things going "poof": the class at the old path is gone, so the server drops it. The editor's redirectors fix references inside your kit. Modders report they don't save players' bases.
To retire content, keep the class. Remove its engram, spawns and loot entries, but leave the Blueprint. To replace a class, add the new one beside it. Swap old copies on load, or ask players to replace them. Delete the old class much later, after warning everyone.
Warning
Fix your folder layout before the first release. Once players have placed something, its path is fixed for good.
Living with ARK and DevKit updates
Three things update, not one
The game, the DevKit and CurseForge's cooker all update on their own schedules. Most update trouble comes from them being briefly out of step.
| What updates | Where | What goes wrong |
|---|---|---|
| The game | Steam, consoles, servers | your mod's behavior changes, or it crashes, without you touching it |
| The DevKit | the Epic launcher | your Blueprints need fixes before the next upload |
| The cloud cooker | CurseForge | your upload cooks against types your kit doesn't have yet |
Your DevKit version is at the top right of the editor and on the Epic launcher's tile. Compare it with the cooker version CurseForge reports.
- Kit newer than the cooker: The upload window refuses, saying the cooking tools haven't been updated. A beta-branch kit always hits this. After a normal kit update, wait for CurseForge.
- Cooker newer than the kit: The cook log shows compile errors for things that compile in your kit. The January 2026 cooker update, for example, changed supply crate item entries to soft class references. Rewire to the new type, or wait for the matching kit.
- The game is newer than the cooker. Modders saw materials go missing after a game update. Re-cooking didn't help until the cooker was updated too.
What updates tend to break
- Events you override: When an event gains parameters, your override needs a refresh and a recompile. The UE 5.8.1 update did this to the hurt-animation override and the AI's changed-target event.
- Properties that were replaced: The same update swapped five ship-ramming properties for a new model. Old values were silently lost, with no warning.
- Types under the hood: A hard reference becomes a soft one, and your wires no longer fit.
- Where values live: The 2025 move of many settings into sparse class data broke mods that set them per actor.
- Pins: An enum pin can lose its chosen value, and a renamed pin only warns. Both fail quietly.
- Kit content: The February 2026 kit update removed DLC packages to save space. Re-enable the DLCs you need in the launcher's install options.
- Saves: A UE 5.8 server upgrades an older save and keeps a backup. Back up your test worlds first.
Some breakage is Wildcard's to fix. Custom weapon animation Blueprints have broken and been fixed several times. If many modders report the same thing, wait for a fix. Lessons §6 lists the 5.5.4 to 5.8.1 changes.
Updating the kit
- Copy your mod folder first. It's
<DevKit>\Projects\ShooterGame\Mods\<YourMod>. The same copy lets you reinstall the kit from scratch. - Update through the Epic launcher, on the normal branch. Check the install options for DLCs you reference.
- Check your launch flags. If you added any to
RunEditorSDK.bat, make sure they're still there. - Let the first launch finish. It recompiles shaders and loads for a long time.
After each update: a checklist
- Read the patch notes and the community Discord's update channel.
- Compare your kit version with the cooker version.
- Open the kit and filter the Output Log for your mod's folder name. Read every error and warning.
- Open each Blueprint that overrides a vanilla event. Refresh changed nodes, compile and save.
- Re-check values on any class whose properties changed.
- Test in PIE as two clients, then on a local server with a backed-up save.
- Upload a fresh build once the cooker matches, even if nothing changed. Modders report a fresh cook cured crashes after a game update.
- Read the cook log, test with
-dev, publish and post the notes.
Note
When ASA moves to a new engine version, CurseForge re-cooks every published mod itself, in batches. For UE 5.8 the cooking servers went offline when the beta DevKit came out, mods with serious problems went on a list sent to their authors, and Wildcard reported 99.9% of mods re-cooked and checked before launch. Your mod can still break in ways a cook doesn't catch, so test it again after every big update.
Common mistakes
CurseForge says the cook succeeded, but the mod is broken
The cook only fails when the cooker crashes. Read the log for your own files: CurseForge says success but the mod is broken.
The old version still loads after my update
Check the file is approved, not just ready for review. Then the server must restart, and so must players' games.
Players say my mod isn't loaded after an update
Their install half-updated. They restart the game, or reinstall the mod as above.
My mod disappeared from search, or servers can't load it
Moderation may have hidden it. A thin description is a common reason. Fix what the notice names and wait for the review; you can't publish updates meanwhile.
My update has sat under review for days
It's in the manual queue, or it arrived before CurseForge's weekend. Check CurseForge's announcements for delays.
Placed structures vanished after my update
You renamed, moved or deleted their class. The installed mod's manifest files list every old path; move the assets back and upload quickly. Worlds that saved in between may have lost them for good.
I need to undo a bad update
Modders roll back by archiving the newest file on the legacy site. The previous published file becomes the live one.
The upload window says the cooking tools haven't been updated
Your kit is newer than CurseForge's cooker. Leave the beta branch, or wait for the cooker to catch up.
Watch
- How to Make an ARK ASA Mod (Complete Beginner Guide) (my video). 25:01 the upload. 26:10 Cross-Platform or PC Only, and why not to switch. 33:07 the legacy site and the project settings. 34:34 the description and how it looks in game. 37:33 file statuses and cook times. 38:26 Publish build, moderation and its hours.
- How to Find Blueprint Paths Using Manifest Files (Mods & Base Game) (my video). Finding the paths a published mod shipped with.
- Modding: Publishing a mod (Mist3r Trixt3r, 2023). 23:15 the Share Mod window and the wait.
Go deeper
- Your first mod, start to CurseForge: the first upload, step by step.
- Testing your mod: the four stages before any release.
- When a cook or upload fails: cook logs, rejections and the known killers.
- How to save your mod's data: what each save keeps, and how not to lose it.
- Lessons §6 (engine updates) and README §2 (how CurseForge fits in).
Sources
- Wildcard's news, read 2026-11-08: Community Crunch 525 (the UE 5.8 re-cook plan) and Community Crunch 531 (99.9% of mods re-cooked).
- My beginner guide video, 7TwjI7TCE_w (September 2025, UE 5.5 DevKit): the upload fields, the legacy site, file statuses, cook times, publishing, approval without notification and my experience of moderation hours.
- My other pages: lessons §6 and §9 (the 5.5.4 to 5.8.1 changes: the two event
overrides, the five ship-ramming properties, save upgrades with
PreUpgradeBackup; the release checklist); README §1 to §3 (the upload window refusing a newer kit; the project ID kept in the.upluginafter publishing); the enum-pin and renamed-pin notes from my own editor logs; When a cook or upload fails (CurseForge accepting cooks with errors). - What modders report, not confirmed by me:
- servers update on restart, clients match the server's version, half-applied client updates and the fixes (April 2024 to October 2026);
- renamed, moved or deleted classes vanishing from saves, and the manifest's old paths (December 2023, July 2026);
- reparenting a placed class (December 2023; opinions differ);
- rolling back by archiving a file on the legacy site (June and July 2024); the Mod Version display (December 2025); the linked-project line in the upload window (June 2025);
- the moderation schedule and review times as CurseForge posted them (July 2024), descriptions getting a mod hidden (October 2023), moderation delays announced by CurseForge (June 2025);
- the kit newer than the cooker (April 2024); the cooker newer than the kit (January 2026); missing materials until the cooker caught up (July 2026); DLC packages removed from the kit (February 2026); copying the mod folder to reinstall (September 2024); a fresh cook curing crashes after a game update; weapon animation Blueprints broken by updates (2025).
- Videos under Watch are creators' tutorials; Mist3r Trixt3r's is from the 2023 kit.
- Community knowledge from the ARK Modding Community Discord (discussions from October 2023 to October 2026), found with Overseer. Threads (they open for server members): updates and restarts (April 2024), old logic after an update (October 2026), bad installs after updates (November 2024), restart the game, update from the Mods menu (November 2024), clients match the server's version (March 2026), moved structures go "poof" (July 2026), moving a structure to a subfolder (December 2023), reparenting a placed structure (December 2023), rolling back an update (July 2024), Mod Version after a backup (December 2025), moderation hours and review times (July 2024), a mod hidden for its description (October 2023), moderation delays (June 2025), cooking tools not yet updated (April 2024), soft references after a cooker update (January 2026), materials missing until the cooker updates (July 2026), DLC packages removed from the kit (February 2026), reinstalling the kit (September 2024).
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 beginner guide video, my update notes and community knowledge (see Sources)