SaveGuard Cyber Shield Logo
SaveGuard Palworld
CheckMySave.com
Palworld Migration Guide Updated September 2026

How to Fix Palworld Co-op Host Character Reset to Level 1 (0000...0001 GUID Migration)

Migrating your 4-player co-op save to a Windows or Linux dedicated server? If all guest players kept their characters but the host was prompted to create a new character, this complete guide will help you restore full character level, inventory, and party Pals.

🛡️ Pre-Flight Verification: Test Your Save First

Confirm whether your save still has the 0000...0001 slot and check for headless guilds before making changes.

Open Scanner

# Why Does the Host Lose Their Character?

In local 4-player listen co-op, Pocketpair hardcodes the hosting player's internal GUID to:

00000000-0000-0000-0000-000000000001 (00000000000000000000000000000001.sav)

However, when you host a Dedicated Server (SteamCMD, Windows Server, or Linux Docker), the server authenticates connecting players using their real Steam ID or Xbox GUID. Because the dedicated server cannot associate your authentic Steam ID with the dummy 0000...0001 slot, it considers you a first-time player and opens the character creator screen at Level 1.

00

Step 0: Pre-Migration Health Check

Before modifying game files or running Python scripts, run your save through CheckMySave.com:

  • Host Slot Detection: Confirms if 00000000000000000000000000000001.sav is still unmigrated.
  • Headless Guild Check: Ensures the host character isn't the sole admin of a guild that will crash the server upon Palbox interaction.
  • WorldOption Override: Checks if WorldOption.sav is present (which blocks custom server settings).
  • 100% Client-Side: Operates locally inside your browser via WebAssembly (zero files are ever uploaded).
01

Step 1: Locating Your Co-op Save Files

On your local computer where the co-op game was hosted:

  1. Press Win + R, type %LocalAppData%\Pal\Saved\SaveGames, and press Enter.
  2. Open the folder with your 17-digit Steam ID.
  3. Open your specific world folder (a 32-character hexadecimal string, e.g. 2E85FD38BAA792EB1D4C09386F3A3CDA).
  4. CRITICAL: Make a complete backup copy of this folder to your Desktop before proceeding!
02

Step 2: Generate the Host's Real GUID on the Dedicated Server

To transfer the old character, you need to know the host's new dedicated server GUID:

  1. Copy the save folder to your dedicated server at PalServer/Pal/Saved/SaveGames/0/<SaveName>.
  2. In PalServer/Pal/Saved/Config/WindowsServer/GameUserSettings.ini (or LinuxServer), verify that DedicatedServerName matches your save folder name.
  3. Start the dedicated server and connect as the host player.
  4. When prompted, create a temporary new character and spawn into the world.
  5. Disconnect from the server and shut down the server process.
  6. Look inside PalServer/Pal/Saved/SaveGames/0/<SaveName>/Players/: you will now see a brand new <NewGUID>.sav file. That filename is the host's authentic dedicated server GUID!
03

Step 3: Transfer Character Data Using palworld-host-save-fix

Use the community migration tool palworld-host-save-fix (by xNul / cheahjs):

python fix_host_save.py <save_path> <new_guid> 00000000000000000000000000000001 False

Where:

  • <save_path>: Path to your temporary save folder.
  • <new_guid>: The 32-character GUID generated in Step 2.
  • 00000000000000000000000000000001: The old co-op host dummy GUID.
  • False: Guild fix parameter (set to False for standard co-op migration).
04

Step 4: Verify and Restart the Server

Copy the modified save folder back into your dedicated server directory. Before starting the server, drop the folder into CheckMySave to verify that the 0000...0001 slot is cleared and player parity is green. Launch the server, log in, and you will spawn with your full original level, equipment, technology unlocks, and party Pals!