> For the complete documentation index, see [llms.txt](https://lua2.fatality.win/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lua2.fatality.win/api/instances/mods/events_t.md).

# Events\_t

<table><thead><tr><th width="289">Usage: mods.events.{method}</th></tr></thead><tbody><tr><td></td></tr></tbody></table>

This module lets you manage custom in-game event listener.

{% hint style="danger" %}
Please note that the game server knows which events you are listening to. Internally, we only listen to events that will get sent to the client anyway in one way or another. If you decide to listen to something the server generally does not expect, it may cause issues on official servers.
{% endhint %}

## AddListener

<mark style="color:purple;">**`Method`**</mark>

Adds a game event to the listener.

{% hint style="success" %}
Internally we listen to the following events:

* bullet\_impact
* weapon\_fire
* bomb\_beginplant
* bomb\_abortplant
* bomb\_planted
* bomb\_defused
* bomb\_exploded
* round\_start
* game\_newmap
* map\_shutdown

Adding those events to the listener is not needed.
{% endhint %}

**Arguments**

| Name   | Type     | Description |
| ------ | -------- | ----------- |
| `name` | `string` | Event name. |

**Returns**

Nothing.

**Example**

```lua
mods.events:AddListener('round_end');
```


---

# 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://lua2.fatality.win/api/instances/mods/events_t.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.