> For the complete documentation index, see [llms.txt](https://docs.sandbox.game/en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sandbox.game/en/creator/voxedit/docs/animator/build-a-rig.md).

# Build a Rig

## What is a Rig?

A <mark style="color:yellow;">**rig**</mark> is a combination of multiple models to shape a compound asset (static) or an animated asset and define how the models may move in relation to each other.

The relationships are set up in a hierarchy of parent and child <mark style="color:yellow;">**nodes**</mark> in the **Skeleton**, where movement of the parent node determines the movement of its child nodes. A child node can also be a parent of other nodes, making it possible to rig and animate complex entities.

## Parent & Child Relationships

{% tabs %}
{% tab title="About Child Nodes" %}

### Child Node

A child node is attached to a parent node within the **Skeleton** hierarchy. This empty node controls the location of any attached model relative to the position of the parent node.

#### Bounding Box

When you create a new node, it will display as an empty bounding box of 32x32x32 (if bounding boxes view enabled) until a model is linked. Then the bounding box will match the model linked to the node.

#### Motion

If the position of the parent node is adjusted, the child node will follow. However, the child node can be moved independently of the parent.

The exception is when [**Inverse Kinematics**](/en/creator/voxedit/docs/animator.md#advanced-inverse-kinematics-hidden) is togged on in the **Menubar**, where the child node can be positioned and its parent (as well as its parent, and so on) will follow, which helps when it's more natural to position the child node at the end of chain of influence created from a hierarchy with multiple levels.
{% endtab %}

{% tab title="3D Movement Example" %}

### &#x20;3D Movement Example

When a child node is moved or rotated in the viewport, the child node moves independently and the parent node stays in the same location.

When a parent node is moved or rotated in the **Viewport**, the child node will follow to maintain its relationship with the parent.

#### Example: Moving a Parent Node and Its Children

<figure><img src="/files/9jvwVFerhFubJXJK8MAc" alt=""><figcaption></figcaption></figure>

#### Example: Rotating a Parent Node and Its Children

<figure><img src="/files/5Oai9gbhqWBZk3cp8gVo" alt=""><figcaption></figcaption></figure>
{% endtab %}

{% tab title="Uses & Viewing" %}

### Parent and Child Node Uses

Creating parent and child relationships between nodes can be useful for:

* Keeping nodes organised in groups for easier management of complex rigs with multiple main parts, such as a bookshelf and the items placed on it
* Building smooth, curved shapes using multiple models, such as a wheel or arch
* Creating motion where some nodes naturally follow others, such as the parts of an arm

### **View Relationships**

Using the ![](/files/rgRQds61aLCQ8i5HH0zr) button in the **Menubar**, the rig's skeleton visibility can be toggled on/off.

<div><figure><img src="/files/wbRgtJpGJyYdBgM8AgZK" alt="" width="150"><figcaption><p>Normal View</p></figcaption></figure> <figure><img src="/files/VtL5ugCGZ9wXsbgkUWwN" alt="" width="150"><figcaption><p>The Skeleton of the Rig</p></figcaption></figure></div>

The image on the left shows the asset's appearance, with models linked to the rig's nodes.&#x20;

The image on the right shows the asset's skeleton, with red lines that are thick at a connection with a parent node and thin at a connection with a child node.

{% hint style="info" %}
**PARENT/CHILD SIMILARITIES IN VOXEDIT & GAME MAKER**\
The parent and child relationships defined in the **Skeleton** of the **Animator** are similar to the parent and child relationships of objects defined in Game Maker's **Hierarchy**.&#x20;

In both software, the parent's position and rotation influences the same for the child.
{% endhint %}
{% endtab %}
{% endtabs %}

## Build a Rig

{% tabs %}
{% tab title="About" %}

<div><figure><img src="/files/WEGCzvW3MDXz9Et4hq4g" alt=""><figcaption><p>Static Compound Entity</p></figcaption></figure> <figure><img src="/files/ltAQEmKUDLXZse5ntWvZ" alt=""><figcaption><p>Skeleton Panel showing the rig</p></figcaption></figure></div>

1. To create a rig, first you must first decide the shape of your whole entity.
2. Then you will [**break it down**](/en/creator/voxedit/creative-guides/art-techniques/3d-design/break-down-objects.md) into smaller parts, or models, based on the necessary structure, whether it is static or animated.
3. To move these parts, <mark style="color:yellow;">**nodes**</mark> must be added in the **Skeleton** in a hierarchy of parent and child relationships.

{% hint style="info" %}
Nodes are sometimes called the "bones" of the "skeleton."
{% endhint %}

3. Models are linked to each node with a simple drag and drop from the Library to the node. Then they are positioned by selecting tools in the **Menubar** and adjusting in the **Viewport**. Be sure the pivot point for each model is positioned correctly for the expected motion.

**Example:**

The pivot point on the lid of a chest should be on the back where the hinges would be.

4. You can create multiple animation states in the **Timeline**, which are poses of your rig's nodes/models. For each animation state, you can add motion keyframes to make the nodes/models move.
   {% endtab %}

{% tab title="A Rig & Its Parts" %}
The entity below is one of many VoxEdit [Templates](/en/creator/voxedit/docs/templates.md), broken down into its models. The joints on a real animal help visualise all of its parts, which will become separate models. The joints also help visualise where the pivot point on each model should be, knowing how a model should move and rotate.

<div><figure><img src="/files/pZI56bHXD9ycZzgtqBZZ" alt=""><figcaption><p>This image shows multiple models combined in the rig</p></figcaption></figure> <figure><img src="/files/2LrlqfgZNgWDeiEUHAC9" alt=""><figcaption><p>This image shows all models in the rig separated</p></figcaption></figure></div>

To simulate the movements of a dog or wolf, an entity would need parts such as:

<table data-view="cards"><thead><tr><th></th></tr></thead><tbody><tr><td><p><strong>BODY CENTRE</strong></p><ul><li><code>Torso</code></li><li><code>Pelvis</code></li></ul></td></tr><tr><td><p><strong>HEAD</strong></p><ul><li><code>Neck</code></li><li><code>Head</code></li></ul></td></tr><tr><td><p><strong>TAIL</strong></p><ul><li><code>Tail01</code></li><li><code>Tail02</code></li><li><code>Tail03</code></li></ul></td></tr><tr><td><p><strong>FRONT LEGS</strong></p><ul><li><code>FrontLeg01</code></li><li><code>FrontLeg02</code></li><li><code>FrontFoot</code></li></ul></td></tr><tr><td><p><strong>BACK LEGS</strong></p><ul><li><code>BackLeg01</code></li><li><code>BackLeg02</code></li><li><code>BackLeg03</code></li><li><code>BackFoot</code></li></ul></td></tr></tbody></table>

The `Torso` and `Pelvis` are the center of the animal's body, so they should be parents of all other nodes. The `Head` and `Front Legs` are attached at the `Torso` and the `Tail` and `Back Legs` are attached at the Pelvis.

Except for the `Body Centre` group above, think of each of the other groups above as a chain of child nodes (and remember you'll need a chain for each `Front Leg` and `Back Leg`, as well as the `Tail`). There are a lot of nodes to add for this rig, but breaking it down like this makes it easier to get started.
{% endtab %}

{% tab title="The Skeleton" %}
The **Skeleton** shows the hierarchy of nodes, and the **Viewport** shows the models linked to the nodes. In the template example below, you can see a cascading chain of child nodes for each leg, the tail, and the head and neck.

In the image below, the skeleton is toggled on in the **Viewport** so you can see how the models are all connected as a hierarchy in the rig.

<figure><img src="/files/VIvU5vV0Cf5TkfH2RCYK" alt=""><figcaption><p>The hierarchy and skeleton are visible to show how the models are all connected.</p></figcaption></figure>
{% endtab %}

{% tab title="Learn Skills to Build a Rig" %}
{% hint style="success" %}
**PRIOR KNOWLEDGE TO BUILD A RIG**\
Visit the [Beginners](/en/creator/voxedit/beginners.md) page for activities which gradually develop your skills:<br>

[/pages/MGU5Zs62su7XkD78bj1W#id-1.-create-a-block-paint-only](https://docs.sandbox.game/en/creator/voxedit/docs/animator/pages/MGU5Zs62su7XkD78bj1W#id-1.-create-a-block-paint-only "mention") introduces adjusting VoxEdit's camera to view your project and using basic editing tools in paint mode, which are also used in the Modeler.

[/pages/MGU5Zs62su7XkD78bj1W#id-2.-create-a-model-basic-tools](https://docs.sandbox.game/en/creator/voxedit/docs/animator/pages/MGU5Zs62su7XkD78bj1W#id-2.-create-a-model-basic-tools "mention") guides you to create and modify a model in the Modeler.<br>

[/pages/MGU5Zs62su7XkD78bj1W#id-3.-customise-a-template-animator](https://docs.sandbox.game/en/creator/voxedit/docs/animator/pages/MGU5Zs62su7XkD78bj1W#id-3.-customise-a-template-animator "mention") introduces the Animator. You'll learn to locate a node in the Animator Skeleton Panel, open its linked model seamlessly in the Modeler and edit, save, and return to the rig in the Animator.\ <br>

[/pages/MGU5Zs62su7XkD78bj1W#id-4.-build-a-rig-animator](https://docs.sandbox.game/en/creator/voxedit/docs/animator/pages/MGU5Zs62su7XkD78bj1W#id-4.-build-a-rig-animator "mention") is the main activity you'll need to rig a static compound entity (no motion). The activity includes adding and removing nodes in the Skeleton Panel, adding a model in the Library, linking models to nodes, and positioning nodes.<br>

**NEXT STEP - ANIMATION**

[/pages/MGU5Zs62su7XkD78bj1W#id-5.-create-animations-add-motion-keyframes](https://docs.sandbox.game/en/creator/voxedit/docs/animator/pages/MGU5Zs62su7XkD78bj1W#id-5.-create-animations-add-motion-keyframes "mention") continues the example from activity 4 and explains how to create multiple animations and motion keyframes for an animated entity.
{% endhint %}
{% endtab %}
{% endtabs %}

## Import a Hierarchy

Importing a hierarchy from another project can save time building the current one. Export the hierarchy you want to reuse, then open the project you want to add it to and import at the correct node location in the **Skeleton**.

This will include a structure of all nodes exported, linked models, and motion keyframes. This method is how templates are "[**unlocked**](/en/creator/voxedit/docs/templates.md#advanced-unlock-a-template)."

**Example**

You've created an excellent animation with multiple models for a flickering candle flame and want to reuse it on other assets.


---

# 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:

```
GET https://docs.sandbox.game/en/creator/voxedit/docs/animator/build-a-rig.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.