> For the complete documentation index, see [llms.txt](https://docs.odyssey.stream/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.odyssey.stream/instant-multiplayer/avatars.md).
# Avatars
## Overview
Odyssey has provided customizable, high-fidelity avatars to use in your project. The avatars are already networked, animated, and do not require any configuration to use.
Features include:
* **Metahuman bodies & clothing** - Diverse set of body and clothing options.
* **Ready Player Me heads** - Users can easily create heads from their likeness.
* **High-fidelity animations** - Naturalistic movements crafted by Odyssey.
* **Loading screen integration** - Users can customize while waiting.
{% hint style="info" %}
Avatars are completely optional. You can also use your own networked player.
{% endhint %}
## Enable Avatars
Enabling Avatars is easy and doesn't require any configuration or code.
1. Open your project. Navigate to **Project Settings -> Odyssey -> Player Type.**
2. Set Player Type to `Odyssey Avatar`.
3. Follow the validation prompts that will correctly set up your project settings.
4. When you ship your project you will now automatically be using Avatars for your player pawn.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.odyssey.stream/instant-multiplayer/avatars.md?ask=&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 `build a script that syncs our docs to a CMS` 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.
