> For the complete documentation index, see [llms.txt](https://docs.existent.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.existent.com/documentation/guides/customising-player-avatar/animation-blueprint.md). # Animation Blueprint Create an animation blueprint based on the skeleton of choice and inherit from Existent Player Anim Instance.

Create animation blueprint

Start by recreating the following animation graph.

Animation Graph

Based on the type of tracking being used the setup in the animation blueprint will change. In this case the animation blueprint will drive fully-body using a 5 point tracking system. Add a root node and set the body driver to Feet & Camera.

Root node

Add a head, arms, legs and two hand nodes.

Head, arms, legs and hands nodes

Create two animation sequences representing the skeletal mesh open/close hand poses. Here is an example of what the poses may look like.

Open hand pose

Close hand pose

Back in the animation blueprint select the hand nodes and set the open/close hand poses to the respective poses. The reference pose can be either of the poses or a complete custom third pose.

Hand nodes poses

--- # 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://docs.existent.com/documentation/guides/customising-player-avatar/animation-blueprint.md?ask=&goal= ``` `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.