> For the complete documentation index, see [llms.txt](https://docs.gercstudio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gercstudio.com/characters/controller/tags.md).

# Tags

{% hint style="info" %}
These are **not the same** as standard Unity tags, which you see in the upper right corner of the editor.
{% endhint %}

The character tag is his unique identifier, which is needed for weapons and footsteps sounds.

You can manage the tags in any character with the <mark style="color:green;">**Controller**</mark> script. If you add a new tag in one character, it will be added to other characters too, i.e. they are synchronized.

![](/files/e9hEy1GZt4yBwUecsYbB)

#### Weapons

Since all characters have different hand positions and orientations, they will hold the same weapon differently. Therefore, you can customize the hands pose for each character separately using the IK tools. And these tags are useful for distributing all IK parameters.

{% content-ref url="/pages/-LfFWCJIJVVr4jaB\_Ixj" %}
[Adjustment](/weapons/adjustment.md)
{% endcontent-ref %}

#### Footstep Sounds

Use different tags to add unique walking sounds for different characters.

{% content-ref url="/pages/-LfFYOlPtoEsVUF9uumA" %}
[Surfaces](/other-components/surfaces.md)
{% endcontent-ref %}


---

# 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://docs.gercstudio.com/characters/controller/tags.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.