Skip to content

Instantly share code, notes, and snippets.

@Darkere
Last active April 8, 2024 02:05
Show Gist options
  • Save Darkere/9e2ebda80a92a91d9257cfc2bcc016a5 to your computer and use it in GitHub Desktop.
Save Darkere/9e2ebda80a92a91d9257cfc2bcc016a5 to your computer and use it in GitHub Desktop.
Finding and editing chunks with NBT Explorer

Finding and editing chunks with NBT Explorer

Download: https://github.com/jaquadro/NBTExplorer/releases

Alternatively NBT Studio is much faster and cleaner but works the same way https://github.com/tryashtar/nbt-studio/releases/

1. Figure out which chunk you are going for.

1.a If you are crashing due to an entitiy or tileentity the crashlog might contain the exact coordinates

1.b If you have a waypoint there for example checking your map files can be helpful

1.c If your player is in the same chunk you can look up your players position

1.c.1 Look up your UUID on https://mcuuid.net

1.c.2 Load up your file under world/playerdata and open it with NBTExplorer

1.c.3 Position should be easy to find.

image

2. Look up where the chunk is stored

2a. Put in your coords or chunk coords on https://dinnerbone.com/minecraft/tools/coordinates/

2b. At the bottom it will show which region file the chunk is in.

image

3. Opening up the region file

3a. MAKE A BACKUP. It is very easy to corrupt chunks here.

3b.Open up the region file (world/region/) in NBTExplorer

3c. Navigate to the chunk (the numbers after "in world at" should match up with chunk x and chunk z on the website)

4. Do what you need to do.

4a. You can see all entities and Tile Entities in the chunk in a simple list. You can delete them by selecting the entry and hitting delete.

4b. You can edit some things about each tile entity. This can be quite useful in case they have things like redstone states.

4c. NBTExplorer has a search feature. It does work (and only searches the selected branch). Can be slow though.

4d. Deleting specific blocks is not possible.

5. DO NOT FORGET TO SAVE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment