Your WorldEdit commands are failing. You copied the mod file into the right folder, typed the slash command exactly as shown, and still nothing happens. The selection wand won’t appear, the blocks won’t budge, and the server console spits out an error. The problem usually isn’t the installation – it’s the edition.

Minecraft Java Edition and Minecraft Bedrock Edition use completely different WorldEdit projects. The Java version, maintained by EngineHub, runs as a mod or plugin and expects commands to start with two forward slashes. The Bedrock version is a separate community add-on that requires semicolons instead. Mistaking one for the other is the single most common reason WorldEdit “breaks” on the first try.

This guide cuts through the noise. You’ll learn exactly which WorldEdit you need, how to install it for your platform, and the core commands that turn hours of manual building into a few precise keypresses.

The Two-WorldEdit Problem

WorldEdit’s core job is the same everywhere: select a region, then fill, replace, copy, or erase thousands of blocks instantly. But the way you access that power depends entirely on your Minecraft edition.

The Java Edition WorldEdit comes from EngineHub, a long-standing open-source project. It’s available for Fabric, Forge, NeoForge, Quilt, Paper, Spigot, Bukkit, Sponge, and Folia. You install it as a .jar file in the server’s plugins folder or the client’s mods folder. Commands almost always start with //.

Bedrock Edition cannot run Java mods. Instead, it uses a separate add-on – often called “WorldEdit for Bedrock” – distributed as a behavior pack and resource pack. You import it through Minecraft’s add-on system, enable experimental features in the world settings, and grant yourself permission with a /tag command. Editing commands begin with ;.

That semicolon is the giveaway. If //wand doesn’t work but ;wand does, you’re on Bedrock. If it’s the opposite, you’re on Java. No amount of folder renaming or re-downloading will change that.

Java Edition: The Power User’s Toolkit

Java players get the most mature version of WorldEdit. The setup varies by loader and server type, but the editing mechanics are identical once you’re in.

Installation Quick Reference

Platform Install Location Key Detail
Single-player (Fabric) .minecraft/mods/ Place Fabric WorldEdit .jar here after installing Fabric loader.
Single-player (Forge/NeoForge) .minecraft/mods/ Use the build tagged for your loader. A Fabric build won’t work.
Paper/Spigot/Bukkit server server-folder/plugins/ Stop the server, drop the WorldEdit .jar into plugins, restart.
Sponge server Refer to Sponge docs Sponge uses a separate WorldEdit version from Ore.

After installation, always check the startup log. A missing dependency or wrong Minecraft version will show up there before you ever type a command.

Getting Command Access

In single-player, open your world with Cheats enabled. If cheats are off, commands are blocked even with WorldEdit installed. On a server, an operator must run:

/op YourUsername

For servers with permission plugins, avoid giving worldedit.* to every builder. Narrow permission nodes like worldedit.selection.* or worldedit.clipboard.* are safer for team members who only need basic editing.

The Commands You’ll Use Every Day

All Java WorldEdit edits start with a selection. Get the wooden axe wand:

//wand

Left-click one corner of your build area, right-click the opposite corner. Then:

  • //size – Check your selection’s dimensions before doing anything destructive.
  • //set stone – Fill the region with stone. Use patterns like //set stone,andesite,cobblestone for variety.
  • //replace sandstone dirt – Swap one block type for another.
  • //stack 4 – Duplicate the selection four times in the direction you’re facing.
  • //copy, then //paste – Move structures. Stand at the reference point before copying.
  • //undo – The lifeline. //undo 7 rolls back seven steps.

Configuration files let you set maximum brush sizes and block-change limits. Cap them early – an accidental //set on a 10,000-block region can freeze a server.

Bedrock Edition: A Separate Beast

WorldEdit Bedrock is an add-on, not a mod. It leans on Bedrock’s experimental API and works on Windows 10/11, mobile, and console Bedrock – but not on Java Edition or Realms that disable experimental features.

