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

# Callbacks

fatality.callbacks

## Functions

### add

Adds a function to a callback

`callbacks:add( name, function )`

| Parameter | Data type |          Description          |
| :-------: | :-------: | :---------------------------: |
|    name   |   string  |        name of callback       |
|  function |  function | function for callback to call |

## Callbacks

### paint

called every frame.

used for rendering. See [fatality.render](/fatality/render.md)

### events

called when a csgo game event is fired. See[ events examples](/csgo/interfaces/events.md#example)

### registered\_shot

called when a shot is registered on the server. See [fatality.shot\_t](/fatality/datatypes/shot.md)

## Examples

```lua
local Callbacks  = fatality.callbacks
local Render     = fatality.render
local EntityList = csgo.interface_handler:get_entity_list( )

-- Function to call on paint
local function OnPaint()
    -- Call fatality.render:rect
    Render:rect( 10, 10, 20, 20, csgo.color(255, 255, 255, 255) )    
end

-- Function to call on registered_shot with parameter
local function OnRegisteredShot(Shot)
    -- Get player from Shot.victim value
    local Player = EntityList:get_player( Shot.victim )
    -- Check if the player is valid
    if Player then
    -- Print that we hit them
        print( string.format( "Hit %s", Player:get_name( ) )
    end
end

-- Add the callbacks
Callbacks:add( "paint", OnPaint )
Callbacks:add( "registered_shot", OnRegisteredShot )
```


---

# 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://lua.legacy.fatality.win/fatality/callback.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.