Skip to main content
infoMod ErrorsAffects: Java Edition

How to Fix WorldEdit Errors

WorldEdit stops an edit with Max blocks changed in an operation reached when a change limit is set. How //limit and the config limits work.

Quick Fix

Run //limit with a higher number, for example //limit 500000. Going above the server's maximum needs the worldedit.limit.unrestricted permission.

Error Message

Max blocks changed in an operation reached (10000).

How to Fix

1

Run //limit with the number of blocks you need. //limit on its own goes back to the default.

2

Admins on Paper, Spigot or Bukkit: raise limits.max-blocks-changed.default and limits.max-blocks-changed.maximum in WorldEdit's config.yml.

3

Admins on Fabric or NeoForge: change default-max-changed-blocks and max-changed-blocks in config/worldedit/worldedit.properties.

4

Give trusted builders the worldedit.limit.unrestricted permission so a server maximum doesn't hold them back.

5

On FastAsyncWorldEdit, raise max-changes in the default limits group of its config.yml, or give players a larger group through the fawe.limit.<name> permission.

6

Split very large edits into smaller selections, and clear your history with //clearhistory after big jobs.

Common Causes

  • Your change limit is lower than the edit. WorldEdit then stops with Max blocks changed in an operation reached, followed by the limit.
  • The server sets a default limit. WorldEdit itself ships without one (-1 means no limit), so the number comes from the server's config or from an earlier //limit.
  • You asked for more than the server allows. //limit then answers Your maximum allowable limit is, followed by that maximum.
  • The server runs FastAsyncWorldEdit, which has its own limits. Its default group allows 50,000,000 block changes and cancels bigger edits with Too many blocks changed.
  • The edit is so large that the server runs low on memory. WorldEdit keeps what each edit changed so //undo can reverse it, up to 15 edits per player by default.

Diagnostic Steps

  1. Read the number in the error message.
  2. Run //limit with a higher number.
  3. Ask an admin if you reach the server maximum.
  4. Split the edit if the server runs low on memory.

FAQ

Is FAWE better than WorldEdit?

FastAsyncWorldEdit is a separate fork made for very large edits on Paper and Spigot. It has its own settings and limits, so advice for WorldEdit doesn't always apply to it.

What does //limit -1 do?

It removes the change limit for your WorldEdit session. //limit with no number goes back to the server's default.

Why does WorldEdit use so much memory?

It stores what every edit changed so //undo can reverse it, and keeps up to 15 edits per player by default. //clearhistory throws that history away.

Related Errors

Need More Help?