> For the complete documentation index, see [llms.txt](https://jabe.gitbook.io/jabe-rig-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jabe.gitbook.io/jabe-rig-wiki/readme.md).

# Jabe Rig Wiki

The documentation for the Jabe Rig, a Minecraft character rig for Blender.

The **Jabe Rig** is a feature-rich Minecraft character rig for Blender, packaged as an add-on with its own control panel: IK and FK, squash and stretch, facial controls, emotions, materials, taper and display settings, all of them keyframable.

## Where to start

Open the **Documentation** tab at the top of the page.

* **New to the rig?** Read *Getting Started* to install the add-on and import the rig.
* **Looking for a control?** *Features* follows the panel from top to bottom.
* **Something not working?** See *Reference*, then *Troubleshooting*.

The **Changelog** tab lists what changed in each release.


---

# 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://jabe.gitbook.io/jabe-rig-wiki/readme.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.