Language & Currency

Currency

Palworld: Your game, your server

from 19.61
AUD /month
from 23.43
BGN /month
from 69.60
BRL /month
from 19.32
CAD /month
from 11.15
CHF /month
from 92.89
CNY /month
from 290.06
CZK /month
from 89.55
DKK /month
from 11.98
EUR /month
from 10.25
GBP /month
from 107.91
HKD /month
from 90.29
HRK /month
from 4,363.72
HUF /month
from 248,383.74
IDR /month
from 42.07
ILS /month
from 1,312.40
INR /month
from 1,708.35
ISK /month
from 2,204.68
JPY /month
from 19,862.72
KRW /month
from 239.02
MXN /month
from 56.23
MYR /month
from 131.09
NOK /month
from 23.47
NZD /month
from 843.00
PHP /month
from 51.68
PLN /month
from 62.86
RON /month
from 1,404.07
RUB /month
from 131.61
SEK /month
from 17.68
SGD /month
from 460.45
THB /month
from 653.90
TRY /month
from 13.76
USD /month
from 228.06
ZAR /month
from 110.00
date /month

Become a Palworld Admin: Password and Server Commands

To get admin rights on your Palworld server, set an admin password and log in with it in-game. After that, you can save, send messages to everyone, or remove disruptive players.

The admin password is not the server password for normal joining. Share it only with people you trust to manage the server.

Set the admin password

Basic Mode

Open your server configuration and enter the password under Server Settings → Admin Password. Save the change and restart the server gracefully. Announce the restart beforehand if players are already connected.

Advanced Mode

Stop the server and open PalWorldSettings.ini. In the existing OptionSettings, find AdminPassword and enter your own password between the quotation marks:

AdminPassword="YOUR_OWN_ADMIN_PASSWORD"

This is a single entry, not a full configuration. Keep the other values as they are. Save the file and start the server again. Use your own strong password instead of the placeholder.

Log in as admin in-game

Connect to the server and open the chat. On PC, the Enter key opens it by default. Replace the placeholder in the following command:

/AdminPassword YOUR_OWN_ADMIN_PASSWORD

Login and commands are documented in the official command overview from Pocketpair.

Essential admin commands

CommandFunction
/InfoDisplay server information
/ShowPlayersShow connected players
/SaveSave the world
/Broadcast MESSAGESend a message to all players
/KickPlayer PLAYER_IDRemove a player from the server
/BanPlayer PLAYER_IDBan a player
/UnBanPlayer PLAYER_IDLift a ban
/TeleportToPlayer PLAYER_IDTeleport to the player
/TeleportToMe PLAYER_IDTeleport the player to you
/ToggleSpectateToggle spectator mode
/Shutdown SECONDS MESSAGEShut down the server after a warning
/DoExitExit the server immediately

PLAYER_ID, MESSAGE, and SECONDS are placeholders. Replace them with the appropriate values.

Player ID instead of display name

The official syntax refers to the identifier for player commands as SteamID. Use the issued identifier, not the visible player name. You can check connected players with /ShowPlayers.

In cross-play, do not replace a console identifier with an invented Steam ID. If an identifier is not accepted, note the platform, command, and error message and have the mapping checked. Do not issue ban commands against other IDs experimentally.

Banning and unbanning players

Before you issue a ban, note the ID used and the reason so you can review the decision later. To lift a ban, use /UnBanPlayer. Use the same identifier as when banning.

The earlier statement that unbanning was only possible by manually editing the ban list no longer applies.

Announce maintenance

A short procedure for planned maintenance might look like this. Send each line as a separate command:

/Broadcast Maintenance in 60 seconds. Please finish your actions.
/Save
/Shutdown 60 Planned maintenance

After your work, start the server again via the server management. Do not use /DoExit as your normal maintenance procedure: the immediate shutdown gives players no warning.

Saving with /Save does not replace a separate backup. Before changing files, you should download the savegame.

If a command does not work

First check that you are on the correct server and have logged in with its admin password. After changing a password, verify it was saved and applied by a restart.

Check spelling and placeholders. If issues persist, note the exact command without the password and the server’s response. If joining already fails, start with connection troubleshooting.