Chunkweave reads the file in your browser and exports a separate copy. The source file is never overwritten by Chunkweave, but replacing a file in a live world is still a high-risk operation, so keep the workflow explicit.
The five-step safety checklist
| Step | Do this | Why it matters |
|---|---|---|
| 1. Identify | Match the symptom to level.dat, playerdata, region, or another file | Prevents editing a valid file from the wrong folder |
| 2. Back up | Copy the entire world and keep the original file | Gives you a complete rollback |
| 3. Stop | Close the game or fully stop the server | Prevents in-memory state from overwriting the edit |
| 4. Export | Edit a copy and download a separate result | Keeps the source untouched |
| 5. Verify | Test the exported file in a duplicate world | Catches wrong paths and invalid values before production |
Back up the source before opening it
- Copy the full world folder to a location outside the live saves or server directory.
- Keep a dated copy of the exact source file you plan to edit.
- If the file is playerdata, also preserve related advancements and stats when they matter to the recovery.
Stop, edit, export, and verify
Open the copy in Chunkweave, inspect the complete path, stage only the intended change, and download the result as a new file. Reopen that downloaded file and verify the value before putting it into a duplicate world.
Open a supported NBT file
Inspect and export a separate copy in your browser without sending world data to a server.
Keep a rollback path
Do not delete the source after a successful test. Keep the original world, the edited file, the exported copy, and a short note describing the NBT path and old/new values until you have confirmed a normal restart and save.
Frequently asked questions
Does Chunkweave overwrite my original file?
No. The workflow is designed to export a separate edited copy. You still control where you place that copy, so keep the source and a whole-world backup.
Can I skip the duplicate-world test for a small change?
It is safer not to. A small tag can still be the wrong type or belong to a different Minecraft version. A duplicate test is the quickest way to preserve a rollback.
What should I record for a rollback?
Record the source path, backup location, NBT path, old and new values, Minecraft version, and whether the game or server was stopped during replacement.