> 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/inventory-set/events.md).

# Events

There are currently multiple places that events fire from.

1. Inventory Slot
2. Inventory
3. Item

The idea behind this is so that it is granular enough for developers to add in functions based on certain criteria.&#x20;

\
E.g. certain items may have different effects when used - you would put this at the Item level. Or you may have certain effects when any weapon is equipped in the inventory - you would put this at inventory level.

On each of these, there are the following events:<br>

### OnItemDropped

Fires when the item is dropped from the Inventory

### OnItemUsed

Fires when the item is used in the inventory

### OnItemEquipped

Fires when the item is equipped from the inventory

### OnItemUnequipped

Fires when the item is unequipped

### OnItemRemoved

Fires when the item is forcibly removed from the inventory

{% hint style="warning" %}
Be warned - think about your approach prior to using the events as they all invoke at the same time. E.g. You may end up with multiple effects if you use the same function on multiple events.
{% 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/inventory-set/events.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.
