> 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/v2/permissions/worlds/restricting-worlds.md).

# Restricting Worlds

*BuildSystem* allows server owners to restrict which worlds a player can modify when using commands.

{% hint style="info" %}
All commands default to `.self` when no suffix (`.self`, `.other`) is provided. 

**For example:** `buildsystem.day` = `buildsystem.day.self`
{% endhint %}

### Only modify worlds owned by player

If you want a player to only modify worlds which belong to the player (i.e. player **is** creator), then use the command suffix `.self`.

**For example:** If you only want player's to change the world time to day (`/day`) in their own worlds, then give the player the permission `buildsystem.day.self`.

### Modify worlds not owned by player

With the permission suffix `.other`, a player can also modify worlds that **don't** belong to the player (player is **not** creator)

**For example:** If you only want player's to change the world time to day (`/day`) in other worlds, then give the player the permission `buildsystem.day.other`.


---

# 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, and the optional `goal` query parameter:

```
GET https://buildsystem.eintosti.de/v2/permissions/worlds/restricting-worlds.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.