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

# Classify

Warriors are classified by Planets and Classes which will have certain effects on them in the game

## Planets

Each Warrior born will belong to a certain planet. The planet is divided according to the current standards of forming cryptocurrencies. This means, what standard the representative cryptocurrency of Warrior is formed, the Warriors will belong to the planet has that standard.

A planet will have many cryptocurrencies used to name Warriors, a cryptocurrency will have many Warriors born with certain characteristics and traits.

The planets released soon in Beta version can be named as:&#x20;

1. Bitcoin planet has BTC, BCH, etc.
2. Ethereum Planet has ETH, etc.
3. Other planets will be revealed on the project's official channels

Planets do not affect the character's base stats but will affect on other activities in the game.

![](/files/-MkjV6s5eecRkrRVtntL)

## Class

Characters are also divided into many different types of classes. Warriors of the same class will have certain advantages in the game such as changing bodyparts of each other, etc.&#x20;

A Warrior belongs to a certain class and one planet. A class can contain multiple Warrior lines and Warriors of the same cryptocurrency also belong to many classes

<table data-header-hidden><thead><tr><th width="156.97101449275365" align="center">Warrior line</th><th align="center">Class</th><th align="center">Warrior</th></tr></thead><tbody><tr><td align="center">Warrior line</td><td align="center">Class</td><td align="center">Warrior</td></tr><tr><td align="center">BTC</td><td align="center">Gangster, Knight</td><td align="center"><p><img src="/files/-MkXYKRx5Xs-ToXsAvfS" alt="" data-size="original"></p><p>Gangster Class </p></td></tr><tr><td align="center">BCH</td><td align="center">Gangster, Mechanical</td><td align="center"><p><img src="/files/-Mka1H0g2pW8ZfZ6QO7R" alt="" data-size="original"></p><p>Mechanical Class </p></td></tr><tr><td align="center">LTC</td><td align="center">Mechanical, Knight</td><td align="center"><p><img src="/files/-Mka0PndB6tNJXcxdHdX" alt="" data-size="original"></p><p>Knight Class </p></td></tr><tr><td align="center">ETH</td><td align="center">Soldier, Mage</td><td align="center"><p><img src="/files/-Mka1OPJZzF7ZZztIDHT" alt="" data-size="original"></p><p>Mage Class </p></td></tr><tr><td align="center">BNB</td><td align="center">Soldier, Hunter</td><td align="center"><p><img src="/files/-Mka2643Zy7C4keEyA4P" alt="" data-size="original"> </p><p>Soldier Class</p></td></tr><tr><td align="center">UNI</td><td align="center">Mage, Hunter</td><td align="center"><p><img src="/files/-Mka2jJUN7K8m3REDaRT" alt="" data-size="original"></p><p>Hunter Class </p></td></tr></tbody></table>

The classes and planets will be added over time when more Warriors are issued.


---

# 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://defiwarrior-1.gitbook.io/defi-warrior/the-warriors/warrior-classify.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.
