Palworld Character Clone Bug: Fix Duplicate Players
Some dedicated servers create a "clone" of a player after a transfer, cross-platform login, or a bad reconnect. The result is a fresh character with empty inventory while the original data still exists on disk. Use the steps below to restore the correct save and prevent it from returning.
If the clone appeared because the player's ID actually changed - a new Steam account, a platform switch, or a world moved out of co-op onto the server - the old character is still on disk under the old ID, and deleting a file will not bring it back. The free Palworld Save Converter rebinds that character to the ID the server now hands them, in your browser with nothing uploaded: level, tech points, unlocked recipes, map and fast-travel unlocks, Paldeck, inventory, party Pals and palbox all move with it.
Symptoms
- Player joins and spawns as a new character with default gear.
- Old base ownership or map progress appears missing for that player.
- Multiple player files exist for the same person in the server save.
Common Causes
| Cause | Why It Happens |
|---|---|
| Account ID mismatch | Joining with a different Steam/Xbox account creates a new player ID. |
| Partial server transfer | World moved without the full Players folder or all player saves. |
| Corrupted player save | The server fails to load the file and generates a blank profile. |
| Guild leaving bug | Someone leaves the guild while other members are offline, corrupting their saves. |
| Server type migration | Moving saves between co-op, Windows server, and Linux server causes GUID mismatches. |
Guild Bug Warning: The guild leaving bug can cause affected players to see an infinite loading screen when trying to join. If multiple players experience this simultaneously, it's likely caused by a guild member leaving while others were offline.
Fix: Restore the Correct Player Save
- Back up the server. Use your host backup tool or the backup restore guide to create a safety copy.
- Stop the server. Do not edit save files while the server is running.
- Find the correct player ID. Log in as admin and run
/ShowPlayersto list player IDs. - Locate player saves. Open
/Pal/Saved/SaveGames/0/<WorldID>/Players/and sort by modified time. - Move the wrong file. Move the newer or empty profile to a backup folder and keep the correct
.savfile. - Restart and test. Start the server and have the player join again.
Advanced Fix: Guild Bug Recovery
If multiple players are stuck on infinite loading screen due to the guild bug, use community save tools:
- Install Python 3.x and a text editor like Notepad++
- Download save tools:
- palfix - Merge a duplicated character save back into the original player profile
- palworld-save-tools - Convert .sav to JSON for editing
- Palworld Save Converter - rebind a character's GUID in your browser (host or any player, 1.0 and Game Pass saves)
- palworld-host-save-fix - the original command-line GUID fix (pre-1.0 formats)
- Convert and edit: Export player saves to JSON, fix corrupted GUIDs, reimport
- Test thoroughly: Have affected players test before declaring success
Prevention Tips
- When migrating servers, copy the entire world folder, not just
Level.sav. See character transfer. - Avoid switching platforms for the same character unless the server supports crossplay.
- Schedule backups before updates and major configuration changes.
- Warn players: Don't leave guilds while other members are offline.
- Keep backups of the Players folder separately for quick recovery.
Important: If you delete the wrong file, the player will lose progress. Always keep a copy of any removed .sav file so you can roll back quickly.
Keep your saves stable. Host your Palworld server with Supercraft and use automated backups to recover from data issues in minutes.