> For the complete documentation index, see [llms.txt](https://mango-5m.gitbook.io/mango5m-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mango-5m.gitbook.io/mango5m-docs/resources/mango-dispatch/configuration/config-files-overview.md).

# Config Files Overview

What each file does and which ones you are meant to touch.

### The files you edit

| File                              | What it holds                                                                                    |
| --------------------------------- | ------------------------------------------------------------------------------------------------ |
| `config/config.lua`               | `Config.Debug`, framework resource names, the whole `Config.Dispatch` block, `Config.Recipients` |
| `config/bridge.lua`               | `Config.Bridge.Framework` and `Config.Bridge.Notifications`                                      |
| `bridge/framework/custom.lua`     | Your own framework, if you are not on ESX/QBCore/Qbox                                            |
| `bridge/notifications/custom.lua` | Your own notification resource                                                                   |
| `web/css/style.css`               | Colours, spacing and sizing for every piece of the UI                                            |
| `web/sounds/`                     | Alert audio files                                                                                |

All six are listed in `escrow_ignore`, so they stay readable and editable after the resource is escrowed.

### The top of `config/config.lua`

```lua
Config.Debug = false

Config.ESXResource = 'es_extended'
Config.QBCoreResource = 'qb-core'
Config.QBoxResource = 'qbx_core'
```

| Key                     | Default       | What it does                                                                    |
| ----------------------- | ------------- | ------------------------------------------------------------------------------- |
| `Config.Debug`          | `false`       | Prints `[mango_dispatch:DEBUG]` lines when calls are created and units register |
| `Config.ESXResource`    | `es_extended` | Only change if your core resource is renamed                                    |
| `Config.QBCoreResource` | `qb-core`     | As above                                                                        |
| `Config.QBoxResource`   | `qbx_core`    | As above                                                                        |

Those three names are what the framework bridges probe with `GetResourceState`, so a renamed core will not be auto-detected until you correct the name here.

### The two blocks below it

`Config.Dispatch` is one table holding every gameplay setting - timers, the alert card, the call window, keys and the responding blip. It is documented field by field in [Dispatch Settings](/mango5m-docs/resources/mango-dispatch/configuration/dispatch-settings.md), [Keybinds](/mango5m-docs/resources/mango-dispatch/configuration/keybinds.md) and [Alerts and Sound](/mango5m-docs/resources/mango-dispatch/configuration/alerts-and-sound.md).

`Config.Recipients` decides who counts as a unit. See [Recipients and Units](/mango5m-docs/resources/mango-dispatch/configuration/recipients-and-units.md).

{% hint style="info" %}
No value in this config has to match anything in another resource. Mango Dispatch never reads another resource's config, and nothing outside it reads this one.
{% endhint %}

### Files you should not edit

Everything under `server/`, `client/`, `shared/`, `bridge/core.lua` and `web/js/` is the resource itself. If you find yourself wanting to change one of them, there is very likely an export or a bridge file that already does what you need - see the [Developer Guide](/mango5m-docs/resources/mango-dispatch/developer-guide.md).