> 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.md).

# Daddy Deathscreen

A death and last stand screen for FiveM with three styles, the cause of death and rotating server tips.

![Daddy Deathscreen](https://2487709298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqcEXX242M9YYHjASblGi%2Fuploads%2Fgit-blob-0e90a26d082b3c5d0ed3ded847000315dbf43cc4%2Fdaddy-deathscreen-thumbnail.jpg?alt=media)

Daddy Deathscreen replaces the death texts of your ambulance script with a clean screen. It reads the death state of the script by itself, so there is nothing to trigger by hand.

## Features

* **3 styles**: `minimal` (bottom of the screen), `center` (card with a ring timer) and `cinematic` (letterbox bars)
* **Cause of death** with an icon: gunshot, blunt force, explosion, burns, fall, drowning, vehicle impact, blood loss. Optional killer name (off by default)
* **Rotating tips** under the timer for your server rules
* **Screen effects** while dead: grey-out and blur, each one optional
* **Low time warning**: the timer turns red, optional beep
* **Accent color** and respawn fee text you can set
* **Discord death log** with player, cause, killer, position and identifier
* English and Turkish included
* No `ox_lib`, no database, no external requests

## Requirements

* FiveM server artifact 5104 or newer with **OneSync enabled**
* One of these death systems:

| Framework | Ambulance script                   | Status                                                                      |
| --------- | ---------------------------------- | --------------------------------------------------------------------------- |
| Qbox      | `qbx_medical` + `qbx_ambulancejob` | **Tested** by Daddy Studios                                                 |
| QBCore    | `qb-ambulancejob`                  | Supported                                                                   |
| ESX       | `es_extended` + `esx_ambulancejob` | Supported                                                                   |
| Any other | your own script                    | Use the [exports](/daddy-studios-docs/scripts/daddy-deathscreen/exports.md) |

Continue with [Installation](/daddy-studios-docs/scripts/daddy-deathscreen/installation.md).

***

[🛒 Escrow on Tebex](https://daddy-studio.tebex.io/package/7689274) | [🔓 Open Source on Tebex](https://daddy-studio.tebex.io/package/7689273) | [💬 Get Support](https://discord.gg/NFKjbN9s2q)


---

# 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.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.