ARK: Survival Ascended Server Admin Commands and How to Use Them

To use admin commands in ARK: Survival Ascended, open the console for your platform, authenticate on a multiplayer server with enablecheats <ServerAdminPassword>, then run commands with the cheat or admincheat prefix. Single-player sessions generally skip authentication and the multiplayer prefix. PC players press Tab (or the configured console key), while Xbox and PlayStation players open the pause-screen Admin Command interface with their controller combination. Start with inspection, communication, and save commands before using deletion, tribe, or map-wide commands: those can permanently remove creatures, structures, players, or ownership data.

How do I open the ARK: Survival Ascended admin console?

The console entry method depends on your platform and input device. On consoles, first make sure console access is enabled in the game settings if the pause menu does not show an Admin Command field. Prompts can vary with the platform, game build, and whether a keyboard is connected.

Platform	Open the command interface	Submit the command
PC	Press Tab. The official community reference also documents ~ as a possible console key on PC and on consoles using an active keyboard and mouse.	Type the command and press Enter.
Xbox	Press LB + RB + X + Y together to open the pause-screen command field.	Enter the command, then select the in-game Admin Command button.
PlayStation	Press L1 + R1 + Square + Triangle together.	Enter the command, then select the in-game Admin Command button.

If a combination does nothing, pause the game and check the current control prompt. A console update or a change from controller to keyboard input can alter which field appears.

How do I enable cheats on a multiplayer ASA server?

On a multiplayer server, run enablecheats <ServerAdminPassword> after opening the console. The password must match the server’s ServerAdminPassword setting, and authentication applies to the current player. After it succeeds, prepend commands with cheat or admincheat.

1. Open the console using the platform method above.
2. Enter enablecheats <ServerAdminPassword>, replacing the angle-bracketed text with the actual password. Do not type the brackets.
3. Run a harmless check such as cheat ListPlayers.
4. Use the authenticated prefix on subsequent commands, for example cheat SaveWorld.

A typical dedicated-server sequence is:

enablecheats <ServerAdminPassword>
cheat ListPlayers
cheat SaveWorld

In single-player, you normally do not need enablecheats, cheat, or admincheat. If a command is rejected on a hosted or rented server, verify that you are using the server’s administrator password rather than an account password and that the command is allowed on that server build.

What command syntax does ASA use?

ASA’s parser is forgiving about capitalization but strict about arguments and scope. These rules prevent many failed commands.

• Case: Command names are generally case-insensitive, so SaveWorld and saveworld are equivalent.
• Booleans: Use true, false, 1, or 0; decimal forms such as 1.0 and 0.0 are also accepted.
• Distances: Coordinates and radius values use game units, described in the reference as centimetres.
• Chaining: Join commands with |. On multiplayer servers, prefix each command separately, for example cheat SaveWorld | cheat Broadcast Server saved.
• Targeting: Commands aimed at the creature or structure under your crosshair, or at the executing player, require local targeting and cannot be used through a remote console when that local context is unavailable.
• Arguments: Keep names containing spaces in quotation marks where the command syntax requires it, and use the exact player ID, account ID, tribe ID, class name, or blueprint path expected by the command.

Which admin commands should I run first?

Begin with commands that observe the server, communicate with players, or create a recovery point. They are useful for diagnosing a problem without changing the world.

Command	What it does	Risk and use
ShowMyAdminManager	Opens a graphical manager containing server information, key configuration values, connected players, bans, whitelist entries, MOTD controls, and a large command list.	Low risk; useful as the first stop for administration.
ListPlayers	Lists connected players and their ARK IDs.	Low risk; copy IDs before moderation or player-targeted commands.
Broadcast <message>	Sends a server-wide message.	Low risk; warn players before a restart or world-changing action.
ServerChat <message>	Sends a chat message to players.	Low risk; useful for a less intrusive notice.
ShowMessageOfTheDay	Displays the configured MOTD.	Low risk; confirms the message that new or returning players see.
SaveWorld	Forces the current world to save to disk.	Low risk and recommended before destructive work.
StartSaveBackup	Starts the server’s save-backup process.	Use before deletion, ownership changes, or maintenance.
GetGameLog	Returns log entries when the server was launched with -servergamelog.	Diagnostic; it does not enable logging retroactively.
GetAllState <ClassName>	Prints entities of a specified class to the console or log.	Diagnostic; requires the correct class name.

How do I moderate players and manage access?

Use player IDs from ListPlayers or the admin manager rather than relying on names that may be duplicated or changed. Account-ID formats differ by platform, so copy the identifier shown by the server tools.

Command	Syntax	Result
Ban a player	BanPlayer <SteamID>	Adds the specified player to the ban list.
Remove a ban	UnbanPlayer <SteamID>	Removes the player from the ban list.
Whitelist an account	AllowPlayerToJoinNoCheck <AccountID>	Allows the account to join without the normal join check.
Remove a whitelist entry	DisallowPlayerToJoinNoCheck <AccountID>	Removes that account from the whitelist.
Disconnect a player	KickPlayer <PlayerName or ID>	Forcibly disconnects a player without adding a ban.

