EAGLERCRAFT
Getting WorldEdit
WorldEdit runs on the Java server, not inside the browser HTML. EngineHub’s permission docs say nobody can use it until a permission node is granted. worldedit.* is the broad node. Commands such as //wand, //pos1, //pos2 and //set each have their own checks.
Last reviewed: . By the Eaglercraft Guide editorial team.
For browser players, the documented route is an authorized server-side WorldEdit installation. A permission failure and an unknown command are different problems; neither is fixed by adding a random client script.
- Confirm the server installed the plugin. EaglerXServer does not bundle WorldEdit by existing.
- Ask for the specific node, not “op,” if the server splits permissions.
- 1.8 and 1.12 servers can run the plugin when the jar matches that server. 26.2 is not in the EaglerXServer support list, so a 26.2 WorldEdit claim is unverified.
- Client automation is not the same as an authorized WorldEdit server installation. Server rules govern automation; this guide neither predicts a ban nor recommends bypassing permissions.
Questions
Why does //wand say I cannot use that?
A permission-denied message points to the operator's permission setup. An unknown command can mean WorldEdit is absent, failed to load, is incompatible or is handled differently by the server. Ask the operator for logs and the specific permission node; the browser client alone cannot identify every cause.
Related: Make a server · Commands · Mods
Continue with the relevant guide
These links explain related topics, not a guarantee of compatibility with every build or server.
Sources
- EngineHub: WorldEdit permissions; match the actual server and plugin version. Reviewed 2026-10-27.
- EngineHub: WorldEdit installation and platform compatibility. Reviewed 2026-10-27.
- EaglerXServer README: Java 17, supported browser clients, installation and proxy listeners. Reviewed 2026-10-27.
Original illustrations on this page are drawn for eaglercraft.pro. They are not official screenshots.