> For the complete documentation index, see [llms.txt](https://sheets.bed.codes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sheets.bed.codes/advanced/configuration.md).

# Configuration

Sheets uses YAML for configuration files.

### Global Configuration (`config.yml`)

The global configuration file for Sheets is located at `plugins/Sheets/config.yml`.

```yaml
# Mode for plugin messages
small-caps: false

# Debug mode
debug:
  enabled: false

# Custom messages
messages:
  insufficient-requirements: "&cYou have not meet the requirements to do this"
  insufficient-funds: "&cYou do not have enough money to do this"
  insufficient-items: "&cYou do not have the required items to do this"
```

### Menu Configurations

Each menu is stored in its own YAML file in the `plugins/Sheets/menus/` folder.

#### Basic Settings

* `name`: Unique name for the menu.
* `title`: The title shown at the top of the menu (Java/Bedrock).
* `type`: The type of menu (`normal` or `anvil`).
* `size`: The size of the Java GUI (e.g., 9, 18, 27, 36, 45, 54).
* `commands`: List of commands that open this menu.

#### Button Settings

Buttons are defined in the `buttons` list.

* `slot`: The slot number or dynamic slot range.
* `material`: The Minecraft material for the item.
* `image`: The image URL or path for Bedrock form buttons.
* `name`: The display name of the item.
* `lore`: List of lore lines for the item.
* `requirements`: Conditions for visibility and interaction. See [Requirements](/features/requirements.md).
* `actions`: Actions to perform when clicked. See [Actions](/features/actions.md).

### Variables

Global variables are defined in the `variables/` folder.

```yaml
prefix: "&c&sServername"
server-ip: "123.45.67.89"
```

Use them in your menus with `{{variable_name}}`. See [Placeholders](/features/placeholders.md).


---

# 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://sheets.bed.codes/advanced/configuration.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.