Palworld admin commands: complete list, syntax, and safe use

Palworld admin commands let you manage a dedicated server after setting its administrator password and authenticating in game chat. You can save the world, remove a player, announce maintenance, shut down the server, and use the documented teleport and spectator commands. The awkward part is choosing the right command channel and player identifier. This guide covers the complete official chat list, the available REST alternatives, and the limits to check before administering a mixed-platform group. It follows Pocketpair’s server documentation and current patch notes; it does not claim a hands-on test of every command or console client.

Become admin before issuing commands#

Set the administrator password on the server first, then authenticate your in-game session. The password used to join the world is a different setting. Knowing the join password does not give every friend permission to ban players or close the server.

These instructions assume you already have a dedicated world. If you are still choosing between ordinary co-op and a separate server, start with how to host a Palworld server. A co-op host should not expect every dedicated-server administration instruction to apply to their invite-code world.

1. Edit the active server configuration

   Stop the server normally and preserve a copy of its configuration. Relative to the installation directory, the active file is:

   Pal/Saved/Config/WindowsServer/PalWorldSettings.ini
   Pal/Saved/Config/LinuxServer/PalWorldSettings.ini

   Use the path for your server operating system. In the existing OptionSettings=(...) line, set the administrator password while preserving the other options and commas. This is the individual field to replace, not a complete configuration file:

   AdminPassword="replace-with-a-private-admin-password"

   Do not paste that example password unchanged. Do not edit only DefaultPalWorldSettings.ini: Pocketpair’s configuration instructions identify the saved configuration as the file that controls the server. A hosting panel may expose the same field through its settings form.

2. Restart, join, and authenticate

   Restart the server after saving the change. Join the correct world, open chat, and replace the placeholder below with the configured password:

   /AdminPassword YOUR_ADMIN_PASSWORD

   Pocketpair documents Enter for opening chat with a keyboard. The command belongs in game chat, not PowerShell or the server process window. Check the login response before continuing; if authentication fails, verify the active file, exact password, and completed restart.

3. Check a read-only command first

   Request server information before trying anything disruptive:

   /Info

   Confirm that the response describes the expected server. Use the login response to establish that authentication succeeded; server information by itself is not a reason to assume every administrative operation will work.

Keep ServerPassword and AdminPassword separate. Share the latter only with people who should have operational control, and avoid capturing it in screenshots or shared support transcripts.

Use the complete Palworld admin commands list#

The official command reference lists the following 13 entries, including authentication and spectator mode. Angle brackets identify values you supply; square brackets mark the optional shutdown arguments in Pocketpair’s notation. Do not type the brackets around a real value.

For a maintenance notice followed by a save, enter these separately:

/Broadcast Maintenance in five minutes
/Save

For a delayed shutdown with a message:

/Shutdown 60 Server closing for maintenance

The last command stops the process; it does not start it again. Arrange the subsequent launch through the host machine, service manager, or provider controls.

The teleport commands are directional: “to player” moves you, while “to me” moves the other person. Ask before relocating someone who is building or fighting. Spectator mode is another distinct operation; Pocketpair also documents the backslash key as its toggle after administrator authentication. That keyboard binding does not establish a controller shortcut.

Choose chat, REST, or an existing RCON tool#

Use chat for in-world actions and REST for supported operations you want to perform without joining. Treat RCON as a legacy integration: Pocketpair’s RCON documentation marks it deprecated and says support will end in an upcoming update. It does not name a removal date, so neither “already removed” nor “safe indefinitely” follows from that notice.

If you arrived expecting a developer cheat console, first distinguish console commands from server commands. The channels overlap, but they are not interchangeable. The REST paths below are relative to /v1/api; use the method shown.

REST also exposes settings and metrics reads. Those are structured API responses, not instructions to paste a slash command into an HTTP request. Pocketpair’s REST introduction describes enabling the API and its Basic authentication requirement. In the existing configuration, the relevant fields are:

RESTAPIEnabled=True,RESTAPIPort=8212

Preserve the surrounding OptionSettings structure and restart after changing it. For a first read from the server machine itself, this curl request prompts for the configured administrator password:

curl --fail --user admin http://127.0.0.1:8212/v1/api/info

Use curl.exe if your PowerShell environment maps curl to a different command. The palctl tool’s documentation also describes the admin username and administrator-password configuration for this API. Successful JSON from the expected server is the useful first check; an authentication error is not a reason to try a shutdown request.

If an existing RCON client serves your group, check it against the installed server version and plan its replacement. Do not assume that deleting the slash from every chat command guarantees equivalent remote behavior, especially for actions requiring an in-world character. If you need a dashboard to coordinate process controls and routine operations, compare these server manager tools for Palworld separately from the built-in command list.

Match the player ID to the command channel#

Use the identifier required by the specific interface. The chat documentation writes targeting arguments as SteamID. The REST player response supplies both userId and playerId, which must not be treated as interchangeable just because they describe one person.

