A command that does nothing and a command that returns the wrong thing are different faults, and they have different fixes. Sort the symptom before you retype the line: no response, wrong result, or works on one map but not another. Then walk the matching branch below. One thing shapes all three: no official Studio Wildcard command catalog had been identified as of 14 October 2026, and commands change with patches. So this page diagnoses causes rather than printing a list that would be stale by the next update.
Branch one — the command does nothing
Start with authentication, not with the command. On multiplayer, run enablecheats again. Console commands require an admin login first; without it the client shows you the command while the server quietly refuses to execute it. Once authentication succeeds, cheat-prefixed commands work for the rest of that session on that client, so you only need to do it once per session — but you do need to do it again after every new login.
Next, check the prefix. Add cheat or admincheat before the command. If the same line behaves in your own single-player world and dies the moment you join a server, that contrast is the clue: the command is fine, the session authority or the prefix is not. Typing it louder will not change either.
A useful tell: a line that appears in the console yet changes nothing in the world is exactly the refused-execution case above. Work authentication and prefix before you suspect the command name at all.
Branch two — it runs, but the result is wrong
Now suspect the version, not your fingers. Confirm the command is listed for ARK: Survival Ascended, not only for the older ARK: Survival Evolved, and read any “partially working” label attached to it. A command carried over from an ASE guide can exist in ASA in name while behaving differently or applying only in a narrower set of situations; that label is the difference between a broken command and a command doing less than you expected.
Then copy the exact spelling, argument order and any blueprint path character for character from the current ASA listing instead of retyping it from memory or from an old forum post. Arguments and paths are where a line that “looks right” quietly diverges. If the command is marked partially working, stop debugging your syntax — the limit is on the command’s side, and the honest fix is to use a different route to the same result.
Branch three — it works on one map, not another
Treat a map-specific failure as a content-scope problem before an input problem. Commands arrive with the content they belong to, so a line lifted from a guide for a different map or expansion may simply not exist in the build you are on. Check that the command is listed for the map and content you are actually playing; if it is not there, no amount of prefix fiddling will conjure it.
The same rule covers commands that worked last patch. A line that used to fire can be renamed, restricted or dropped in a later update. When a previously reliable command goes quiet, re-confirm it against the current build before assuming your setup broke.
Before you run anything destructive
Commands that wipe wild dinos, force tames or spawn entities change the saved world, and there is no undo prompt. Back up the save first. On a single-player world, make a manual copy of the save folder before the session; on a server, have the host take a backup of the world files. If you are not the host, you should not be running world-changing commands at all — that is an admin-authority question from branch one.
The catalogue caveat is worth restating because it is the reason for the order above. With no official command directory and commands shifting between patches, any fixed list of “working commands” becomes wrong over time. The diagnostic order does not: authenticate, check the prefix, confirm the command is listed for your current ASA build, then check its content scope. That sequence still applies after the next patch, long after individual command names have moved.
For the commands themselves, the spawn commands guide is the reference page; this one is only about why they fail. If the real problem is a mod that never loaded, use the mods troubleshooting steps instead, and check single-player settings when the confusion is about which options your own world exposes.