PAL SAVE // LOCAL INSTANCESave Editor
SESSION BROWSER ONLY
Open save
NO REMOTE LINK

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.

PAL SAVE EDITOR / LOCKEDSave migration

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.
Open this task Select files inside the App so the local session is preserved.
SymptomLevel 1 characterWorld loads, but login selects a new identity
EvidenceOld Players fileDo not delete it while testing mappings
Special caseCo-op hostHost identity may not behave like a client player
01

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.

02

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.

03

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.

04

Build and test the identity map

Treat the source and target as two separate evidence sets. The target's newly created level-one record is useful because it shows which identity the server selected, while the source Players file preserves the progression you are trying to recover. Never delete either one while the map is unresolved.

A safe recovery plan maps PlayerUID, GUID, file path, display name, owned Pals, guild, bases, inventory, technology, and map state. The final check is not just a level number: each account must log in with the expected identity and retain its linked records.

  1. 01

    Stop the target server

    Prevent another login or autosave from creating more player records while you collect evidence.

  2. 02

    Copy both complete worlds

    Preserve the source and target WorldID folders, including all old and newly created Players files.

  3. 03

    List identity fields

    Record PlayerUID, GUID, file path, display name, owned Pals, guild, bases, and last-modified time for every candidate.

  4. 04

    Propose a one-to-one map

    Match the old progression to the target identity only when the evidence is consistent; keep co-op hosts as an explicit special case.

  5. 05

    Verify every linked record

    Test the restored copy with each account and check inventory, Pals, guilds, bases, technology, Paldeck, and map progress before replacing the target.

Identity reset evidence to compare
RecordSource worldTarget worldDo not accept until
PlayerUID / GUIDOriginal progression identityNew or selected login identityThe mapping is one-to-one
Players fileOld file with inventory and progressNew level-one or empty fileThe intended file is preserved
Owned Pals and guildOriginal ownership linksTarget-side referencesPals, guild, and bases match in game
Inventory and technologyOriginal stacks and unlocksTarget login resultEach player verifies the restored state
SAFE

Task checklist

  1. 01Stop the target server.
  2. 02Back up source and target complete worlds.
  3. 03Keep both old and newly created player files.
  4. 04Map PlayerUID and GUID, not display name.
  5. 05Record file paths and timestamps for every candidate.
  6. 06Verify guild, bases, Pals, inventory, technology, Paldeck, and map state.
FAQ

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.

Why should I keep the new level-one file?

It records the identity the target server actually selected. Deleting it removes evidence needed to build an old-to-new mapping and can make recovery harder.

Can a correct level prove the transfer is fixed?

No. Verify inventory, owned Pals, guild membership, bases, technology, Paldeck, fast travel, and map progress for each affected account.

Does this page rewrite player identities?

No. The page provides recognition and recovery guidance. Identity mapping and rewrite remain locked until every cross-file preservation and round-trip condition is proven.