Start with the current connected-player list, then match the intended person before taking action:

/ShowPlayers

For chat, retain the official SteamID syntax. The primary documentation reviewed here does not establish a universal display-name substitution or a set of Xbox and PS5 prefixes for those chat commands. Guessing a prefix is a poor way to decide who gets banned.

For REST, read the players response and copy the actual userId returned for that player, preserving its prefix. The example response distinguishes it from the world-specific playerId. The kick request then uses a lowercase request property named userid:

{
  "userid": "COPY_THE_ACTUAL_RETURNED_USER_ID",
  "message": "Please reconnect after maintenance"
}

That is a request-body template, not a real player identity. Send it to POST /v1/api/kick only after replacing the placeholder. The same lowercase property is required by ban and unban; unban does not need the optional kick/ban message.

Check the response and refresh the player list after a kick. For a ban, keep a private record of the identity you acted on so an unban is possible. Avoid publishing raw API output in a help request: the players response can contain IP addresses as well as names and identifiers.

Administer a server from PS5 or Xbox#

Console access to chat and administrator authorization are separate requirements. Pocketpair’s v1.0.4 patch notes published September 6 add opening chat from the Radial Menu on PS5. On that version, use the radial menu’s chat option before entering the documented administrator login.

That patch note establishes the chat entry point. It is not a test of every moderation or teleport command with every console account identifier. Start with authentication and a harmless information request. If a targeting command rejects an identifier, return to the documented interface instead of cycling through guessed names and prefixes.

For Xbox, inspect the current game’s controller bindings and chat controls. The official sources reviewed for this guide do not establish one exact controller shortcut, so there is no invented button combination here. A keyboard instruction in the server docs should not be relabeled as an Xbox controller instruction.

When in-game entry is unavailable or inconvenient, the owner can administer supported operations from another device with private REST access, or through provider controls that explicitly support them. Those requests target the dedicated server and do not require your game character to be connected. They still require the administrator credentials and a reachable, protected API; using a console for gameplay does not bypass either requirement.

Recognize commands vanilla does not provide#

The official vanilla list does not include give-items, spawn-Pal, weather, or god-mode commands. A search result demonstrating one of those features may be using a mod, a different console, or custom server software. Copying its syntax into a normal server’s chat does not install the missing capability.

Spectator mode is a useful exception to broad “there are no cheat-like tools” claims: /ToggleSpectate is documented. It should not be described as a general god-mode or item-spawning command. Likewise, changing a server gameplay setting is a configuration task, not evidence that a similarly named chat command exists.

For progression rates, death rules, and base limits, follow the Palworld configuration explainer and preserve the rest of your active settings line.

The author’s AdminCommands project, for example, adds commands through additional software and dependencies. Its commands belong to that project, not Pocketpair’s vanilla reference. Check the project’s current supported build and installation requirements before relying on a demonstration from another patch.

Keep experiments away from the only copy of your group’s world. Confirm the exact mod version, dependencies, and client requirements, then test against a separate backup. “Server-side” alone does not establish compatibility with every console client or guarantee that a game update will preserve the feature. If all you need is a save, kick, or scheduled stop, the documented administration interfaces may already cover the job.

Finish with a save and a recoverable shutdown#

A reliable maintenance routine warns players, saves, stops cleanly, preserves a separate copy, and verifies the next launch. A successful save command proves neither that an independent backup exists nor that the server will restart automatically.

1. Announce the interruption. Give players enough notice to finish their immediate activity. In REST, the announcement endpoint takes a JSON message; it does not take a raw chat command.
2. Save the world. Use the documented save operation and check its response. The REST save endpoint is POST /v1/api/save and documents no request body.
3. Request a delayed shutdown. Use the chat example above or the REST body below. A countdown gives connected players a final warning.
4. Confirm the server stopped, then back up. Preserve the complete world data and relevant configuration on separate storage. Avoid copying a changing live save as though it were a known consistent snapshot.
5. Start the server and check the world. Launch through your normal host controls, then have a player confirm their character, inventory, and base. Keep the pre-maintenance backup until that check succeeds.

For REST shutdown, send this JSON to POST /v1/api/shutdown:

{
  "waittime": 60,
  "message": "Server closing for maintenance"
}

The wait time is an integer. The immediate stop endpoint is a different operation; it should not silently replace the planned countdown in your routine.

Self-hosting is reasonable when you are comfortable owning this maintenance. If keeping the machine available and managing recurring work have become the burden, compare dedicated-server hosting routes and the responsibilities each provider accepts. The Game Hosting Palworld page currently presents a waitlist; confirm availability and the actual administration and backup controls before relying on a service for your world.

Keep one short runbook with the connection method, authorized administrators, backup location, and restart procedure. The useful final result is a world your friends can rejoin with their progress intact, plus a recovery path if the next maintenance window goes wrong.