> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-combatlog/configuration/server-settings.md).

# Server Settings

Everything in `server/config.lua`. This file is loaded by the server only and is never sent to players, so the Discord webhook is safe here.

| Setting                | Default         | Description                                                                              |
| ---------------------- | --------------- | ---------------------------------------------------------------------------------------- |
| `DiscordWebhook`       | `''`            | Webhook URL that receives every combat log. Empty = off                                  |
| `UseDatabase`          | `false`         | Save logs to the `daddy_combatlogs` table (needs oxmysql)                                |
| `DisplayDuration`      | `60`            | Seconds a log stays visible. Allowed range 30-180                                        |
| `BroadcastRadius`      | `150.0`         | Meters: players this close to the spot receive the log. Admins always do. `0` = everyone |
| `Identifier`           | `'license'`     | `'license'`, `'steam'`, `'discord'` or `'fivem'`. Falls back to the license              |
| `IdentifierAdminsOnly` | `true`          | Only admins see the identifier on the panel                                              |
| `AdminAce`             | `'group.admin'` | Principal allowed to use the admin commands                                              |
| `AdminNotify`          | `true`          | Notify online admins when someone combat logs                                            |
| `IgnoredReasons`       | `{}`            | Disconnect reasons that are not logged                                                   |
| `ReasonLabels`         | see file        | Maps disconnect reason texts to labels                                                   |

## Ignoring reasons

A disconnect whose reason contains one of these texts (case-insensitive) is not logged:

```lua
ServerConfig.IgnoredReasons = { 'connecting to another server' }
```

## Reason labels

The server compares the disconnect reason with `ReasonLabels` from top to bottom and uses the first pattern it finds in the text, so keep the most specific patterns on top. `key` points to a `reason_<key>` entry in `locales/*.json`.

| Key                | Meaning                      |
| ------------------ | ---------------------------- |
| `kicked_afk`       | Kicked for being AFK         |
| `game_crashed`     | Game crashed                 |
| `timed_out`        | Connection timed out         |
| `exiting`          | Exited through F8            |
| `connecting_other` | Connecting to another server |
| `quit`             | Quit the game                |
| `kicked_admin`     | Kicked                       |
| `banned_admin`     | Banned                       |

To add a reason, add an entry to `ReasonLabels` and a matching `reason_<key>` text to every file in `locales/`. A reason that matches nothing is shown as the raw text FiveM sent.


---

# 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://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-combatlog/configuration/server-settings.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.