How to Update a Palworld Server (SteamCMD, Steam, Docker and GameTeam)

To update a Palworld server, stop it, back up Pal/Saved, run steamcmd +login anonymous +app_update 2394010 validate +quit, and start it again. If you installed the server through the Steam client, Steam updates the Palworld Dedicated Server tool for you. On GameTeam it’s one step: stop the server in the panel and start it, and it updates itself to the latest version as it boots. Every setup is covered below, plus what to do when the update breaks something.

Why you have to update the server

A Palworld dedicated server and its players have to be on the same version. When Palworld patches, players’ games update and a server still on the old build can’t let them in. So every game update means a server update, ideally the same day, and every player updating their game too.

Before any update: back up

Updates are when worlds get lost, so back up before every one. Pocketpair’s own Docker guide opens its update section with exactly that. Stop the server first so nothing is half-written, then copy the whole Pal/Saved folder: it holds the world (SaveGames) and your settings (Config).

  • Self-hosted: copy steamapps/common/PalServer/Pal/Saved somewhere outside the server folder.
  • Docker: copy the mounted ./Saved folder.
  • GameTeam: use Backup Now in the panel, or ask the copilot to back up the world. Premium plans also take automatic daily backups.

How to update a Palworld dedicated server with SteamCMD

SteamCMD updates the server with the same command that installed it: app ID 2394010, anonymous login, and validate to check every file. Stop the server, run the command, start the server. It works the same on Windows and Linux, and only downloads what changed.

  1. Stop the server. If players are on, warn them first as admin: /Broadcast Updating in 5 minutes, then /Save and /Shutdown 60 Updating.
  2. Run SteamCMD:
    steamcmd +login anonymous +app_update 2394010 validate +quit

    On Windows run it from your SteamCMD folder as steamcmd.exe; on Linux it’s usually steamcmd or ./steamcmd.sh. If you installed the server into a custom folder, update it the same way you installed it so the files land in the same place.

  3. Start the server again: PalServer.exe in steamapps\common\PalServer on Windows, ./PalServer.sh in ~/Steam/steamapps/common/PalServer on Linux. Use the same launch arguments as before.

Want to confirm the version? If you run the REST API, its info endpoint returns the server version. Otherwise the quickest test is a friend on the latest game joining.

Update through the Steam client

If you installed Palworld Dedicated Server from your Steam Library (filter: Tools), Steam treats it like any other app and downloads updates when they come out. Close the server before Steam updates it. If an update doesn’t start on its own, open Steam’s Downloads page and start it there, then launch the server again with Play.

Update a Palworld server in Docker

With Pocketpair’s official image, the version is the image tag in compose.yaml. To update, back up, stop the container, change the tag to the new game version, and start it again. Nothing inside the container needs touching.

docker compose down
# edit compose.yaml: image: ghcr.io/pocketpairjp/palserver:<new version tag>
docker compose up -d

The community thijsvanloef/palworld-server-docker image works differently: with UPDATE_ON_BOOT=true (the default) it updates the server every time the container starts, so a restart is an update. It can also update on a schedule: set AUTO_UPDATE_ENABLED=true with a cron in AUTO_UPDATE_CRON_EXPRESSION, and it warns players AUTO_UPDATE_WARN_MINUTES ahead (30 by default). Scheduled updates need RCON_ENABLED and UPDATE_ON_BOOT set to true.

How to update a Palworld server on GameTeam

There’s no command to run. Stop the server from the GameTeam panel, then start it: the server checks for the latest Palworld build and installs it on the way up. Your world and your settings stay where they are. Warn players before you do it, or ask the copilot to handle the whole thing.

  1. Back up the world (Backup Now, or tell the copilot).
  2. Click Stop, wait for the server to shut down, then Start.
  3. Join and play. If the server crashes on start with signal 11 or exit code 139 after a big Palworld patch, that’s the server image, not your world: ask the copilot to update the image. It’s a one-line change and nothing in the save is lost.

Updating a modded server

Mods are the part of a Palworld server update most likely to go wrong. UE4SS and many mods have to be updated after a patch, and one outdated mod can stop the server starting. Before updating, note which mods you run and remove the ones whose authors haven’t released a version for the new patch. Then update the server and UE4SS, and reintroduce mods one by one.

Workshop mods loaded through Pocketpair’s official PalModSettings.ini system are easier: when a mod’s version changes, the next restart removes the old files and deploys the new ones. The full routine is in how to add mods to a Palworld server.

Problems after a Palworld server update

Problem Likely cause Fix
Friends still can’t join Their game hasn’t updated, or the server didn’t Have everyone update and restart the game; confirm the server version
Crash on start, signal 11 / exit code 139 Outdated server image or build Update the image or re-run the SteamCMD update
Crash on start, a mod named in the log Mod not updated for the new version Start with -NoMods, then add mods back one by one
Settings back at default The file was regenerated by a panel or Docker image, or its header line broke Restore PalWorldSettings.ini from your backup (settings guide)
Everyone starts over in a fresh world The server made a new world because DedicatedServerName in GameUserSettings.ini no longer points at your world folder Set it back to your world folder’s name; see when an update wipes player progress
SteamCMD can’t find the server Updating into a different folder than you installed to Run the update the same way, into the same folder, as the install

Other crash causes are in why a Palworld server keeps crashing.

FAQ

How do I know my Palworld server needs an update?

The usual sign is friends on the latest game suddenly unable to join. Self-hosted, check whether Steam shows an update for Palworld Dedicated Server, or compare the version from the REST API’s info endpoint with the game’s.

Does updating delete my world?

It shouldn’t: the world lives in Pal/Saved, not among the program files an update replaces. But big patches are when saves go wrong, which is why the backup step comes first.

Do my friends need to update too?

Yes. The server and every player must be on the same version. Steam and the console stores usually update the game on their own; anyone who can’t join should restart their game and check for an update.

How long does an update take?

It depends on the size of the patch. SteamCMD only downloads files that changed, so small patches are quick and big content updates take longer.

Should I turn on automatic updates?

For a small private group, yes, with a warning to players before the restart. On a modded server, update by hand so you can check mods first.

Skip the update routine

Patch day shouldn’t mean an evening of SteamCMD. On GameTeam’s Palworld server hosting you stop and start the server and it’s on the new build. Or hand it to the AI copilot: “back up the world, then update the server” makes a backup and locks it so it won’t get deleted, restarts onto the latest build, and if the old image would crash on the new version, it updates the image too. It reads the log afterwards and tells you whether everything came up clean. Pay per GB of RAM from $0.49/GB a week, unlimited slots. Running your own? The Palworld dedicated server guide covers the full setup, and port forwarding sorts out friends who still can’t connect.

Total
0
Shares
1 comment
Leave a Reply

Your email address will not be published. Required fields are marked *

Related Posts
Cookie Settings