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

# Introduction

In Battleworld, players, also known as **Contenders,** take on the role as owners of one or more warriors. Warriors come in many types, and they are martial artists, combat experts, and champions from many worlds throughout the Universe.&#x20;

{% hint style="info" %}
Each Acolyte and Renegade warrior is unique (and each is an NFT) that you can acquire, train, and develop into the warrior that you want them to be
{% endhint %}

In the Alpha version you do not control your warrior but rather guide their journey and ensure their victory through strategic decisions and wise management.

![](/files/XT531Evx743BkhByxI1i)


---

# 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://taunt-battleworld.gitbook.io/battleworld/acolyte-warriors/introduction.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.
