UUID-named DAT files
Open the individual .dat file associated with the player you intend to inspect.
Open a UUID-named .dat file from a Java Edition world's playerdata folder, review nested tags, stage careful edits, and export a separate copy.
Files are parsed and rebuilt locally in your browser. Nothing is uploaded to Chunkweave.
A player file may contain nested compounds, lists, inventory data, coordinates, status values, and version-specific fields. Chunkweave shows the raw typed structure so you can see exactly where a value lives before changing it.
Open the individual .dat file associated with the player you intend to inspect.
Follow compounds and lists instead of editing a flattened or lossy representation.
Review staged values and original content before saving the complete batch into a new copy.
A running server can write its in-memory player state back to disk and overwrite manual changes. Stop the server safely, retain the original file, and test the edited copy in a controlled environment.
They are normally stored as UUID-named .dat files inside a world's playerdata folder. Server layouts and backups may place copies elsewhere.
Yes. Chunkweave can open Java Edition playerdata .dat files as typed NBT trees, stage changes, and export a separate copy locally.
You should not. Stop the server or ensure the player data is not active, make a backup, and follow the server's safe maintenance procedure before replacing a file.
No. The editor preserves NBT types and structure, but it cannot guarantee that a value is valid for your Minecraft version, server, datapacks, or mods.
Open a supported Minecraft Java Edition file, stage edits, and export a separate copy without sending world data to a server.