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

# Avatar System

<figure><img src="/files/5jo6nXysPTkIBGCw8gb4" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
The choice of an avatar is made once and cannot be changed.
{% endhint %}

The Avatar system in Moovy is one of the key features of the game. In Moovy, players can create and customize their own avatar, which represents them in the game. Avatars can be customized with different clothing and accessories, allowing players to express their unique style and personality.

There are three different types of avatars in Moovy: Driver, Technician, and Ecologist. Each avatar type has its own unique attributes, such as Versatility, Fame, and Mastery, which can impact their performance in the game. This system determines the attributes of each avatar and car and is used to calculate the rewards players can earn in the game.

Additionally, players earn XP to level up their avatar and improve their Versatility, Fame, and Mastery. This allows players to further optimize their performance and increase their earnings and in-game development.


---

# 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://moovy-io.gitbook.io/moovy.io-whitepaper/gamefi-elements/avatar-system.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.