☰

World Border Bug

The world border is in an invalid state, producing errors or strange behavior at the edge of the world. A bad border size or center value, often from a command or plugin, is behind it.

What does this error mean?
The world border has a center and a size. 'Invalid world border' means one of those values is out of range or malformed, which can break movement near the edge or throw errors when the border is processed. 
Invalid world border
Most Common Causes
  • A border size set to an invalid or extreme value.
  • A plugin or command setting a malformed border.
  • Corrupted border data in level.dat.
  • Conflicting border changes from multiple plugins.
  • A datapack altering the border incorrectly.
How To Diagnose
  1. Check the current border with '/worldborder get'.
  2. Note any plugin or datapack that manages the border.
  3. Review recent border commands.
  4. Inspect level.dat border data if needed.
Recommended Fixes
  • Reset the border
    Use '/worldborder set <size>' and '/worldborder center <x> <z>' to restore sane values.
  • Audit border plugins
    Find the plugin/datapack setting a bad value and correct its config.
  • Repair level.dat data
    If border data is corrupt, restore level.dat from a backup.
  • Avoid conflicting controllers
    Ensure only one system manages the world border.
Analyze My Log
Frequently Asked Questions

Run '/worldborder get' for its size, plus check the center with the worldborder commands.

Any reasonable positive number within the world's limits, avoid extreme or zero values.

Yes, two border managers can produce invalid states, keep just one in control.