Tell players what will happen before a kick, ban, maintenance shutdown, or rollback. For a planned stop, Broadcast a warning, save the world, and only then use DoExit. DoExit shuts down the server as soon as possible; it is not a routine way to reload a map.

How can I change my character’s movement, survival stats, or building permissions?

These commands affect the executing player unless their syntax says otherwise. Toggle commands remain active until you reverse them, leave the session, or use the corresponding off command.

Command	Effect	How to reverse or limit it
God	Toggles invulnerability.	Run God again to toggle it off.
InfiniteStats	Refills and maintains health, stamina, oxygen, food, and water.	Run it again to stop the effect.
LeaveMeAlone	Combines God, InfiniteStats, and enemy invisibility.	Use the individual toggles when you need a controlled test instead of the bundle.
Fly	Enables free movement.	Use Walk to restore normal physics.
Ghost	Enables no-clip movement through terrain and structures.	Run Ghost again; return to a safe position before doing so.
GiveCreativeMode	Enables creative building and related creative privileges.	Toggle it off using the command’s normal in-game toggle behavior before returning to regular play.

Use Fly for inspection and Ghost only when collision prevents access. Turning off no-clip inside terrain can leave a character stuck, so move into open space first.

How do I teleport myself or another player?

Choose the narrowest targeting method that solves the problem. Crosshair teleportation is quick, while player-ID and coordinate commands are more precise and easier to audit.

• Teleport moves you forward to the next collision point.
• TeleportToPlayer <PlayerID> moves you to another player.
• TeleportPlayerIDToMe <PlayerID> brings the specified player to you.
• SetPlayerPos <x> <y> <z> places your character at explicit coordinates.

Check the destination before moving a player: a coordinate inside rock, deep water, or an enclosed structure can cause damage or trapping. For a player-ID command, obtain the exact ID from ListPlayers rather than guessing from a display name.

How do I give items, resources, experience, or equipment?

ASA provides three main item-grant forms: a shorthand blueprint search, a full blueprint path, and a numeric item ID. The command you choose determines how much identifying information you must supply.

Command	Syntax or purpose	Best use
GFI	GFI <BlueprintPathPart> <Quantity> <Quality> <ForceBlueprint>	Fast grants when you know a distinctive part of the blueprint name.
GiveItem	Uses the full blueprint path, quantity, quality, and blueprint option required by the item.	Precise grants when a shorthand match is ambiguous.
GiveItemNum	Uses an item number, quantity, quality, and blueprint option.	Useful when you have the numeric ID; for example, giveitemnum 1 1 0 false.
GiveResources	No item arguments; grants a bundle of resources.	Quick building or crafting tests.
GiveArmorSet	Grants a preset armor tier.	Equipping a test character quickly.
GiveWeaponSet	Grants a preset weapon tier.	Combat or balance testing.
AddExperience	Adds experience to the executing player.	Testing progression without normal grinding.
GiveExpToPlayer	Gives experience to a specified player.	Administering progression to another player.
LevelUp	Raises a selected stat or progression level according to its arguments.	Controlled character testing; verify the stat argument before submitting.

Quality and blueprint arguments are not interchangeable. If a grant produces the wrong object, check the blueprint path or numeric ID and confirm whether the final boolean should be true for a blueprint rather than a finished item.

How do I tame, summon, or manage creatures?

Creature commands differ in whether they target an existing animal, perform a normal tame, or create a new tamed creature. Aim at the intended creature before using a crosshair command.

• ForceTame immediately tames the creature under your crosshair. A force-tamed creature can be rideable without a saddle until it is cryopodded and redeployed; after redeployment, normal saddle requirements can apply.
• DoTame performs a normal-style tame interaction on the targeted creature.
• GMSummon "<type>" <level> spawns and tames a creature, but the resulting creature still requires a saddle.
• ClearCryoSickness clears cryo-sickness on the targeted tame.
• PlayersOnly stops creature movement and crafting while players can still move. Repeat it to toggle the effect.
• DestroyWildDinos removes all untamed creatures so new wild spawns can populate. It does not permanently prevent respawning.

DestroyWildDinos is map-wide and can disrupt a live server’s ecosystem. Warn players and save first, even though it does not delete tamed creatures.

How do I change time, weather, game speed, and diagnostics?

World and diagnostic commands alter the server state or expose information without necessarily changing player inventories. Apply them deliberately on a live server.

Command	Syntax	Use and limitation
SetTimeOfDay	SetTimeOfDay <HH:MM:SS>	Sets the world clock, such as SetTimeOfDay 12:00:00.
SetDay	SetDay <day>	Changes the current day number.
CE	CE <weather command>	Starts or stops map-specific weather events; available subcommands vary by map.
Slomo	Slomo <multiplier>	Changes game speed. Set Slomo 1 to return to normal speed.
ToggleDamageNumbers	No additional argument	Toggles floating damage numbers on the server.
GetGameLog	No additional argument	Returns log entries only when the server was started with -servergamelog.
GetAllState	GetAllState <ClassName>	Prints entities of a specified class to the console or log.

