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

# Character

<figure><img src="/files/mKmc3R0sVwk5VDrQeeP3" alt=""><figcaption></figcaption></figure>

Players can embark on an adventure in **Reign Alter World** as a default Character that is not based on any race/ethnicity/nation. However, players build their Characters through daily activities (talents) and determine their roles by allocating attribute points (points earned with each level up), which will define the Character's abilities.&#x20;

There are four types of Character roles: **Guardian**, **Fighter**, **Engineer**, and **Thinker**.

For example, if a player frequently engages in mining activities and allocates points to HP (Constitution), their character would be suited as a Guardian. In a District, a Guardian fits well as a Warden or Mechanic.

By assigning the right values, they can secure the appropriate Job in the District or even be selected by the Governor to become a Region Advisor.


---

# 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://reignalterworld.gitbook.io/litepaper/gameplay/character.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.