Losing save data is one of those things that can kill a game session entirely. For some Palworld players jumping into 1.0, that was a real risk, and Pocketpair has moved quickly to close it down. Patch 1.0.1 landed shortly after launch and targets four specific bugs that were quietly making life harder across PC, Xbox, and PS5.
The save data bug that nobody wants to talk about
The most serious fix in this patch addresses a bug where save data could be "unintentionally discarded after certain operations." Pocketpair hasn't spelled out exactly which operations triggered the loss, but the phrasing suggests it wasn't a rare edge case. For a game where players are sinking dozens of hours into base building and Pal collecting, silent save deletion is about as bad as it gets.
Here's the thing: this lands right as Pocketpair has been publicly encouraging players to start fresh saves for the full 1.0 experience. If you were on the fence about wiping your old world, our guide on whether you should start a new save or keep your old one in Palworld 1.0 breaks down exactly what you stand to gain and lose either way.
Xbox players were hitting a 30-second wall at every fast travel
For anyone on Xbox, teleporting between locations was causing the game to freeze for roughly 30 seconds before resuming. That's not a minor stutter. In a survival game where you're constantly moving between your base, dungeons, and resource nodes, a half-minute hard stop every time you use fast travel makes the whole system feel broken.
Patch 1.0.1 resolves the freeze entirely. Teleporting should now behave the same way it does on other platforms.
A PS5-specific save error on the title screen
PS5 players were running into a separate save-related problem: a save error that would "repeatedly occur when attempting to return to the title screen." The looping nature of it made the issue particularly disruptive, since returning to the title screen is a standard part of session management, not something players should have to avoid.
That fix is also confirmed in this patch.
The campfire burn that kept burning
The fourth fix is less catastrophic but still noticeable. A bug was causing the burning status effect to persist on a player character even after they touched a campfire, meaning the fire damage kept ticking long after contact ended. Campfires are a basic survival mechanic in Palworld, so having the burn linger past the point of contact was a genuine annoyance for early-game players.
All four fixes are live now across platforms.
Four bugs, but the bigger picture matters
Patch 1.0.1 is a small list compared to the enormous 1.0 launch notes, which brought 72 new Pals, a reworked story, a level cap raise to 85, and an entirely new sky island zone. If you want the full breakdown of everything that changed at launch, the Palworld 1.0 major changes and additions guide covers all of it in detail.
The speed of this hotfix matters. Palworld 1.0 pulled over 855,000 concurrent Steam players during its first weekend, a number that puts it among the largest Steam peaks ever recorded. With that kind of active player base, bugs affecting save integrity and core navigation need fast turnarounds. Pocketpair delivered one within days of launch, and the studio has already signaled that more content is in development beyond the already-announced Palfarm and Palworld dating sim spin-offs.
The patch is out now. Load up your world.
