Skip to content

WorldBorder Staff Reference

Public-safe technical notes for staff who configure or support WorldBorder on 1MoreBlock.

Verify destructive, economy-changing, permission-changing, and player-data commands against the installed build and an approved support case before running them.

CommandPermissionPurpose
/wb listworldborder.listLists configured world borders.
/wb getmsgworldborder.getmsgShows border message configuration in supported builds.
/wb <world> set <radius>worldborder.setChanges a world border; coordinate maps and backups.
/wb <world> fillworldborder.fillGenerates chunks inside the border; resource intensive.
/wb <world> trimworldborder.trimDeletes chunks outside the border; destructive.
PermissionPurposeSuggested access
worldborder.listReads border state.Support staff
worldborder.setChanges boundaries.Server administrators
worldborder.fillChunk generation.Server administrators
worldborder.trimDestructive chunk trimming.Server owner/approved maintenance only

No plugin-owned placeholders were verified. PlaceholderAPI may still expose values through a separate expansion or an integrating plugin.

  • BlueBridgeWB can expose border data to BlueMap.
  • Multiverse owns world loading; maps, portals, homes, claims, and warps must be reviewed when a border moves.
  • Fill/trim operations need disk, CPU, backup, and maintenance planning.
/wb list
/wb getmsg
/wb <world> set <radius>
  • Confirm world, center, radius, shape, and whether vanilla or plugin border triggered.
  • Check homes/warps/portals and BlueMap bounds after border changes.
  • Never run trim without a verified backup and dry planning.