New in v1.0.4: Retest Server, Mods, and Building Rules

Pocketpair released v1.0.4 on September 7, 2026. Relevant for dedicated servers are a fixed crash when sorting Pals, corrected access permissions when using chest materials, and a new setting for a per-player building limit. Version mismatches now display the version of the connection target.

After the update, test joining, sorting Pals, and using materials with the permissions actually configured, on a backed-up world. For the new building limit, don't guess an ini key: use the parameter documented for your installed build, or an existing setting for it. The patch notes don't name a configuration key here.

Source: Pocketpair: v1.0.4.

Update note checked on September 8, 2026: Palworld v1.0.4. Here's how to update an existing server: back up your world, align server and clients, check your current configuration, and test joining. For a fresh install, use Create a Palworld Dedicated Server. The detailed cleanup of old mods is covered in Migrate Palworld 1.0 Mods.

What's Been Relevant Server-Side Since Palworld 1.0

Pocketpair released Palworld 1.0 in July 2026. Existing save files can continue to be used; an externally verified backup remains mandatory before any major version change. The full release added, among other things, Sunreach, the World Tree, and 72 new Pals, as well as changes to bases, multiplayer, and performance.

Corrections followed afterward:

  • v1.0.2 fixed crashes and connection drops during the Panthalus fight on dedicated servers and reduced the load in Sunreach.
  • v1.0.3 brought further balance and bug fixes; the linked documentation may since carry a newer version. Check its version selector.

You can also find current patch statuses and sources in the Palworld Update Hub.

Before Updating: Back Up Your World and Operating State

Set an AdminPassword, authenticate in-game with /AdminPassword <password>, and run /Save. Then stop the server cleanly. Back up at least:

  • World and save data,
  • the active PalWorldSettings.ini,
  • startup parameters,
  • manually or Workshop-installed mods,
  • the last working server build, provided your hosting setup keeps it available for a rollback.

Check that the backup is actually readable and up to date. The mere existence of a file name doesn't prove a restorable backup.

Bringing Server and Clients to the Same Build

Update the server through your designated hosting process and start it initially without unconfirmed mods. All players update their clients to the same compatible version. A common reason for failed connections after a patch isn't the world, but build or mod drift between client and server.

Check the startup log for the detected version, repeated crash loops, and configuration warnings. Connect with a test account first before ending maintenance for everyone.

Checking PalWorldSettings.ini Against Your Build's Documentation

On Linux, Pal/Saved/Config/LinuxServer/PalWorldSettings.ini is the active file. DefaultPalWorldSettings.ini is only the template; changes there have no effect. The directories are only created after the first server start.

Particularly relevant today are:

  • CrossplayPlatforms=(Steam,Xbox,PS5,Mac) as the documented default,
  • bIsUseBackupSaveData for rolling world backups with additional disk load,
  • AdminPassword, ServerPassword, and ServerPlayerMaxNum,
  • bAllowClientMod for controlled mod access.

Pocketpair also points out that, since v1.0, omitting the old arguments -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS can improve performance. Don't remove them blindly on a production system: compare startup time, log, and load with the same world in a controlled test.

Running a Complete Functional Test

After the update, check:

  1. The server starts without new recurring errors.
  2. The correct world loads with bases, Pals, guilds, and progress.
  3. A test account can fully join and interact.
  4. Admin authentication and /Save work.
  5. The required platforms can connect via crossplay.
  6. Only afterward do confirmed mods come back, one at a time.

For platform errors, see Check Palworld Crossplay; for load questions, see Plan Palworld Performance and RAM.

Troubleshooting

Server Won't Start After the Update

Start without mods, compare the active ini with the current documentation, and check the first relevant log event instead of just the last follow-on error message. If the start remains broken, stop further write attempts and work with the backed-up world copy.

The World Looks Empty or Wrong

First check whether the server is loading the correct save path and world. Only restore a backup once a wrong slot, path, or permissions error has been ruled out.

Crossplay Players Can't Join

Compare client and server build, CrossplayPlatforms, address, and port. The documented default array allows Steam, Xbox, PS5, and Mac, but it doesn't replace a version check.

Load Increases After the Update

Compare the same world and player count without mods. Check bases, active Pals, and backup disk load; don't adopt a blanket RAM table from an old patch announcement.

Primärquellen

FAQ

Do I Need to Start a New World for the Update?

No. An existing world can continue to be used. Back it up anyway and check it after the update, especially if you're using mods or have very old save data.

Which File Do I Need to Edit?

On Linux, the active Pal/Saved/Config/LinuxServer/PalWorldSettings.ini, not just DefaultPalWorldSettings.ini.

Which Version Should Players Use?

The same compatible version as the server. As of September 8, 2026, v1.0.4 is the patch version checked here.

Does Mod Cleanup Belong Here?

Only as an update gate. The complete inventory, removal, and step-by-step reintroduction of old mods is covered in the separate mod migration guide.