How to Fix Player Position or Progress Not Saving

Direct answer

If a player returns to an old position after relogging, determine whether player NBT writes fail or a login/spawn plugin teleports them intentionally.

Identify the failing layer

Do not delete player files until you rule out plugins that reset spawn or position. Force-killing Java may also skip outstanding writes.

First checks and evidence

Back up world player data and plugin databases before testing.
Check log messages around logout, world saving and startup for I/O or NBT write errors.

Admin diagnosis and repair

Inspect whether the player UUID remains stable and whether a multiworld/spawn plugin restores a custom position.
Move a test account to a safe coordinate, use a clean stop, restart and compare the actual location.

Verify the fix: The same player should rejoin at the saved position after a normal shutdown and again after an ordinary relog.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?

Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.