Weather syntax is map-dependent, so do not assume a command that works on one map is valid on another. Likewise, leave Slomo at 1 after a test; an elevated multiplier affects movement, crafting, combat, and other timing-sensitive systems.

Which ASA commands are destructive, and how can I avoid losing a world?

Deletion and ownership commands have substantially different scopes. A crosshair command can remove one object, while tribe and map commands can erase thousands of entities or players. Treat every destructive command as irreversible unless you have a tested backup.

Command	Scope	Important distinction
DestroyMyTarget	Targeted creature or structure	Deletes the target without leaving a corpse.
Kill	Targeted creature or player target	Kills the target and leaves a corpse where applicable.
DestroyAll <ClassName>	Every entity of the specified type	A wrong class name or broad class can produce a much larger deletion than intended.
DestroyAllEnemies	Map-wide non-player creatures	Removes enemies across the map, not just near the administrator.
DestroyStructures	All player structures	Can erase the entire built world.
DestroyWildDinos	All untamed creatures	Wild spawns can return after the cleanup.
DestroyTribeId	Tribe-wide	Operates on a tribe scope; confirm the tribe ID first.
DestroyTribeIdDinos	Tribe-wide creatures	Removes the tribe’s dinos.
DestroyTribeIdPlayers	Tribe-wide players	Removes players associated with the tribe.
DestroyTribeIdStructures	Tribe-wide structures	Removes the tribe’s structures.

1. Confirm the exact target, tribe ID, class name, and any radius argument.
2. Run SaveWorld.
3. Start the server’s backup process with StartSaveBackup and verify that the backup completed through your hosting or server-management tools.
4. Prefer a crosshair or narrowly identified target over an area-of-effect or map-wide command.
5. Broadcast the planned action and its scope before executing it.
6. Run the command once, inspect the result, and avoid repeating it while diagnosing a delay.

Do not use DoExit as a substitute for a backup. It stops the server; it does not undo a deletion.

Why do command lists differ between ASA references?

There is no permanent, universal command count. One current reference reports 240 commands, including 63 marked PC-only, 13 marked ASA-only, and eight categories; it says its list was checked against an ASA server binary downloaded on August 31, 2026. Another reference currently displays 244 commands and lists 25 under Server Administration. The difference reflects snapshot dates, inclusion rules, and platform labels rather than a guaranteed change of exactly four commands.

Use the in-game admin manager and the command behavior on your own server as the final check after a major ASA patch or server-binary update. A command may exist in a list but be unavailable on your platform, require a different prefix, or depend on a map-specific argument. Keep a small, tested set of recovery commands—ListPlayers, Broadcast, SaveWorld, and your backup procedure—rather than copying an old list wholesale.

What should I do when an admin command fails?

Most failures come from the wrong console, missing authentication, an incorrect identifier, or a command that is unavailable on that build.

• No response to the key combination: Pause the game, enable console access in settings if available, and check the displayed Admin Command control for your platform and input mode.
• Authentication rejected: Re-enter enablecheats with the exact server administrator password. Confirm that the password is the server’s ServerAdminPassword value and that you are connected to the intended server.
• Command works in single-player but not multiplayer: Add cheat or admincheat after authenticating. On a chained line, prefix every command.
• Wrong player or creature affected: Re-run ListPlayers, copy the ID, and place the crosshair directly on the intended target. Remote consoles cannot supply local crosshair context for commands that require it.
• Item grant is wrong: Check whether the command expects a blueprint fragment, full blueprint path, or numeric item ID, then verify quantity, quality, and the final blueprint boolean.
• Weather command fails: Check the map-specific CE subcommand; weather events are not universal across maps.
• Entity cleanup appears incomplete: Remember that DestroyWildDinos removes untamed creatures but does not disable future spawning. Allow the server time to repopulate.
• Results are different after an update: Recheck the current build’s command list and test on a backup or private session before applying the command to a populated server.

Frequently Asked Questions

Can every player on an ASA server use admin commands after I authenticate?

No. Authentication is applied to the player who successfully runs enablecheats. Each other player must be authorized separately, and server configuration or platform restrictions can still limit which commands are available.

Do admin commands disable achievements or progression in ASA?

The command references in this guide do not establish a universal achievement rule. Treat creative, item-grant, teleport, and progression commands as gameplay-altering and check the achievement behavior of your specific single-player, non-dedicated, or dedicated setup before using them on a completion-focused save.

Can I run ASA admin commands from a server console instead of inside the game?

Some server-management interfaces accept commands, but local-target commands need the executing player’s crosshair and therefore cannot work remotely. Use the in-game console for commands that target your character or the object you are looking at.

What is the safest way to test an unfamiliar command?

Make a verified save backup, test on a private or disposable world, and begin with an observational command such as ListPlayers or GetAllState. Confirm the command’s platform and build availability before trying it on a live server.