> For the complete documentation index, see [llms.txt](https://boundbyoath-bbo.gitbook.io/animation-composer-system-acs-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://boundbyoath-bbo.gitbook.io/animation-composer-system-acs-documentation/outline/sample-material.md).

# Sample Material

I recommend opening the **Sample Scene** to explore the setup. Inside, you’ll find **three characters**:

* One using a **CharacterController** component
* One using a **Rigidbody** component
* And one that’s completely **bare**

Each character includes a sample script I created called **`AnimationTester`**, which allows you to quickly test animations by binding different **AnimComposers** to different input keys.

***

<figure><img src="https://3643221000-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOonWvHFQUDRtnFYUlNna%2Fuploads%2Fo8hufoiW9QfIQMJYVDre%2FAnimationTester.gif?alt=media&amp;token=1e453c9c-9b7c-486c-9946-ba750d19f0eb" alt=""><figcaption></figcaption></figure>

***

Some of the assigned **AnimComposers** are **full animations**, while others are **additive blends** or **bone-specific overrides**. This setup lets you easily observe how different animation types mix together in real time.

All characters share the same array of **AnimComposers**. This demonstrates that a single AnimComposer can work across multiple **Humanoid** characters—regardless of the **Preview Model** selected for it.

You only need to create a **character-specific AnimComposer** when the **ActionBlock settings** should differ between characters. For example:

* A larger character may cover more distance due to **Motion Warping**.
* A particular character might trigger **unique sounds** or **custom effects** on certain actions (like dying or attacking).

Feel free to **inspect and modify** these sample characters. You can insert your own custom **AnimComposers** into the **AnimationTester** component to see how they behave, or use one of the **template characters** as a foundation for building your own custom setup.

***

<figure><img src="https://3643221000-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOonWvHFQUDRtnFYUlNna%2Fuploads%2FJv4W7Y6Y9bpUDre14Di4%2FSampleScene.gif?alt=media&amp;token=b0fa7c63-6d3b-4138-a43c-1a2bbba1790b" alt=""><figcaption></figcaption></figure>

***


---

# 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://boundbyoath-bbo.gitbook.io/animation-composer-system-acs-documentation/outline/sample-material.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.
