Testing on a server before you publish: the -dev method
7 min readASA DevKit as of November 2026 (UE 5.8.1); ASA only (ASE had no CurseForge cook)
You don't have to publish a mod to test it on a real server. Add -dev to your CurseForge project ID in the
server's mod list, for example -mods=926919-dev. The server then downloads the newest file of that project, even
one that's only "ready for review" and was never published. It's built into the game: no tools, no tricks.
This is the last test before players get your mod, because it runs the real cloud cook on a real server. It's also how you test an update to a mod that's already live without your players getting it.
- You'll do: link your game account, add testers, start a server with
-dev, join it and check the log - Time: 10 minutes once the server is installed; the cloud cook takes minutes to hours
- Level: beginner (you've uploaded a mod once)
- You'll need: a mod uploaded to CurseForge with a "ready for review" file, and a dedicated server on your PC or a hosted one
Three ways to test an unpublished mod
| Route | Where it runs | What it tests | Use it for |
|---|---|---|---|
| My Mods in the game | Single player on your PC or console | The cloud cook, without networking | A quick look; custom cosmetics (only testable this way) |
-dev on a server |
A dedicated server, yours or hosted | The cloud cook with real networking, stasis and restarts | The final check before publishing; testing an update to a live mod |
A local cook copied over a -dev download |
A dedicated server on your PC | Your own cook, in minutes instead of waiting for CurseForge | Repeated tests while you fix things (the steps) |
-dev only matters when the server downloads the mod from CurseForge. Once your local cook sits in the mod folder,
the flag isn't what loads it. You still need -dev the first time an unpublished project downloads.
The process
Upload the mod and wait for "ready for review". Don't press publish.
Show me how
- Upload from the DevKit as in publishing and updating.
- On curseforge.com, your project's Files tab shows each platform's file move from processing to cooking to
Ready for Review. That's the state
-devloads. - Test the file your players will get. A server set to PC only loads the PC-only file; a crossplay server loads the crossplay one. A modder who switched a crossplay project to PC-only uploads found the server kept installing the old version. If you want fast PC-only test builds, keep them in a separate test project.
Link your game account to CurseForge. Without it you can't see the mod in My Mods or join a
-devserver.Show me how
- On curseforge.com: your profile, Edit profile, Connected Accounts, then sign in to each platform you play on (Steam, Xbox, PlayStation).
- One CurseForge account per platform account, and the other way round.
- In the game, a My Mods tab appears in the mod list once the link works. It lists every mod your account owns or can access, published or not.
Add your testers as project members (optional, up to 5 people).
Show me how
- On the project: Manage Project, Members, search the tester's CurseForge name, Add Member, pick a role.
- Tick Cross Platform Testing, then Save Changes. Wildcard's page says console testers need this permission. A modder in 2023 found testers couldn't reach the mod until it was ticked, so tick it for PC testers too.
- The tester accepts the invitation from their email before they get access (my beginner guide).
- Each tester links their own game account, as in step 2.
- If CurseForge can't find the name, the tester may have changed the name it generated when they signed up. Ask for the name their profile shows now.
Get a dedicated server. Your own PC is free; a hosted one works the same way.
Show me how
- On your PC: install ARK: Survival Ascended Dedicated Server from your Steam library's Tools list. Or use
SteamCMD:
steamcmd +login anonymous +app_update 2430930 validate +quit. - The server program is
<Server>\ShooterGame\Binaries\Win64\ArkAscendedServer.exe. - Hosted: CurseForge's article names Nitrado as ASA's hosting partner. Its Active Mods field takes the same
<ProjectID>-dev. - Some third-party server managers download your mod themselves and then start it as a normal mod, without
-dev. That fails for an unpublished file. Check that yours adds the suffix.
- On your PC: install ARK: Survival Ascended Dedicated Server from your Steam library's Tools list. Or use
SteamCMD:
Start the server with
-devafter your project ID.Show me how
- A minimal command line:
ArkAscendedServer.exe TheIsland_WP?listen?SessionName=ModTest -mods=<ProjectID>-dev -log - Use the project ID from the project page, not a file's ID.
- Several mods are separated by commas. Published and unpublished ones mix fine:
-mods=926919-dev,900062. - For a map mod, start on your map's level name instead of
TheIsland_WP(a map mod). -logwrites<Server>\ShooterGame\Saved\Logs\ShooterGame.log.
- A minimal command line:
Check the log before you join.
Show me how
- Good:
UShooterEngine::LoadGameModslists your mod, thenServer: "ModTest" has successfully started! - Bad:
Detected an unavailable mod: <Name> (<ID>)! Ensuring mod is deleted.... The server didn't find a file it's allowed to load, so it deletes the mod's folder. A local cook you copied there is gone too. The usual cause is a missing-dev. Otherwise the file isn't "ready for review" yet, or the ID is wrong. - The log prints your admin password. Blank it before you share the log (reading logs).
- Good:
Join and test as a real player would.
Show me how
- Join from the game's server list (search your session name) or with
open <IP>:7777in the console. - Every account that joins needs access to the unpublished file: you or a project member, with a linked game account. Anyone else fails to join.
- Test with two players, one of them not an admin, and join one late. Testing your mod has the full list: stasis, restarts, gamepad.
- Join from the game's server list (search your session name) or with
Test an update to a live mod the same way. Upload the update but don't publish it. Restart your test server with
-dev: it loads the newest file, while your players' servers, without-dev, keep the published one.Show me how
- The server picks the newest file when it starts. After a new file finishes cooking, restart the server.
- A modder reported in October 2023 that
-devignored newer test files once a version had been published. Reports from December 2024 and July 2026 say it loads them. Make sure yours did: put a version number somewhere you can see it, such as an item's tooltip or a Print String at start-up. - For transfer features (uploads, cluster travel), modders run two
-devservers in one cluster.
Never use
-devon a server your players use. Wildcard's page warns against it. Only members can join a server running an unpublished file, and it would pull every untested upload you make.
Testing in single player: My Mods
For a quick look without a server:
- In the game, open the mod list, then the My Mods tab, and pick your mod.
- Install it. Choose the newest version: an unpublished file can differ from the public Mod Browser one.
- Create a new game. Under the game's mod settings, move your mod from Available mods to Active mods, then start it in single player, or as a non-dedicated session so a tester can join you.
My Mods also works on consoles, for testers with the Cross Platform Testing permission. It's the way to test custom cosmetics: a server shows only those its CosmeticWhitelistOverride setting allows (custom cosmetics). Single player hides everything about networking, so finish on a server.
Common mistakes
The server log says "Detected an unavailable mod"
-dev is missing, the file isn't "ready for review" yet, or the ID is a file ID instead of the project ID. The
server deletes the mod folder when it logs this. Recopy a local cook afterwards.
My friend can't join my test server
They must be a project member with Cross Platform Testing ticked, and their game account must be linked to the CurseForge account you added. A project allows up to 5 members besides you.
The server keeps loading the old version
Restart it after the new file finishes cooking. Check that the server's platform (PC only or crossplay) matches the file you uploaded.
My server manager installs the mod, but it never loads
The manager probably starts it as a normal mod, without -dev. Add the suffix to the mod ID yourself, or use a
plain command line.
Go deeper
- Testing your mod: the four stages, from PIE to this one, and the pre-publish checklist.
- Works in PIE, not on a server: the local cook copied onto a downloaded mod, and what PIE hides.
- Publishing and updating: uploading, the publish button and moderation.
- Reading a crash report: when the server crashes on your mod.
Sources
- Wildcard's DevKit docs: Testing (read
2026-11-13): My Mods, the
-devsuffix with a-mods=example, joining needs access to the unpublished file, up to 5 members, the Cross Platform Testing permission for consoles, and the warning against player servers. - CurseForge Support: How to test your new ARK mod on all platforms (modified 2025-05-06): Connected Accounts, Members and the Cross Platform Testing tick, the My Mods steps, Nitrado, and published and unpublished mods together on one server.
- Video: SlayerXtreme, ASA Modding Episode 14 (2024-08-05, auto captions):
testing a "ready for review" file without publishing; connected accounts;
the
-devserver list and testers. My own beginner guide (2025-09-02): testers accept the invitation by email. - SteamCMD app ID 2430930 is the ASA dedicated server's Steam app.
- Community knowledge from the ARK Modding Community Discord (October 2023 to July 2026), found with
Overseer. Threads (they open for server members):
-devbefore approval (October 2023), "unavailable mod" fixed with-dev(November 2024),-devisn't needed for a local cook (April 2024), testers and the cross-platform permission (November 2023), -dev ignored newer files (2023) (October 2023), testing an update with-dev(2024) (December 2024), My Mods or-devfor an update (2026) (July 2026), two-devservers for transfers (December 2025), crossplay and PC-only files (November 2024), server managers and-dev(December 2025), console testers (September 2026).
Where this page's information comes from
Applies to: ASA DevKit as of November 2026 (UE 5.8.1); ASA only (ASE had no CurseForge cook)
Wildcard's testing page, CurseForge's testing article, the community Discord and a creator's video (see Sources)