Palworld: Restoring Saves & Fixing "Fresh World" Bug
A common nightmare for Palworld admins is restarting the server only to be asked to "Create Character" again. Usually, your save isn't gone—the server simply forgot where to look.
1. The Cause
The server tracks which save folder to load via the DedicatedServerName string in the config. If this resets or mismatches, the server generates a brand new folder.
2. The Check
Before panicking, check /Pal/Saved/SaveGames/0/. If you see TWO folders (e.g., your old 2F4A... and a new 8B1C...), your data is safe.
3. The Fix
We need to tell the server to ignore the new folder and point back to the old GUID folder.
Step-by-Step Recovery Guide
- Stop the Server immediately to prevent new data from overwriting old backups.
- Open **File Manager** and go to
/Pal/Saved/SaveGames/0/. - Identify the folder with the **larger size** or **older date** (this is your original save). Copy its name (the long random string).
- Navigate to
/Pal/Saved/Config/LinuxServer/. - Edit
GameUserSettings.ini. - Find the line:
DedicatedServerName=.... - Paste your original folder name here.
Example:DedicatedServerName=2F4A9999... - Save and Restart.
"I'm Still Level 1 but the World is Built?"
If you log in and see your base, but you are forced to create a new character, this is a **GUID Mismatch**.
- This happens when moving from Co-op to Dedicated, or changing server ownership.
- The game has assigned you a new UserGUID because you are connecting via a different method.
- **Solution:** You must use a Python script to migrate your old character data (`.sav`) to the new GUID. Use the Palworld Host Save Fix tool.
Emergency: If fixing the config doesn't work, delete the contents of the config file `DedicatedServerName` (leave it blank). Start the server, let it generate a new folder, stop it, then COPY the contents of your OLD folder into the NEW folder.
Never lose progress. Host your Palworld server with Supercraft, where our automated systems handle GUID mapping and daily backups for you.