> For the complete documentation index, see [llms.txt](https://ss3d.gitbook.io/systems/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/systems/inventories.md). # Inventories Inventories represent in part what player can hold on themselves, including clothes, what they have in hand, in their pocket, in their bag, but also what they can access through a container. When a player open a toolbox and use an interaction to view it, the toolbox's container become a part of the player inventory as long as the player is observing the content of the toolbox. Inventories in SS3D rely on the container system. Every container on a player and every container viewed by the player is part of its inventory. ## Functionalities The inventory is currently responsible for the following functionalities : * Transferring an item to a container, eventually in a given slot. * Spawning an item from a container back in the world. * Firing the open animation when a container is added first to an inventory. * Switching between activated hands. * Adding and removing container to itself, firing event when doing so. * Checking server side some of the above can be done by a client asking to perform those actions. That would for instance include checking if a player can interact with their hand with a given container. ## Dependencies Containers UI are depending a lot on the inventory system, when adding a container to an inventory, it's UI(if it has one) will be displayed. The Roles System depends on it as well, as it needs to spawn role items in the inventory at the beginning of the round. --- # 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/systems/inventories.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.