> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/art-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ss3d.gitbook.io/art-guide/3d/rigging/rig-formatting/equipped-and-held-items.md).
# Equipped & Held Items
While the rigged model is useful for being worn, it is not very useful as a held or dropped item. For this purpose, **we need two models for a given piece of equipment** (with the exception of head items).
One for being worn on the character, and as an item to be held in the hand. Head-worn items generally do not deform like most clothes do, so it is unnecessary to make separate rigged and item versions of these articles.
The equipped item vs. the held item.
If for some reason you need your head-worn item to deform, then you will likely need a separate held item for it as well.
Items like headwear generally look fine without needing a held item version.
---
# 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://ss3d.gitbook.io/art-guide/3d/rigging/rig-formatting/equipped-and-held-items.md?ask=&goal=
```
`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.
