World Access

Lock a world down, and choose who may still get in.

Configure entry restrictions, builder list requirements, and builder overrides to control player actions in specific worlds.

---

1. Entry Permissions

Every world can be assigned a required permission node that players must hold to teleport into or enter the world:

• Assigning a Permission: In the World Editor GUI or via /worlds setPermission <world> <permission_node>.

• Disabling Entry Lock: Set the permission to - to allow unrestricted entry.

• Default Setup: Configured in config.yml under world.defaults.permission (defaults to - for public worlds and worlds.%world% for private worlds).

• Bypass Permission: A player can bypass entry locks if they have:

  • buildsystem.bypass.permission.public (for public worlds)

  • buildsystem.bypass.permission.private (for private worlds)

  • buildsystem.bypass.permission.archive (for archived worlds)

  • buildsystem.admin (all-access override)

World Editor GUI

---

2. Modification & Builder Rules

To restrict blocks from being broken, placed, or interacted with:

The Builder Whitelist (builders-enabled)

If builders-enabled is toggled to true (default: true for private worlds, false for public worlds):

• Owner/Creator: The world's registered creator is automatically allowed to build.

• Whitelisted Builders: Only players added via /worlds addBuilder <player> can modify blocks.

• Restricting Non-Builders: Non-builders are blocked from:

  • Placing or breaking blocks.

  • Interacting with containers (if settings.builder.block-worldedit-non-builder is enabled in config.yml, this includes WorldEdit and brush commands).

Modification Override

A player who is not a builder can modify the world if they hold:

• buildsystem.bypass.builders

• buildsystem.admin

• Or have toggled on Build Mode (/build) if they have permission to do so.