With over half a year since the last big WorldEdit update, we're now releasing WorldEdit 7.1, with many new features and improvements.

A few of the main features include significant memory usage reductions, WorldEdit-CLI, running WorldEdit from the console and command blocks, watchdog ticking, translations, and more!

Performance Improvements

After the release of WorldEdit 7, we focused on different ways we could maximise the performance of the new WorldEdit architecture. This work paid off, significantly decreasing memory usage across almost all WorldEdit operations. We also sped up expression parsing, for commands such as //gen . On top of this, the Bukkit-section of the API now performs better when converting between Bukkit and WorldEdit types.

WorldEdit-CLI is a command-line application that allows you to use WorldEdit operations on schematics, and worlds in the future, without launching a Minecraft server. It is also usable as an API to create an application or service that uses WorldEdit. An example that we've made is WorldEdit Golf, a competition game site where you can compete to turn one schematic into another with as few commands as possible.

For more information on WorldEdit CLI, see this article.

WorldEdit from the Console and Command Blocks

Almost all of WorldEdit is now usable from the Console, and on Bukkit-based servers, Command Blocks. A new command, //world <worldname> , has been added, allowing for world selection.

Due to a bug in Minecraft itself in Command Blocks, we can only currently support them on Bukkit. Minecraft now strips all / characters away from the beginning of Command Block commands, preventing any double-slash command from working. As Bukkit supports namespaced commands, /worldedit:/set can be used instead, which works around the Minecraft bug.

When using Command Blocks, if you want them to all use the same WorldEdit session (same selection, same history, etc.), make sure to give them all the same name using an Anvil.

Watchdog Ticking

Every so often, someone comes and tells us that WorldEdit is crashing their server. We then need to explain to them that it's not WorldEdit causing a crash, but the server's watchdog implementation. The one in Spigot is notorious for this, as it often triggers earlier than it should.

The solution before now has been to disable the watchdog in the Spigot config file. However, this is not ideal and can be potentially dangerous as it prevents real server hangs from being detected.

As of WorldEdit 7.1, there is now a //watchdog command. This command tells WorldEdit to talk to the server's watchdog, ensuring that it doesn't incorrectly trigger when WorldEdit is applying modifications to the world.

Translations and Localisation

WorldEdit has a massive community of users whose primary language is not English. Until now, they've had to rely on unsupported third-party modifications or stick with English. Now, WorldEdit natively supports every language that Minecraft supports.

As the WorldEdit team cannot possibly know over one hundred languages, this is very much a community effort. We have a CrowdIn page, linked here where we massively appreciate contributions. Translations will also of course not be perfect from the start. As of writing, only a few languages have complete translations, one of which being LOLCAT.

If you want to override any messages or download new translations, you can create a new folder within the WorldEdit directory named lang . The default translations file is called strings.json , and per-language files are called language-Code/strings.json . For example, an Australian English file is en-AU/strings.json .

And More!

Aside from these more substantial changes, many small improvements have happened across the board. If you'd like to read the full changelog, it's available here.