For the complete documentation index, see llms.txt. This page is also available as Markdown.

The World Editor

Change any single world's settings from one menu.

/worlds edit [world] opens the editor for a single world. With no argument it edits the world you are standing in.

This is where nearly every per-world setting lives. Each control has its own permission, so you can hand out a subset: a builder who may change the status but not the visibility, for example.

  • Permission: buildsystem.edit, which supports the .self and .other suffixes so you can allow editing your own worlds only.


Controls

Identity

Control
Permission
What it does

World item (top row)

buildsystem.edit.icon

Opens the item picker to choose the world's icon. Right-click a player-head icon to set its skull texture instead.

Pin

buildsystem.edit.pin

Keeps the world at the top of every navigator list, above the normal sort order.

Status

buildsystem.edit.status

Opens the status picker. Status decides which navigator tabs list the world, and whether building is allowed at all. See Custom Statuses & Categories.

Project

buildsystem.edit.project

Prompts in chat for a free-text project tag, shown in the world's lore and /worlds info.

Permission

buildsystem.edit.permission

Prompts for the permission a player needs to enter. Enter - to remove the restriction. Restricted by settings.world-permission-whitelist if you have set one.

Visibility

buildsystem.edit.visibility

Switches between public (EVERYONE) and private (ADDED_PLAYERS). A barrier icon means you lack permission to create that kind of world, and clicking does nothing.

Builders

buildsystem.edit.builders

Left-click toggles the builder whitelist on or off. Right-click opens the builder list. While enabled, only the creator and added builders may modify the world.

Protection

Each of these is an independent switch. Turning one off blocks that action for everyone without a bypass.

Control
Permission
Blocks

Block breaking

buildsystem.edit.breaking

Breaking blocks.

Block placement

buildsystem.edit.placement

Placing blocks.

Block interactions

buildsystem.edit.interactions

Right-clicking chests, doors, buttons, and everything else interactable.

buildsystem.bypass.settings overrides all three at once.

World Behaviour

Control
Permission
What it does

Physics

buildsystem.edit.physics

Left-click toggles physics for the world. Right-click opens the exceptions menu, covered below.

Explosions

buildsystem.edit.explosions

Whether TNT and creepers damage terrain.

Mob AI

buildsystem.edit.mobai

Whether mobs move and act. Off leaves them frozen in place, which is useful for posed builds.

Time

buildsystem.edit.time

Cycles the world's time between sunrise, noon, and night, using the values from world.defaults.time.

Difficulty

buildsystem.edit.difficulty

Cycles Peaceful, Easy, Normal, Hard.

Game rules

buildsystem.edit.gamerules

Opens a paginated list of every game rule. Booleans toggle, numeric rules increase by 1 on right-click and 10 on shift-right-click.

Remove entities

buildsystem.edit.entities

Deletes every entity in the world and reports the count. Players, and a small set of protected entity types, are left alone.


Physics Exceptions

Physics used to be all or nothing. Right-clicking the physics toggle opens a menu where individual behaviours keep working while the world's physics stay off.

Category
Covers

Block updates

Attached blocks such as torches and rails popping off, and block shape updates.

Connections

Fences, gates, glass panes, stairs, and walls joining to their neighbours.

Falling blocks

Sand and gravel obeying gravity.

Fluid flow

Water and lava spreading.

Leaf decay

Leaves disappearing without a nearby log.

Growth

Crops and saplings growing.

Spreading

Grass, vines, and fire spreading to other blocks.

Block forming

Snow and ice forming.

Block fading

Ice and snow melting, coral dying, fire burning out.

The common case is enabling Connections on a build world: fences and walls still join up as you place them, but nothing else moves.

Values are stored per world. New worlds inherit the defaults from world.defaults.physics-exceptions in config.yml, as does any existing world that has no stored value yet.

  • Permission: buildsystem.edit.physics, the same node as the toggle itself.


Who Can Edit What

Three layers decide whether a click goes through:

  1. buildsystem.edit to open the editor at all, with .self and .other if you want to distinguish own worlds from other people's.

  2. The control's own node, such as buildsystem.edit.difficulty. Deny it and that one control stops responding while the rest keep working.

  3. The world's own rules. A status with building disabled, or an enabled builder whitelist you are not on, blocks edits regardless of permissions. buildsystem.bypass.archive and buildsystem.bypass.builders override those.

A control you lack permission for still renders. Clicking it is refused rather than hidden, so builders can see a setting exists and ask for it rather than wondering why the menu looks different from a screenshot.

Last updated