> For the complete documentation index, see [llms.txt](https://docs.otherside.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.otherside.xyz/odk-docs/characters/creating-a-custom-character/trouble-shooting.md).

# Trouble Shooting

### MML format is correct and the GLB is valid but it is not loading in the Otherside.

Double check that the MMLs are encoded with `UTF-8` and not a something like `UTF-8 with BOM`.<br>

### Avatar prepared but not loading in ODK/Otherside

Check the output logs in editor tab for more details on possible errors.\
\- Make sure the rig uses the exact bone naming and positions from the reference skeleton.\
\- Do not include any additional bones or unsupported structures.\
\- Make sure your GLB files are publicly accessible (avoid CORS issues)


---

# 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.otherside.xyz/odk-docs/characters/creating-a-custom-character/trouble-shooting.md?ask=<question>&goal=<user_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.