> For the complete documentation index, see [llms.txt](https://docs.sollumz.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sollumz.org/tutorials/creating-vehicles/vertex-groups-hierarchy-and-armature.md).
# Vertex Groups, Hierarchy, and Armature
### Create and assign Vertex Groups
To create a new vertex group, go to **Data** tab, click `+` in **Vertex Groups**, double click on the Group name and rename it to **bonnet**.
Process of creating a vertex group
1. Change **Object Mode** to **Edit Mode.**
2. Switch to **Face Select.**
3. Select all faces by pressing `A` or using the `CTRL+A` shortcut.
4. Go to **Vertex Groups**, click Assign button and exit **Edit Mode**.
Now all of the selected faces are properly set to the **bonnet** vertex group**.**
Assignment of faces to vertex group
### Hierarchy
Our new custom bonnet model has to be considered by Sollumz as a valid part, so we have to move the mesh by expanding Adder's armature then drag and drop bonnet's Drawable Model inside `adder.mesh`
Bonnet part moved into adder.mesh
{% hint style="info" %}
You can delete the original bonnet, since is not needed anymore.
{% endhint %}
Removal of vanilla bonnet part of adder.
### Armature
A replacement custom part has also to be linked to the armature, you can do this via **Armature** modifier.
1. Go to **Modifiers** tab.
2. Add an **Armature** modifier.
3. Select your vehicle's armature.
Armature modifier creation
---
# 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.sollumz.org/tutorials/creating-vehicles/vertex-groups-hierarchy-and-armature.md?ask=&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.
