If you run a server, read this first
Update your server build to 1.0.2, or your players won’t be able to connect.
Once a player’s client updates to 1.0.2 — which happens automatically on Steam unless auto-update is disabled — it can no longer connect to a server still running the previous build. That’s a version mismatch, not a bug, and it’s the single most actionable line in this whole patch for anyone hosting rather than just playing. If you’re on a managed host, check whether your provider auto-updates server builds or whether you need to trigger it yourself from the control panel; if you’re self-hosting, update the server files the same way you’d update the game client.
What actually changed
A stability patch, not a content drop
No new Pals or biomes here — this is Pocketpair cleaning up the rough edges that surfaced after the full 1.0 launch, and by most accounts, it fixes the issue that was generating the most complaints.
Biggest fixCrashes & disconnections
- The Panthalus boss fight was disconnecting entire dedicated servers mid-battle — this was reportedly the most widely reported issue since 1.0 launched, and it’s fixed here.
- A related crash during the same fight, also dedicated-server specific, is resolved in the same pass.
- A crash triggered by Japanese text input in fullscreen mode is also fixed, unrelated to hosting.
Multiplayer sync
- Terrain could fail to render correctly for a host if a guest was already standing in the World Tree area when the host arrived there — fixed.
- The tower boss “Victor & Shadowbeak” could vanish after a teleport attack mid-fight — fixed.
- In the final boss fight, a guest respawning while the host was mid-victory could end up with broken lighting — fixed.
Missions & achievements
- Two missions (“The First Islander” and “Captured Adventurer”) could leave the screen stuck faded-out if dialogue was interrupted mid-fade — fixed in both.
- The “Predator Hunter” achievement, and a separate achievement tied to collecting Pal Effigies, could fail to unlock despite meeting the requirements — both fixed.
- Xbox specifically had outdated icons on two Lifmunk Effigy achievements — updated.
Graphics, controls & UI
- Mac players saw heavily distorted terrain in the World Tree area, bad enough to block normal play — fixed.
- Certain face types could render the eyes incorrectly during cutscenes or specific actions — fixed.
- New key rebinding options added for “Attack that enemy!” and Inventory.
- Several control-setting bugs fixed, including old settings from pre-v0.7 falsely flagging as conflicts, and middle-mouse-button bindings not applying correctly.
- Mining damage numbers could incorrectly display as 0 — fixed.
Performance
- Reduced processing load specifically in the Sunreach region, which should mean fewer frame drops for anyone playing or hosting a server with that area active.
What people are actually asking
Palworld 1.0.2 — common questions
Almost certainly yes, unless your host has automatic server updates enabled. Player clients update automatically on most platforms, and a client on 1.0.2 cannot connect to a server still on an older build — that’s a version mismatch, not a connection problem. Check your host’s control panel for an update option, or manually update if you’re self-hosting.
Yes — both the server-wide disconnect and the related player-side crash during that specific fight are addressed directly in this patch. It was widely reported as the most disruptive issue since the 1.0 launch. If you were holding off attempting that boss on a dedicated server because of it, this update is the reason to try again.
A follow-up Steam hotfix landed the day after 1.0.2, specifically targeting an infinite loading screen that could occur after defeating the World Tree boss. It’s rolling out to Steam first, with other platforms to follow — worth checking you’re on the latest build if you hit that specific issue.
No, crossplay compatibility is unaffected. The usual rule still applies though — every platform needs to be on the matching version to play together, so if your group spans PC and console, make sure everyone’s updated before jumping back in.
Confirm both your client and server are actually on 1.0.2 first — a mismatched pair can still produce crash-like symptoms that look unrelated to version. Beyond that, our Palworld crash and connection troubleshooting guide covers the other common causes.
Keep reading
