> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/core/cuxial-admin/developers.md).

# Exports & events

Public API of Cuxial Admin: the event other resources can listen to and the events it reads.

Cuxial Admin has no exports. Its public surface is one client event, plus a few events from other resources that it listens to.

## Client events

### cuxial\_admin:revived

Fired on the client of a player who has just been revived by the panel's own revive. It carries no arguments.

```lua
AddEventHandler('cuxial_admin:revived', function()
    -- reset your own death state here
end)
```

{% hint style="info" %}
This event is not fired when `cuxial_medical` is running. In that case the revive goes through the medical system and the panel does nothing on its own.
{% endhint %}

## Events it listens to

Cuxial Admin reacts to these events when another resource sends them. You do not need to do anything for them to work.

| Event                         | Side   | Effect                                    |
| ----------------------------- | ------ | ----------------------------------------- |
| `txAdmin:events:playerBanned` | Server | Adds the ban to the sanctions history     |
| `txAdmin:events:playerKicked` | Server | Adds the kick to the sanctions history    |
| `txAdmin:events:playerWarned` | Server | Adds the warning to the sanctions history |

## Internal events

Every other event and callback starting with `cuxial_admin:` is internal. They check the caller's rank on the server and may change without notice. Do not trigger them from your own resources.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cuxial.com/scripts/core/cuxial-admin/developers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.