Palworld 1.0.2 and the 1.101.103 Hotfix: What Changed for Dedicated Servers

Palworld 1.0 landed on 10 July 2026 and has been patched three times since. If you run a dedicated server, the one that matters to you is 1.0.2 – it is the release that carried server-side fixes and Sunreach performance work. This is the version history in order, what each patch actually addressed, and which of it changes anything for a server owner rather than a solo player.

Short version: nothing in the 1.0 line has changed the save format or the server configuration file, so an existing world carries forward. What changed is stability, and one hotfix cleared a progression blocker that could strand players mid-fight.

The 1.0 line, in order

What actually changes for a server owner

Take 1.0.2 or later, and take the hotfix

1.0.2 is the only release in this line where server fixes are called out by name, and 1.101.103 clears a progression blocker. If your host still has you on 1.0 or 1.0.1, the two symptoms you are most likely to be chasing are Panthalus instability and players stuck on an infinite loading screen after the World Tree fight. Neither is a configuration problem on your end, and no amount of RAM fixes either.

Your world carries forward

None of the 1.0 patches has been documented as changing the save format or the server settings file. A world made on 1.0 keeps working across 1.0.1, 1.0.2 and the hotfix. That is worth stating plainly, because “will this update eat my world” is the first question people ask and the honest answer here is no.

Take a backup anyway before any version change. Not because this line is risky, but because a backup taken while the server is running is often cut short, and the moment you discover that is the moment you need it. Stop the server, then copy.

The level 80 cap is a slow storage story

1.0 raised the cap to 80 and added 72 Pals. Neither costs you anything on day one. Over months, more Pals caught and more built means each player’s slice of the world grows, and Palworld worlds grow with use rather than with map size. If you are sizing a box for a group that will still be playing at Christmas, size for the world you will have then, not the one you have this week.

What has not been documented

Being straight about the edges: the published notes for this line do not detail dedicated-server configuration changes, network architecture changes, or save-file format revisions. If you have seen a config key change between 1.0 and 1.0.2, it is not in the patch notes, and we would rather say that than invent a changelog entry. Everything above is what has actually been published.

If something is broken after updating

• Players stuck loading after the World Tree boss – that is the 1.101.103 hotfix. Update rather than debug.
• World will not load at all – check the save is intact before anything else; a truncated Level.sav from an interrupted copy looks identical to a corrupt world. The save checker reads it in your browser and finds the newest intact backup.
• Moving a world between co-op and a dedicated server – the character UIDs differ, which is why a migrated character can appear at level 1. The save converter rewrites those references.

Sources

Version numbers and dates from the published Palworld update history and patch notes as of 3 August 2026. Where a detail is not in the published notes, this page says so rather than filling the gap.

Running Palworld for a group? Supercraft Palworld hosting runs on AMD EPYC hardware with NVMe storage, daily backups and in-place plan upgrades, so a world that grows past its box can be resized rather than rebuilt. Live pricing for your region is on the plan page.