Patch Day

Palworld ships hotfixes frequently and enforces strict client/server version lockstep, which is why patch-day automation is one of PalCommand’s most valuable features. On update detection, PalCommand drains the server gracefully (announce, save, shutdown), snapshots the save and config, updates through SteamCMD, verifies the new build, and relaunches, without you doing anything.

Seeing that an update is pending

A server with an update waiting shows an amber Update available chip on its dashboard card. The Dashboard’s stats strip also has an “Updates pending” cell; once anything is pending, it grows an Update all → link.

Dispatching an update

Three ways to trigger one:

• Click the Update available chip on a card to update just that server. The confirm’s button reads Update now. The card’s overflow menu also carries a plain Update item, which works whether or not an update was detected. Neither lives on the server’s own page: patch-day actions stay on the dashboard card.
• Update all → in the stats strip dispatches every server with a pending update. Busy or crash-looping servers are skipped rather than forced. The confirmation toast is worded off how many actually got dispatched, e.g. “Update dispatched for 3 of 5 servers” if two were skipped.
• Check for updates (Dashboard header) checks right away instead of waiting for the next automatic check.

Every update dispatch confirms first. If players are online, the dialog states the count and warns they’ll get an announced countdown before the server saves and restarts.

Automatic dispatch

On a server’s Schedule tab, the Automatic updates card offers Manual (you or a scheduled task decide when) or Immediately (a detected patch applies right away, with a configurable announce-seconds warning). A cron Update task in the schedule table below it is the way to apply patches on a fixed window instead, for example overnight.

While it runs

The card’s status pill turns amber and cycles through phases as it goes: draining, snapshotting, installing, verifying, relaunching. There’s no exact percent to show for the install step, so the card shows a plain progress sweep rather than inventing a number.