RBRaidBench Latest Updates
RaidBench / Patch Watch / Palworld

Palworld ยท v1.0.1

Palworld v1.0.1 save-data fix: what players should do next

A cautious post-update checklist after the official fix for unintended save-data discards and the persistent burning-status issue.

Current hotfix Official update: 2026-07-15 Reviewed: 2026-07-17 How RaidBench reviews updates

Did Palworld v1.0.1 fix the save-data problem?

Short answer

The official v1.0.1 notes say the update fixed an issue that could unintentionally discard save data after certain operations. It also fixed a burning status that could continue after touching a campfire. Update the game before resuming important progression, then verify that the expected world and character save loads correctly before making major changes.

AreaWhat it means
FixedAn issue that could unintentionally discard save data after certain operations.
Also fixedBurning status continuing after contact with a campfire.
Player actionInstall v1.0.1 and verify the correct save before a long session.
Server actionConfirm host and client versions match before multiplayer progression.
Risk postureKeep normal backups where the platform or server workflow allows them.

Player checklist

  1. Confirm the title screen or platform update history shows v1.0.1 or later.
  2. Load the intended world and check recent structures, inventory, and progression.
  3. Avoid overwriting a suspicious save until the correct file or backup is identified.
  4. For multiplayer, confirm the host has updated before reconnecting.
  5. Keep backup practices in place even after a specific bug is fixed.

What this update does not prove

The short hotfix note addresses two named bugs; it is not a guarantee against every possible save, mod, server, or platform problem.

Refresh trigger

Review after any later save-system hotfix, rollback notice, or platform-specific advisory.