Do not keep repeating the same edit until it works. First prove which file the game reads, whether the game is still writing it, and whether the tag has the exact name and type expected by your Minecraft version.
First check the file you changed
Confirm that the file belongs to the world you actually launched. A common trap is editing a backup, a copied server world, or a similarly named save while the launcher opens a different folder.
- Check the world name and the full folder path.
- Confirm the file timestamp changes when you export a new copy.
- For servers, verify the server.properties level-name points to the folder you edited.
Close Minecraft or stop the server
Check level.dat and level.dat_old
Java Edition normally keeps a previous metadata copy as level.dat_old. If level.dat was replaced or reverted, compare both files on a backup copy. Do not blindly rename files while the game is running, and keep the original pair before testing a repair.
.minecraft/saves/<world name>/level.dat
.minecraft/saves/<world name>/level.dat_oldConfirm the tag type and path
- Open the exported file again and verify the changed value is present in the file you plan to use.
- Follow the complete NBT path, including compounds such as Data, GameRules, or WorldGenSettings.
- Check the tag type: a byte value of 1 is not interchangeable with a string containing 1, and a long seed is not an int.
- Compare the structure with the Minecraft version that created the world; mods can add or rename tags.
Test the exported copy in a duplicate world
- Duplicate the world folder and give the copy a clear test name.
- Apply the exported file to the duplicate while the game is closed.
- Load the duplicate and check the exact behavior tied to the tag you changed.
- Only after the test succeeds should you consider applying the same change to the live world.
Reopen your exported NBT copy
Use the editor to confirm the changed path and value are present before you put the file back into a world folder.
What to do when the old value keeps returning
If the value returns after a restart, stop and compare timestamps instead of editing again. The process may be writing a different copy, the server may be restoring a backup, or a plugin or mod may be enforcing its own setting. Test an unmodified duplicate world to separate a save-path problem from a version or mod problem.
Frequently asked questions
Can an autosave undo a manual NBT edit?
Yes. If Minecraft is still open, its next save can write the in-memory state back to disk. Close it before replacing a file and test the change after restarting.
Why does singleplayer player data not change when I edit playerdata?
Singleplayer player data normally lives inside level.dat under the Player compound. The playerdata folder is used for separate server player files, so use the file-location guide to identify the right target.
Why does a server keep restoring the old value?
The server may still be running, you may have edited the wrong world folder, or a plugin or mod may be rewriting the value. Stop the server fully, verify level-name, and test on a duplicate before touching production data.
Can a tag path change between Minecraft versions?
Yes. Tags, types, and modded structures can differ by version. Compare against a backup from the same version and do not assume a path or numeric type from an older guide is still valid.