If your problem lives inside Minecraft’s NBT data — the tags that describe chunks, players and world settings — two free tools show up repeatedly: NBTExplorer and MCA Selector. They approach the data from opposite directions. NBTExplorer is a tree editor for individual files: level.dat, player data, region files, schematics. MCA Selector starts from a map of the world and changes chunk data in batch across a selection. For a lot of real repair jobs, the honest answer is that they complement each other.
The short answer
- Choose NBTExplorer to open one file and edit its raw tags by hand: a player’s inventory or location in their .dat file, game rules and settings in level.dat, or the tag tree inside a single region file or schematic.
- Choose MCA Selector to change the same field across hundreds or thousands of chunks at once with the NBT Changer, to find chunks by filter (biome, block palette, entities, DataVersion…), or to delete/export whole chunks and regions.
- Overlap exists and is worth knowing: MCA Selector’s Chunk Editor edits one chunk’s full NBT tree, so for a single chunk either tool can do the job. NBTExplorer goes beyond chunks to standalone files MCA Selector does not touch.
Side-by-side
| MCA Selector | NBTExplorer | |
|---|---|---|
| Starting point | A top-down map of the world; you select chunks/regions first | A file browser; you open one file and expand its tag tree |
| Edits | NBT Changer batch operations across a selection; Chunk Editor for one chunk’s tree | Manual tag-by-tag editing of the file you opened |
| Files covered | Chunk data in Java world saves (region, poi, entities) | level.dat, player data, .mca/.mcr region files, schematics and other NBT files |
| Map/visual selection | Yes — that is the core of the tool | No map view, no chunk selection |
| Bulk delete/export of chunks | Yes | No |
| Price | Free | Free |
| Licence | MIT | MIT |
| Platforms | Windows, macOS, Linux | Windows, macOS, Linux |
Where NBTExplorer wins
- Player data. A stuck player, a corrupted inventory, a location that needs resetting — that data lives in per-player .dat files, outside the chunk system MCA Selector works on. NBTExplorer opens those files directly.
- level.dat and world-level settings. The world’s root settings file is a single NBT document; a tree editor is the natural tool for it.
- Archaeology in a single file. When you need to see exactly what tags a region file or schematic contains — every value, in order — the tree view shows you the raw structure with nothing abstracted away.
- Small, precise, one-off fixes where setting up a selection and a batch operation would be more machinery than the fix deserves.
Where MCA Selector wins
- Scale. “Set this biome on every chunk in the badlands project”, “delete entities from all chunks matching this filter”, “replace one block type with another across the region” — the NBT Changer applies a field change to an entire selection in one operation, in Change mode (only where the field exists) or Force mode (write it everywhere).
- Finding the chunks first. The chunk filter locates chunks by DataVersion, InhabitedTime, biome, block palette, entities, structures and more — the map shows you what matched before anything is written.
- Structural operations. Deleting, exporting, importing and defragmenting chunks and regions are file-level operations NBTExplorer does not attempt.
- A maintained, current release line. MCA Selector tracks new Minecraft versions (the current 2.9 covers worlds up to Minecraft 26.3); NBTExplorer’s development moves slowly by comparison.
Using them together
A typical repair session uses both. MCA Selector does the finding and the heavy lifting: filter for the chunks that match the problem, apply the batch fix with the NBT Changer, or export the affected chunks for inspection. Then, if one specific file still needs hand work — a player’s data, a value inside level.dat, a single tag the batch operation deliberately did not cover — that file goes into NBTExplorer for surgery. The rule of thumb: world-scale questions start on the map; file-scale questions start in the tree.
Whichever tool you pick, back up first: world editors change your save files directly. Close Minecraft (and stop your server, if the world is on one), copy the whole world folder somewhere safe, and only then start editing. This applies twice over here, because both tools write raw data files.
Pick by task
| Your task | Pick |
|---|---|
| Fix a player’s inventory, location or data file | NBTExplorer |
| Edit level.dat or world-level settings | NBTExplorer |
| Inspect the raw tags inside one file | NBTExplorer |
| Change a field across thousands of chunks | MCA Selector |
| Find chunks by biome, blocks, entities or version | MCA Selector |
| Delete, export or import chunks/regions | MCA Selector |
| Edit one chunk’s full NBT tree | Either — MCA Selector’s Chunk Editor or NBTExplorer |
Download MCA Selector 2.9
If MCA Selector is the tool that fits your job, get the current release from the MCA Selector download page — the Windows installer, the cross-platform .jar, the macOS .dmg and the Linux .deb/.rpm, every button pointing at the official GitHub release files with the SHA-256 checksum listed, plus a clearly labelled site mirror as a fallback. It is free and open source under the MIT licence.
One last backup reminder: keep the copy of your world you made before editing until you have loaded the edited world in Minecraft and confirmed it looks right. Deletions and NBT changes in MCA Selector are permanent once applied.
Related guides
Go deeper on the NBT side of MCA Selector, or read the other comparisons: