# WorldEdit: the Minecraft map editor that runs inside the game

> EngineHub's GPL v3 project gives Minecraft selections, schematics, copy and paste, brushes and scripting, ships as a mod and a plugin for six platforms, and can be launched from its own source with a single Gradle command once Java 21 is present.

**EngineHub/WorldEdit** — 🗺️ Minecraft map editor and mod

- Repository: https://github.com/EngineHub/WorldEdit
- Website: https://enginehub.org/worldedit/
- Stars: 3,528 · Forks: 973
- Language: Java
- License: NOASSERTION
- Published: 2026-10-06 · Updated: 2026-10-06 · Language: en
- Canonical page: https://hysenlabs.com/projects/enginehub-worldedit

## Editing primitives rather than gameplay features

The README's pitch is a single line: a Minecraft map editor that runs in-game. The feature list that follows is what makes that more than a slogan. Selections and schematics give you a way to mark a region and move it around. Copy and paste and brushes cover both the interactive and the repeatable cases. Scripting sits on top of all of it, and is the part that separates WorldEdit from a building menu.

The intended contexts are listed without much hedging: creative mode, survival in single player, and your own server. The server case has its own justification attached, fixing griefing and mistakes. That framing matters for how people judge it. A survival player sees a powerful tool; a server owner sees a moderation and repair utility, which is why the project is equally at home on Bukkit, Spigot and Paper as on Fabric and NeoForge.

Java Edition is required, and the compatibility list is NeoForge, Fabric, Bukkit, Spigot, Paper and Sponge. Six platform targets from one codebase, which is the real engineering in this repository and the reason the source tree has as many platform modules as it does.

## Use Modrinth, not this repository, if you just want the mod

The README is direct about the distinction. This repository contains the Java code for WorldEdit, but if you only want to use it, get the mod or plugin from Modrinth at the versions page.

That is the single most useful sentence in the README for a new user, because the alternative is a source tree with a Gradle build, six platform modules and a dev environment, which is the wrong tool for the job of editing a build. There is no published release on this repository to grab instead, so Modrinth is the distribution channel of record.

The project has 3509 stars, 963 forks and 175 open issues, and its primary language is Java. The fork count is worth a second look in a project where most users consume a compiled artifact: it suggests a meaningful amount of people modifying and repackaging it, often for their own server configurations.

One small inconsistency to know about if you take the zip route. The README offers a link to download a .zip of the source from the `master` branch, while the repository's default branch is `version/7.4.x`. If you want the version the maintainers are actually working on, use the branch the project is developing rather than the one the convenience link points at.

## Four steps to a running game with WorldEdit

The contributor setup is unusually well specified, and the README claims you can get the game running from the source with no additional outside steps by doing four things.

First, get the source. The README recommends Git if you know it, and offers a .zip download otherwise, while noting that contributing changes means working out Git. Second, install Java greater than or equal to 21. The detail worth keeping is that if you do not install JDK 21 exactly, Gradle downloads it on the first run, but some form of Java must be installed for Gradle to start at all. Third, open a terminal and navigate to the source directory. Fourth, run one of three commands, which differ only in how the shell resolves the wrapper:

```bash
./gradlew :worldedit-fabric:runClient
```

The README is honest about the experience that follows. It takes a long time to actually transform WorldEdit into a mod, and if the command succeeds the Minecraft game opens and you can create a single player world with WorldEdit in it.

Two consequences follow for your workflow. Restarting is required after every change, so re-run the command for edits to take effect, and Java syntax errors make the command fail rather than silently doing nothing. `COMPILING.md` is linked for anything beyond this.

## Run the server instead of the client to shorten the loop

The README calls the restart cycle annoying and then gives the fix: run the server rather than the client, using `runServer` instead of `runClient`, and reconnect after restarting it.

That is a small piece of advice with a disproportionate effect on how much work you get done. Launching a client means launching a full game client every time, while a server starts faster, needs no window and no rendering, and can be left running while you inspect the result over a normal reconnect. For anyone doing real development on WorldEdit rather than a one-off change, this is the difference between a two minute loop and a twenty second one.

The same idea shows up in the IDE instructions, which cover the case where you want to run the game from IntelliJ IDEA Community Edition. Open the source folder in the IDE, then add a Gradle task under Run and Edit Configurations, choosing `worldedit-fabric` as the project and typing `runClient` as the task. Running the debug variant under the Debug menu gives you breakpoints in the mod while the game is live, which is how you would actually investigate a world editing operation that misbehaves on a particular platform.

Note the asymmetry between the two documents. The command line route gets a full four step walkthrough, while the IDE route gets two steps and a link onward. The IDE path is the one where you will end up reading the external documentation.

## What the source tree reveals about the platform support

The directory listing explains the compatibility list better than the prose does. There is `worldedit-core/` for the platform independent logic, `worldedit-core-mc/` for the Minecraft specific layer, `worldedit-libs/` for bundled dependencies, and `worldedit-mod/` for the standalone mod.

Alongside those are one module per platform target: `worldedit-bukkit/`, `worldedit-fabric/`, `worldedit-neoforge/` and `worldedit-sponge/`. And then there is `worldedit-cli/`, which is the interesting one. A command line module sitting next to the in-game modules means the operations WorldEdit exposes are not trapped inside a running Minecraft client, which is what makes the scripting support useful for batch jobs and for servers that would rather not have a player present.

The build infrastructure around it is modern Gradle with Kotlin DSL, in `build.gradle.kts` and `settings.gradle.kts`, plus a `build-logic/` directory for convention plugins and a `verification/` directory. A `gradle.properties` and a committed wrapper in `gradle/` are there, with `gradlew` and `gradlew.bat` for the two platforms.

Two smaller files are worth knowing about. `CHANGELOG.txt` at the root is a plain text changelog, and `crowdin-distributor.sh` indicates translations are managed through Crowdin, which is consistent with WorldEdit being translated into a large number of languages.

## Licensing, contributions and where the real documentation lives

WorldEdit is open source, licensed under GPL v3, and the README draws the consequence directly: your contributions will also be open source. The recommended route is to fork on GitHub, put your changes there, and open a pull request against the WorldEdit repository. `CONTRIBUTING.md` is flagged as holding important guidelines to follow, which on a project of this age usually means conventions that will save you a review cycle.

There is a `SECURITY.md` for disclosure, a `.git-blame-ignore-revs` file for keeping history clean after automated formatting, and `HEADER.txt` and `LICENSE.txt` at the root. YourKit is credited as a supporter, providing monitoring and profiling tools for Java and .NET.

Where documentation lives is the practical takeaway. The repository README covers running from source and nothing much else. End user documentation, meaning the commands, the selection syntax and the scripting API you would actually want while playing, is hosted separately at worldedit.enginehub.org. The project website is enginehub.org, with the WorldEdit page at enginehub.org/worldedit, and there is a Discord for support plus a public issue tracker.

That split is normal for a mod of this size and worth internalising before you start: the repository is a build manual, and everything you need to actually use WorldEdit is in the external docs.

## Conclusion

WorldEdit is unusual among Minecraft mods because it is not primarily a gameplay addition. Selections, schematics and brushes are world editing primitives, and the scripting layer plus the `worldedit-cli` module mean the same automation works outside the game as well as inside it. Two practical notes. As a user you want the build from Modrinth, because the repository is the source rather than the distribution, and the platform list in the README is NeoForge, Fabric, Bukkit, Spigot, Paper and Sponge, with Java Edition required. As a contributor you need Java 21 or newer, only the Gradle wrapper commands differ per platform, and `COMPILING.md` is where the detail beyond that lives. The default branch is `version/7.4.x` rather than master, the repository was pushed on 2026-09-23, and end user documentation is hosted separately at worldedit.enginehub.org.

## FAQ

### How do I get WorldEdit in Minecraft?

Download the mod or plugin from Modrinth rather than building from this repository, which holds the Java source. WorldEdit requires Java Edition and is compatible with NeoForge, Fabric, Bukkit, Spigot, Paper and Sponge.

### Is WorldEdit legal to use?

Yes. WorldEdit is open source and licensed under GPL v3, and the README describes it as usable in creative mode, in survival in single player, and on your own Minecraft server.

### Is Minecraft WorldEdit free?

Yes, as open source software. The distribution is on Modrinth and the code is on GitHub under GPL v3, with contributions also required to be open source.

### What is the WorldEdit command?

The README does not list individual commands. It describes the feature set as selections, schematics, copy and paste, brushes and scripting, and points to the separate end user documentation at worldedit.enginehub.org for command syntax.

## Sources

- [EngineHub/WorldEdit on GitHub](https://github.com/EngineHub/WorldEdit)
- [Issues](https://github.com/EngineHub/WorldEdit/issues)
- [Project website](https://enginehub.org/worldedit/)
- [README](https://github.com/EngineHub/WorldEdit/blob/version/7.4.x/README.md)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/enginehub-worldedit