Reviewed status: Palworld v1.0.3 on August 28, 2026. This guide owns the update intent for an existing server: save the world, align server and clients, review current configuration and test a full join. For a new installation, use create a Palworld Dedicated Server. Handle detailed mod cleanup with install and manage Palworld mods.

What matters to a server since Palworld 1.0

Pocketpair released Palworld 1.0 in July 2026. Existing save data can continue, but a tested external backup still belongs before every major version change. The full release added Sunreach, the World Tree and 72 Pals alongside changes to bases, multiplayer and performance.

Follow-up fixes matter too:

  • v1.0.2 fixed Dedicated Server crashes and disconnects during the Panthalus battle and reduced processing load in Sunreach.
  • v1.0.3 added balance adjustments and bug fixes; the official Dedicated Server documentation is now explicitly versioned 1.0.3.

Track current releases and sources in the Palworld update hub.

Save the world and operating state first

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

  • world and save data,
  • the active PalWorldSettings.ini,
  • startup arguments,
  • manually or Workshop-installed mods,
  • the last working server build where your operating path provides it for rollback.

Confirm that the backup is readable and current. A filename alone does not prove that restoration will work.

Align server and clients

Update through the intended hosting workflow and perform the first boot without mods that have not confirmed compatibility. Every player updates to the same compatible build. Failed joins after a patch often come from client/server or mod drift rather than the world itself.

Inspect the startup log for the detected version, repeated crash loops and configuration warnings. Use one test account before ending maintenance for everyone.

Compare PalWorldSettings.ini with v1.0.3

On Linux, Pal/Saved/Config/LinuxServer/PalWorldSettings.ini is active. DefaultPalWorldSettings.ini is only the template and edits there have no effect. The directories appear after the first server start.

Current settings to review include:

  • 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 notes that, from v1.0 onward, leaving -useperfthreads -NoAsyncLoadingThread -UseMultithreadForDS unset may perform better. Do not remove them blindly in production: compare startup time, logs and load with the same world in a controlled test.

Run a complete functional test

After the update, verify:

  1. The server starts without a new repeating error.
  2. The correct world loads with bases, Pals, guilds and progress.
  3. A test account can join fully and interact.
  4. Admin authentication and /Save work.
  5. Required platforms can connect through crossplay.
  6. Only then are confirmed mods returned one by one.

For platform failures, use Palworld crossplay; for load, use Palworld performance and RAM.

Troubleshooting

The server does not start after updating

Start without mods, compare the active ini with current documentation, and inspect the first relevant log event rather than only the final cascade. If startup remains broken, stop additional writes and work from the saved world copy.

The world looks empty or wrong

Confirm the server is loading the correct save path and world. Restore a backup only after excluding the wrong slot, path or permissions.

Crossplay players cannot join

Compare client/server builds, CrossplayPlatforms, address and port. The default array permits Steam, Xbox, PS5 and Mac, but does not replace version parity.

Load increases after the update

Compare the same world and player count without mods. Inspect bases, active Pals and backup disk load; do not reuse a universal RAM table from an old patch article.

Primary sources

FAQ

Must I start a new world for v1.0.3?

No. Existing save data can continue. Still back it up and verify it after updating, especially with mods or very old data.

Which file should I edit?

On Linux, edit Pal/Saved/Config/LinuxServer/PalWorldSettings.ini, not only DefaultPalWorldSettings.ini.

Which version should players run?

The same compatible version as the server. v1.0.3 is current on the review date.

Does detailed mod cleanup belong here?

Only as an update gate. Inventory, removal and step-by-step reintroduction belong to the specialist mod guide.