Error fingerprint CHARACTER-RESET
Palworld character reset after transfer usually means identity changed.
The old player file may still be present. Stop the server, preserve both source and target worlds, and map the original PlayerUID and GUID to the identity created on the target.
Open the source world for migration
A safe migration needs complete source and target worlds plus explicit player identity mapping.
Platform clues and missing-file diagnosis are available. GUID rewrites, host changes, and ownership migration are not.What happened
The target server associated the login with a different player ID or GUID. Palworld created or selected a new Players/*.sav record while the original progression remained under another identity.
Safest recovery sequence
Stop the target server and copy its current world. Preserve the source world separately. Inventory all player files on both sides, identify the newly created target identity, then build an explicit old-to-new map. Handle the co-op host as a separate unresolved record until confirmed.
Verify more than player level
A successful identity repair should restore guild membership, bases, Pal ownership, inventory, technology, map progress, and other cross-file links. A correct-looking level alone does not prove the mapping is complete.
Task checklist
- 01Stop the target server.
- 02Back up source and target complete worlds.
- 03Keep both old and newly created player files.
- 04Map PlayerUID and GUID, not display name.
- 05Verify guild, bases, Pals, inventory, technology, and map state.
Questions people ask before touching the save
Is my old character deleted?
Often it is still stored in another player file. Preserve the folders before testing any mapping fix.
Can I rename the old player file to the new GUID?
Filename replacement alone may leave world-side references unchanged. A safe fix must update every required identity link.