> 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-deathscreen/configuration/discord.md).

# Discord Death Log

Set these in `server/config.lua`.

```lua
ServerConfig.DiscordWebhook = 'https://discord.com/api/webhooks/...'
ServerConfig.LogDeaths = true
```

Every death is posted as an embed with the player and server ID, the cause, the killer, the identifier (license) and the position. Leave the webhook empty to turn the log off.

{% hint style="warning" %}
Never put the webhook in `config.lua`. That file is sent to every player. `server/config.lua` stays on the server.
{% endhint %}

## Trust

The cause and the killer are reported by the player's own client, so a modified client could report false ones. The player's name, the identifier and the position come from the server. Treat the log as a record, not as proof, and do not punish players on the strength of the killer field alone.

Reports are limited to one per player every 3 seconds, and only known causes and online players are accepted.


---

# 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-deathscreen/configuration/discord.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.