> For the complete documentation index, see [llms.txt](https://documentation.rcore.cz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.rcore.cz/paid-resources/rcore_gangs/integrations/integrations-dispatch.md).

# Dispatch

{% hint style="warning" %}
For experienced **DEVELOPERS** only!
{% endhint %}

## Config File

Start by setting the dispatch to zero and make sure you don't have any of the supported dispatches present on your server:

```lua
Config.Dispatch = 0
```

## Dispatch Files

This resource utilizes dispatch for drug sales only. The file which you need to integrate is located in `rcore_gangs/server/dispatch/dispatch.lua` and optionally you can put your client code in `rcore_gangs/client/dispatch/dispatch.lua`. As with the framework or the inventory the bridge function in this file is described in JSDoc. You can get a good idea on what to do from the other dispatch files. The bridge function prints out an error message in the default, here's an example:

{% tabs %}
{% tab title="Client" %}

```lua
-- Client side is left empty in the default
```

{% endtab %}

{% tab title="Server" %}

```lua
-- Sends a dispatch to all police officers
-- @param {number} source - The server identifier of the player who sold the drug
-- @param {string} drug - The name of the drug that was sold
-- @returns {nil}
Dispatch = function(source, drug)
    -- If the dispatch you use is not supported by this script, place your code here
    print('^1[GANGS] Dispatch not recognized^7')
end
```

{% endtab %}
{% endtabs %}


---

# 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://documentation.rcore.cz/paid-resources/rcore_gangs/integrations/integrations-dispatch.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.