Setup from Scratch

  1. Download the Bedrock WorldEdit add-on from its official project source. Double-click the .mcpack or .mcaddon file to import it into Minecraft.
  2. Open your world settings, activate WorldEdit Behavior Pack and WorldEdit Resource Pack.
  3. Under Experimental Features, enable Beta APIs (or the setting required by the add-on version).
  4. Enter the world and give yourself permission:
/tag @s add worldedit

For other players:

/tag "Player Name" add worldedit

Commands with a Twist

Bedrock commands replace the double slash with a semicolon:

  • ;wand – Get the selection tool.
  • ;set stone – Fill.
  • ;replace sandstone dirt – Swap.
  • ;copy, ;cut, ;paste – Clipboard.
  • ;undo – Roll back.

Touchscreen users can run ;kit to access item-based shortcuts: a Pattern Picker to select blocks, a Fill Selection item, and an undo button. This keeps building fast without typing on a glass keyboard.

Selections, Shapes, and Safer Editing

Whether you’re on Java or Bedrock, the editing workflow follows the same logic: select, check, act, undo if wrong.

Beyond Cuboids

Cuboid selections are the default, but WorldEdit supports spheres, cylinders, convex shapes, and more. Use //sel <type> on Java or the equivalent Bedrock command to switch. For circular towers, switch to a cylinder. For domes, switch to a sphere.

Check Your Size

Before any command that alters blocks, run //size (Java) or ;size (Bedrock). It reports the selection’s dimensions and total block count. A 100×100×100 cube is a million blocks – enough to lag a server if you’re not careful.

Patterns and Masks

Don’t just fill with solid stone. Mix blocks with comma-separated lists to add variation. On Java, apply a mask to limit where a brush or fill works – for example, replace only dirt without touching stone.

Clipboard, Schematics, and Team Builds

The clipboard isn’t just copy-paste. You can rotate and flip structures before pasting, save blueprints as schematics, and share them across worlds or with teammates.

  • Java: //copy, then //rotate 90, //flip north, and //paste. Save with /schematic save -f my_build.
  • Bedrock: ;copy, ;rotate 90, ;paste. Schematics work similarly but through the add-on’s interface.

Clear the clipboard when done (/clearclipboard on Java) to avoid accidentally pasting an old build.

Brushes and Terrain

Hold a tool, bind a brush, and right-click to sculpt landscapes instantly.

/brush sphere stone 5

On Bedrock, the syntax is similar but starts with ;. Brushes are perfect for hills, cliffs, and organic shapes. Use masks so you don’t accidentally paint over buildings.

When the Commands Still Don’t Work

Even after matching the edition, problems creep in. Here’s your troubleshooting list:

  • Command prefix: Double-check you’re using // on Java, ; on Bedrock.
  • Permissions: On Java, are cheats on? Are you opped? On Bedrock, did the tag apply correctly? Re-run /tag @s add worldedit.
  • Version mismatch: The WorldEdit download must match your exact Minecraft version. A 1.20 mod won’t load on 1.21.
  • Experimental features (Bedrock): If Beta APIs aren’t toggled on, the add-on sits idle. Toggle them, then reload the world.
  • Server overload: Huge brush radii or large //set commands can freeze a server temporarily. Reduce sizes and test incrementally.

Always back up your world before experimenting. WorldEdit’s undo history is powerful, but it doesn’t survive a server restart or a misplaced //cut.

Moving Forward: What’s Next for WorldEdit

WorldEdit for Java Edition continues to evolve alongside Minecraft updates, with EngineHub actively maintaining builds for new loaders like NeoForge. Bedrock’s add-on, while functional, depends on Microsoft’s experimental API – meaning updates can occasionally break functionality until the add-on is patched.

For builders who work across both editions, the key takeaway is simple: treat them as two entirely separate tools with different syntaxes. Once you internalize that, WorldEdit becomes the fastest path from a blank landscape to a finished masterpiece.