> For the complete documentation index, see [llms.txt](https://malbersanimations.gitbook.io/animal-controller/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://malbersanimations.gitbook.io/animal-controller/basic-setup-instructions/setting-up-item-inventory-types.md).
# Setting up Item/Inventory Types
Item/Inventory types are incredibly important within the Inventory System. \
\
What these essentially do, is allow us to categorise our items and then insert them into the corresponding Inventory type.
### Example
E.g. Let's say I have a Weapon. I give it the Weapon Item Type:
I also have a corresponding Inventory with that Weapon type:
Whenever I pick up this Weapon, it will now automatically go into the Inventory with the matching type.
### **Creating a New Type**
If you want to create a new Item/Inventory type, the easiest way is just to copy/paste an existing type in the Malbers Animations -> Integrations -> Inventory System -> TypeIDS folder.
Then change the Display Name and the ID.
{% hint style="danger" %}
**The ID MUST be Unique.**
{% endhint %}
---
# 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://malbersanimations.gitbook.io/animal-controller/basic-setup-instructions/setting-up-item-inventory-types.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.