> For the complete documentation index, see [llms.txt](https://docs.convai.com/api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.convai.com/api-docs/plugins-and-integrations/unreal-engine/guides/creating-metahuman-characters-1/adding-lipsync-to-metahuman.md).
# Adding ReadyPlayerMe Character
## Steps to add a ReadyPlayerMe Character
1. Create a new blueprint and select `ConvaiRPM_Character` as the parent class which you can find under `All Classes` .
2. Drag the blueprint to the scene and the default ReadyPlayerMe character should appear.
3. Create a new character on [Convai Playground](https://convai.com/pipeline/dashboard) and copy the Character ID, you can also edit the avatar by clicking on the `Edit Avatar` icon on the top right of the avatar preview window.
4. Back to Unreal, click the character in the scene and under the details panel find the Char ID field and paste the copied character ID into it.
5. Hit `Play` , and wait for a few seconds then the character should now load into the game.
{% hint style="info" %}
The first time the character loads will take more time but after that it will be cached and loaded faster.
{% endhint %}
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.convai.com/api-docs/plugins-and-integrations/unreal-engine/guides/creating-metahuman-characters-1/adding-lipsync-to-metahuman.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 `automate deployments from our CI pipeline` 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.
