> For the complete documentation index, see [llms.txt](https://buildsystem.eintosti.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://buildsystem.eintosti.de/permissions-and-access/restricting-worlds.md).

# 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]`, which asks for the node in chat.
* **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).
* **Folders**: If the world is in a folder and `folder.override-permissions` is `true` (the default), the folder's permission applies instead of the world's own. See [Organizing Folders](https://buildsystem.eintosti.de/managing-worlds/creating-a-folder.md).
* **Always Allowed**: The world's creator and its builders can always enter.
* **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 worlds whose status has building turned off, such as archive; this replaces the public/private node for those worlds)
  * `buildsystem.admin` (all-access override)

![World Editor GUI](https://2366875379-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZtdJcIoBgnlLEZoCMTDD%2Fuploads%2Fgit-blob-ca4be427d9f4ab79472087995815fe7852f0d933%2Fworlds_editor_gui.png?alt=media)

***

## 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, breaking or interacting with blocks.
  * Using WorldEdit commands, while `settings.builder.block-worldedit-non-builder` is `true` in `config.yml` (the default). Build Mode and `buildsystem.admin` always pass. Otherwise `buildsystem.bypass.builders` lets a non-builder through, and a world whose status turns building off needs `buildsystem.bypass.archive`.

### Modification Override

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

* `buildsystem.bypass.builders`
* `buildsystem.bypass.settings`, which covers breaking, placing and interacting with blocks
* `buildsystem.admin`
* Or have toggled on Build Mode (`/build`) if they have permission to do so.

### Order of checks

Placing, breaking and interacting with blocks, and the player settings that act on blocks (instant signs, place plants, slab breaking, open trapdoors and disable interactions), are checked in this order:

1. Build Mode and `buildsystem.admin` always pass.
2. In a world whose status turns building off, such as archive, everyone else needs `buildsystem.bypass.archive`.
3. `buildsystem.bypass.settings` then skips the world's block breaking, placement and interaction toggles and the builder list.
4. Otherwise the world's toggle for the action must be on, and the builder list applies.
