Palworld Command Manager

At a glance

The Command Manager runs server commands for you on a repeating schedule - a save every half hour, a restart warning at the same time each night, a weekly reward for whoever is online.

It is one of two tabs on the Event Manager page. Config Events change PalWorldSettings.ini for a while and restart the server - a weekend with different capture rates. The Command Manager sends commands to the running server and restarts nothing.

How commands actually reach Palworld

Palworld's dedicated server has no console you can type into. The window it runs in reads nothing. Everything goes over the server's REST API, on your game port plus two, authenticated with your AdminPassword.

Two consequences follow, and both matter.

The upside of the REST API is that it answers back, so a Palworld run is recorded as a real success or a real failure with the server's own response stored beside it.

Your first schedule

1. Nothing to set up first: if Settings → AdminPassword is blank, the platform writes one when the server starts.

2. Open Event Manager, then the Command Manager tab.

3. Click + New Schedule.

4. Name it Auto Save, pick Save World, choose Every N minutes and set 30.

5. Click Create, then Run now, then History.

If step 5 shows an authentication error, the admin password was changed after the server started - restart the server. The schedule is not the cause.

The 11 commands

Six are vanilla and reach any Palworld server. Five are PalDefender commands and need that mod installed with its REST API enabled.

Vanilla

PalDefender

Neither Shutdown nor Stop restarts anything. Everyone is disconnected and the server stays down until you press Start in the panel. For a nightly restart, use the panel's auto-restart rather than scheduling a stop.

Rewarding everyone without typing player IDs

Palworld identifies players by a platform-prefixed ID:

steam_7656119XXXXXXXXXX
gdk_2533274800000000
ps5_ABCDEF123456

Four commands take one - Kick Player, Give Item, Give XP and Give Pal - and typing those by hand is miserable. Worse, they are the sort of thing you get subtly wrong once and then wonder for a week why one player never got their reward.

Each of those four shows an Send to every online player checkbox next to the player field. Tick it and you enter no IDs at all: when the schedule fires, the platform asks the REST API who is online, reads each player's platform ID from the answer, and sends the command once per person.

Palworld has no "everyone" selector of its own, so this genuinely is one command per player. That is expected, not a fault.

To find one player's ID when you do want to target a single person, run ShowPlayers from the Console tab.

Schedules worth building

A restart warning that stays accurate

Broadcast Message, ten minutes before your nightly restart:

Restart at {nextRun} - {players} online

{nextRun} is filled in when the message goes out, so it cannot drift out of step with the restart it is announcing.

A save before the nightly restart

Let the panel's auto-restart do the restarting.

Reading the history

Click History on the schedule for its runs, 20 at a time with Load older runs for more, each with the command sent, the API's response, and a status.

A PalDefender command on a server without PalDefender fails, and the error says so. That is the quickest way to confirm whether the mod is actually loaded.

Each status and what to check: Command Manager Troubleshooting.

Everything else a schedule can do

Multi-step sequences, waits, run conditions, overlap policy, catch-up windows, start spread and missed-run alerts work the same on every game.