A player changes their name and their character turns into a stranger's

Saves filed under a player's name break the moment names change or are given to someone new. Here is how to move old name-based saves onto stable accounts, what to do when two old saves belong to one person, and what must be left alone.

Why this works

A name is something people change and others may take, so it cannot be what ties a save to its owner. A number that never changes and is never reused can, and any old save that cannot be matched with certainty is kept, not guessed at.

When not to use it

Not possible for a game with no accounts, such as a guest-only arcade, where the name or a code the player keeps is all there is. In that case ask them to write down a recovery code, and never promise more.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 4 common mistakes and the fix
• A diagram of every state
• 33 lines of example code with 4 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "A player changes their name and their character turns into a stranger's" (read_entry save-by-account-not-by-name) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP