MCA Selector: deleting and exporting Minecraft chunks outside the game

The problem MCA Selector solves for Minecraft Java world owners

A Minecraft Java world is stored as region files, and each region file holds a grid of chunks. The game has no built-in way to remove an individual chunk. If you want terrain regenerated in one area, or you want to carve a section out of a world and hand it to someone else, you either edit the region files yourself or you load the world and try to work around the problem in-game. MCA Selector takes the first route. It reads the region files, draws the chunk grid, and lets you mark chunks for deletion or export. The README describes it as "an external tool to export or delete selected chunks and regions from a world save of Minecraft Java Edition." The audience is narrow and specific: server administrators cleaning up explored terrain, map makers extracting a region, and players who want a fresh start in part of a world without losing the rest. It is not a world editor in the general sense, and it does not generate terrain. It removes or copies what is already there.

How MCA Selector reads and writes region files

The tool operates on the save folder rather than on a running game. You point it at a world, and it renders the region grid, which is the chunk and region grid shown in the README screenshot. Selection happens on that grid. Deletion removes the selected chunks from the region files. Export writes the selected chunks into a new world save. Both operations work at the file level, which is why the README warns in bold that MCA Selector modifies and deletes chunks and that you should back up your world first. That warning is not boilerplate. There is no undo documented in the README, and the wiki is where operational detail lives; the README itself links to it rather than reproducing it. The supported versions table is the other half of the mechanism: each Minecraft version range maps to a data version range, from 1.2.1 through 1.12.2 with data versions None to 1343, up to 26.1 through 26.3+ with data versions 4764 to 5023+. The tool has to understand the chunk format for the version it opens, which is why that table exists and why snapshot worlds are explicitly not guaranteed to work.

Downloading MCA Selector for Windows, macOS and Linux

There is no package manager step and no build step for normal use. The README points to the official GitHub repository as the only official and safe download location, and the release page for 2.9 offers a Windows installer, two macOS disk images (arm64 and x64), DEB and RPM packages for arm64 and x64, and a universal jar. Pick the artifact for your platform, or download the jar if you want to run it anywhere a Java runtime is available.

On Linux, the DEB and RPM packages are the direct route. The README lists both architectures, so an arm64 machine gets mcaselector-2.9-aarch64.deb or mcaselector-2.9-aarch64.rpm, and an x64 machine gets the x64 equivalents.

On macOS, mount the disk image matching your machine. Apple silicon users take the aarch64 image; Intel users take the x64 image. The README gives both downloads separately rather than shipping a universal macOS build, so picking the wrong one is the first thing to get right.

For a first real use, the sequence the README implies is: back up the world folder, open the world in MCA Selector, select chunks on the grid, then either delete them or export them. The README does not document the exact menu path for those two actions, so check the wiki or one of the linked video tutorials before your first delete. What you should see after opening a world is the chunk and region grid rendered for that save, matching the screenshot in the README.

Where MCA Selector is the wrong tool

Two limits stand out. First, it is Java Edition only. The README title says so directly: "a world save of Minecraft Java Edition." Bedrock worlds use a different storage format, and nothing in the README suggests MCA Selector touches them. If your world came from a phone, a console, or the Bedrock edition on Windows, this is not the tool. Second, snapshot support is qualified. The supported versions table lists a range up to 26.3+, but the README adds that there is no guarantee worlds generated in a snapshot version will work even when the table covers that version, and that old snapshots of past releases are not officially supported. So a world created in a current snapshot sits in an uncertain zone. The third limitation is the one the README states in bold: the tool modifies and deletes chunks, and there is no documented rollback. Treat every delete as irreversible and treat the backup as part of the procedure, not as an optional precaution.

MCA Selector compared with Amulet Editor

Amulet Editor is the obvious alternative, and the difference is in what each tool is for. MCA Selector works on chunk and region granularity: you select whole chunks on a grid and delete or export them. It does not give you block-level editing, and it does not try to. Amulet is a general world editor, so it operates at the block level and can change what is inside a chunk rather than only whether the chunk exists. If your goal is to remove explored terrain so it regenerates, or to lift a region out of one save and into another, MCA Selector's chunk grid is the shorter path. If your goal is to edit the contents of a build, replace blocks, or move structures, chunk-level selection is the wrong granularity and Amulet is the better fit. The two are not competing for the same task, which is why the choice should follow from what you actually need to change.

Maintenance, licence and what the MIT terms mean here

The repository is not archived, and the last push was on 2026-09-22, one day before this writing. Releases are regular: 2.7 on 2026-03-24, 2.8 on 2026-06-15, and 2.9 on 2026-09-15. That cadence tracks Minecraft's own release schedule, which the supported versions table makes explicit by mapping each Minecraft range to a data version range. The practical upgrade cost is low because there is no dependency to install and no server component. You download the new artifact and open your world with it. The cost that matters is not the upgrade, it is the version match: a world from a Minecraft version outside the table, or from an unsupported snapshot, is the case where you should not proceed. The project is MIT licensed, which is permissive and places few obligations on anyone redistributing or modifying it. That is a statement about the licence text, not legal advice; if you plan to bundle the tool or ship a modified build, read the LICENSE file in the repository and get proper advice for your situation.

Editorial conclusion

Adopt MCA Selector if you run a Java Edition world or server and need to delete or export specific chunks, and you are willing to back up the save first. Do not adopt it for Bedrock worlds, and do not expect it to load a world the game itself has not generated. Before your first delete, verify the Minecraft version against the supported versions table, confirm your save is a Java Edition world, and copy the world folder somewhere the tool cannot reach.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Querz/mcaselector on GitHub
4. README
5. Releases