> 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/cause-of-death.md).

# Cause of Death

With `Config.ShowCause = true` the screen shows an icon and the cause, for example "Gunshot wound" under "CAUSE OF DEATH".

| Cause       | English        | Icon       |
| ----------- | -------------- | ---------- |
| `shot`      | Gunshot wound  | crosshair  |
| `melee`     | Blunt force    | fist       |
| `explosion` | Explosion      | burst      |
| `fire`      | Burns          | flame      |
| `fall`      | Fall           | arrow down |
| `drowning`  | Drowning       | waves      |
| `vehicle`   | Vehicle impact | car        |
| `bleeding`  | Blood loss     | drop       |

The texts are `cause_<key>` entries in `locales/*.json`, change them there.

## Where the cause comes from

* **Qbox:** `qbx_medical` passes the attacker and the weapon with its death event
* **ESX:** `es_extended` passes the cause and the killer with `esx:onPlayerDeath`
* **QBCore and standalone:** the last damage the player took is remembered through the game event `CEventNetworkEntityDamage`

If a player is downed first and dies later, the cause of the last stand is kept. When the framework reports nothing, no cause is shown.

## Killer name

`Config.ShowKillerName` shows "Killed by " when another player killed the character. It is **off by default**: it invites revenge and metagaming. The name is the character name from your framework, resolved by the server.


---

# 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/cause-of-death.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.