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

# Elbify Documentation

The official documentation for the Elbify bot.

Welcome to the official **Elbify** documentation, the ultimate resource for learning more about Elbify, its powerful roleplay-enhancing features, and how to use them.

Elbify is a free-to-use, simple and powerful bot designed to enhance your Emergency Hamburg private roleplay experience. Our main goal is to provide for the communities which use Elbify on a daily basis, providing them with tools to help run roleplay servers without any hassle.

***

## Official Links

* [Support](https://discord.gg/XfkCkYJxTf)
* [Website](https://elbify.xyz/)
* [Documentation](https://elbify.gitbook.io/docs)

***

## Key

{% hint style="info" %}
**Information**

This is an information block to highlight important details of a page.
{% endhint %}

{% hint style="warning" %}
**Important**

This is an important block to highlight important details of a feature or command.
{% endhint %}

{% hint style="danger" %}
**Warning**

This is a warning block to highlight warnings of a feature or command.
{% endhint %}

***

The documentation is maintained by select documentation editors, which are handpicked by the management team. You can **express interest** in becoming a documentation editor in our [Discord community](https://discord.gg/XfkCkYJxTf).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://elbify.gitbook.io/docs/elbify-documentation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.