> 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/features/requirements.md).

# Requirements

Requirements are conditions that must be met for a button to be visible or clickable.

### Usage

Requirements are defined as lists of conditions. If all conditions in a list are met, the requirement is satisfied.

**YAML Example:**

```yaml
requirements:
  view:
    - "%player_has_permission_sheets.admin% = true"
  click:
    - "%vault_eco_balance% >= 100"
    - item:
        material: DIAMOND
        amount: 1
```

### Types of Requirements

| Requirement | Description                                    |
| ----------- | ---------------------------------------------- |
| `view`      | Controls if the button is visible in the menu. |
| `click`     | Controls if the player can click the button.   |

### Supported Conditions

Conditions can use [placeholders](/features/placeholders.md) and logical expressions to determine if a requirement is met.

| Condition    | Description                                          |
| ------------ | ---------------------------------------------------- |
| `condition`  | A logical expression (e.g., `%balance% > 100`).      |
| `permission` | Checks if the player has a specific permission.      |
| `balance`    | Checks the player's Vault balance.                   |
| `item`       | Checks for specific items in the player's inventory. |

### Logical Expressions

You can use standard comparison operators in your conditions:

* `=`, `!=`, `>`, `>=`, `<`, `<=`
* `contains`, `startsWith`, `endsWith`

**Example:**

```yaml
- "%player_name% = bed"
- "%vault_eco_balance% >= 500"
```


---

# 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/features/requirements.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.