> For the complete documentation index, see [llms.txt](https://conditions.gitbook.io/conditions-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://conditions.gitbook.io/conditions-docs/usage.md).

# Usage

### Conditional text

This way allows you to create conditional text that depends on other placeholders.

First, find the `conditions` section in your config and create a new condition like this one:

```
conditions:
  lobby:
    conditions:
    - '%server%=lobby'
    true: "You are in lobby"
    false: "You are not in lobby"
```

This condition checks if player is in server `lobby` and if yes, displays `"You are in lobby"`, otherwise displays `"Your are not in lobby"`.\
To check for more than just 1 condition, add more to the list. Additionally, you will now need to specify `type`, which is either `AND` or `OR`.

For example,

```
conditions:
  lobby:
    conditions:
    - '%server%=lobby'
    - '%server%=lobby2'
    type: OR
    true: "You are in lobby"
    false: "You are not in lobby"
```

will return the lobby text if player is in server `lobby` **OR** in server `lobby2`. If you want both of those conditions to be required to display text, use `type: AND`.\
It is not possible to combine both `AND` and `OR` in a single condition. To do that, create multiple conditions and use one inside another.

Now that the condition is created, we can use it using `%conditions_lobby%`. This placeholder will return the texts configured in `true` and `false` values based on whether the condition was met or not.


---

# 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://conditions.gitbook.io/conditions-docs/usage.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.