> 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/v4/command-reference/worlds.md).

# /worlds

The `/worlds` command (aliases: `/w`) manages world navigation, folders, properties, and whitelists.

***

## Navigation & Editor UI

### `/worlds`

* **Syntax**: `/worlds` (or `/w`)
* **Permission**: `buildsystem.navigator`
* **Description**: Opens the World Navigator main dashboard.

### `/worlds public`

* **Syntax**: `/worlds public`
* **Permission**: `buildsystem.navigator`
* **Description**: Opens the public worlds navigator list directly.

### `/worlds private`

* **Syntax**: `/worlds private`
* **Permission**: `buildsystem.navigator`
* **Description**: Opens the private worlds navigator list directly.

### `/worlds archive`

* **Syntax**: `/worlds archive`
* **Permission**: `buildsystem.navigator`
* **Description**: Opens the archived worlds navigator list directly.

### `/worlds edit [world]`

* **Syntax**: `/worlds edit [world]`
* **Permission**: `buildsystem.edit` (supports `.self` / `.other` suffixes)
* **Description**: Opens the interactive World Editor GUI to adjust settings like physics, difficulty, weather, time, and builders. Defaults to the player's current world if no argument is provided.

### `/worlds tp <world>`

* **Syntax**: `/worlds tp <world>`
* **Permission**: `buildsystem.tp`
* **Description**: Teleports the sender directly to the target world's spawn location.

***

## Directory Management

### `/worlds import <world> [-c creator]`

* **Syntax**: `/worlds import <world> [-c creator]`
* **Permission**: `buildsystem.import`
* **Description**: Imports a folder present under the server's root as an active build world. The optional `-c` flag registers a player UUID as the world's creator.

### `/worlds importAll`

* **Syntax**: `/worlds importAll`
* **Permission**: `buildsystem.importall`
* **Description**: Batch-imports all unregistered world folders in the server directory. Execution is throttled via config delay to prevent lag spikes.

### `/worlds unimport <world>`

* **Syntax**: `/worlds unimport <world>`
* **Permission**: `buildsystem.unimport`
* **Description**: Unloads the world from memory and deletes its BuildSystem registry entries without deleting the directory on disk.

### `/worlds delete <world>`

* **Syntax**: `/worlds delete <world>`
* **Permission**: `buildsystem.delete`
* **Description**: Unloads the world and permanently deletes its directory from the server disk.

### `/worlds saveTemplate <world> [templateName]` (New in 4.0.0)

* **Syntax**: `/worlds saveTemplate <world> [templateName]`
* **Permission**: `buildsystem.savetemplate`
* **Description**: Saves a copy of the target world directory into `plugins/BuildSystem/templates/` to make it selectable during new world creation.

***

## Property & Access Mutation

### `/worlds setCreator <world> <creator>`

* **Syntax**: `/worlds setCreator <world> <creator>`
* **Permission**: `buildsystem.setcreator`
* **Description**: Sets the registered owner/creator of the world.

### `/worlds setProject <world> <projectName>`

* **Syntax**: `/worlds setProject <world> <projectName>`
* **Permission**: `buildsystem.setproject` (supports `.self` / `.other` suffixes)
* **Description**: Sets the project tag metadata for the world.

### `/worlds setPermission <world> <permission>`

* **Syntax**: `/worlds setPermission <world> <permission>`
* **Permission**: `buildsystem.setpermission` (supports `.self` / `.other` suffixes)
* **Description**: Sets the permission node required for players to join the world. Use `-` to clear permission locks. Checks against `world-permission-whitelist` if configured.

### `/worlds setStatus <world> <status>`

* **Syntax**: `/worlds setStatus <world> <status>`
* **Permission**: `buildsystem.setstatus` (supports `.self` / `.other` suffixes, and requires the dynamic permission node `buildsystem.setstatus.<statusId>` with underscores removed, e.g. `buildsystem.setstatus.inprogress` for `in_progress`)
* **Description**: Sets the progress state of the world (e.g., `not_started`, `in_progress`, `almost_finished`, `finished`, `archive`, `hidden` or any custom status).

***

## Spawn Management

### `/worlds setSpawn`

* **Syntax**: `/worlds setSpawn`
* **Permission**: `buildsystem.setspawn`
* **Description**: Sets the exact location of the target world's spawn point to the sender's current position.

### `/worlds removeSpawn`

* **Syntax**: `/worlds removeSpawn`
* **Permission**: `buildsystem.removespawn`
* **Description**: Deletes the custom spawn point set for the target world.

***

## Whitelist Management

### `/worlds addBuilder <world> <player>`

* **Syntax**: `/worlds addBuilder <world> <player>`
* **Permission**: `buildsystem.addbuilder`
* **Description**: Adds a player to the target world's builder list. Only the creator or an admin can manage this list.

### `/worlds removeBuilder <world> <player>`

* **Syntax**: `/worlds removeBuilder <world> <player>`
* **Permission**: `buildsystem.removebuilder`
* **Description**: Removes a player from the builder list.

### `/worlds builders [world]`

* **Syntax**: `/worlds builders [world]`
* **Permission**: `buildsystem.builders`
* **Description**: Opens a GUI displaying all whitelisted builders for the target world.

***

## Folder Management

### `/worlds folder <folder> add <world>`

* **Syntax**: `/worlds folder <folder> add <world>`
* **Permission**: `buildsystem.folder.add`
* **Description**: Adds the world to the specified folder.

### `/worlds folder <folder> remove <world>`

* **Syntax**: `/worlds folder <folder> remove <world>`
* **Permission**: `buildsystem.folder.remove`
* **Description**: Removes the world from the specified folder.

### `/worlds folder <folder> delete`

* **Syntax**: `/worlds folder <folder> delete`
* **Permission**: `buildsystem.folder.delete`
* **Description**: Deletes the empty folder directory.

### `/worlds folder <folder> setPermission <permission>`

* **Syntax**: `/worlds folder <folder> setPermission <permission>`
* **Permission**: `buildsystem.folder.setpermission`
* **Description**: Configures an access permission for the folder.

### `/worlds folder <folder> setProject <project>`

* **Syntax**: `/worlds folder <folder> setProject <project>`
* **Permission**: `buildsystem.folder.setproject`
* **Description**: Configures a project tag for the folder.

### `/worlds folder <folder> setItem <Material>`

* **Syntax**: `/worlds folder <folder> setItem <Material>`
* **Permission**: `buildsystem.folder.setitem`
* **Description**: Sets the display material representing the folder in menus.

***

## Utility Commands

### `/worlds help`

* **Syntax**: `/worlds help`
* **Permission**: `buildsystem.help.worlds`
* **Description**: Displays the help panel index.

### `/worlds info [world]`

* **Syntax**: `/worlds info [world]`
* **Permission**: `buildsystem.info`
* **Description**: Prints world metadata (creation date, physics, AI status, visibility) directly to chat.

### `/worlds item`

* **Syntax**: `/worlds item`
* **Permission**: `buildsystem.item`
* **Description**: Spawns the navigator clock item inside the sender's inventory.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://buildsystem.eintosti.de/v4/command-reference/worlds.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.