When a server world is opened in singleplayer, Minecraft may create a new local player identity. The terrain and world settings come across, but the old inventory, position, and Ender Chest remain under the server player's UUID file until you copy the relevant data into the singleplayer save.
Why the world loads but your player is empty
A dedicated server stores each player's state in <world>/playerdata/<uuid>.dat. A singleplayer save normally stores the active player under level.dat / Data / Player. Opening the same world folder does not automatically merge those two structures.
Find the server UUID file
- Make a copy of the original server world and the singleplayer copy.
- Look in the server world's playerdata folder for UUID-named .dat files.
- Match the username to a UUID using usercache.json from the server or a trusted account lookup.
- Open the matching playerdata file and confirm the position or inventory is the one you expect before copying anything.
<server-world>/playerdata/<player-uuid>.datUnderstand the singleplayer Player compound
| Source | Useful data | Destination in the singleplayer save |
|---|---|---|
| Server playerdata .dat | Pos, Rotation, Dimension, Health | level.dat / Data / Player |
| Server playerdata .dat | Inventory and SelectedItemSlot | level.dat / Data / Player / Inventory |
| Server playerdata .dat | EnderItems | level.dat / Data / Player / EnderItems |
Copy only the data you need
- Back up the full singleplayer world folder and the original server playerdata file.
- Open the server UUID file and the singleplayer level.dat copy in separate editor tabs or windows.
- Copy only the compounds you intend to restore, such as Inventory, EnderItems, Pos, or Dimension.
- Preserve the singleplayer file's surrounding structure and export a separate edited level.dat copy.
Test in a duplicate world
- Rename the edited copy as a test save and leave the original singleplayer world alone.
- Load the test world and check inventory, Ender Chest, position, and dimension one at a time.
- If the player loads in an unsafe location, use a known safe Pos and Dimension from the backup rather than guessing.
- Keep the backup until you have closed and reopened the test world successfully.
Open a playerdata file
Inspect the server player's typed NBT tree before moving selected data into a singleplayer save.
If the old player data is already overwritten
Stop editing and look for a server backup, level.dat_old, a hosting snapshot, or an older copy of the playerdata folder. If no backup contains the old file, recovery may be limited to items or coordinates recorded elsewhere; do not assume the current empty file can recreate the old inventory.
Frequently asked questions
Does this also apply to a LAN world?
A LAN world hosted from singleplayer still uses the host's singleplayer Player compound. The dedicated-server playerdata workflow applies when the world was saved by a server with UUID-named player files.
Can I do this while players are online?
No. Only edit data for a server you administer, stop the server fully, and wait for all processes to release the world files before replacing anything.
Do I need both a world backup and a playerdata backup?
Yes. Keep a copy of the whole world and the original UUID file. A player-only backup is useful for comparison, but the whole-world copy is the safer rollback if metadata or region files are also changed.
Why did my Ender Chest not come back?
Ender Chest contents are stored in EnderItems inside the player data. Copy that compound deliberately, verify the tag type and list structure, and test on a duplicate world before using the live save.