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

# Installation

## Steps

### 1. Download and extract

Download the resource from your [Cfx Portal](https://portal.cfx.re/assets/granted-assets) (escrow edition) or from the store (open-source edition) and extract the archive.

### 2. Add the folder

Place the `daddy-deathscreen` folder in your server's `resources` directory.

### 3. Start order

Start it after your framework and your ambulance script:

```cfg
ensure qbx_core            # or qb-core / es_extended
ensure qbx_medical         # or qb-ambulancejob / esx_ambulancejob
ensure daddy-deathscreen
```

### 4. Hide the death texts of your ambulance script

{% hint style="warning" %}
This step is required. The ambulance scripts draw their own death texts. Without this step both texts are on screen at the same time.
{% endhint %}

You only delete a few lines that draw text in one file. Every key and every timer stays. Follow the steps for your framework in [Framework Integration](/daddy-studios-docs/scripts/daddy-deathscreen/integration.md).

### 5. Match the settings

Open `config.lua` and set `Config.RespawnFee` to the fee of your ambulance script. On QBCore and ESX also set `Config.Timers` to the timers of your script (see the same page).

### 6. Preview

Allow your admins to use the preview command in `server.cfg`:

```cfg
add_ace group.admin command.deathscreentest allow
```

Join the server and type `/deathscreentest 120 dead cinematic`. See [Preview Command](/daddy-studios-docs/scripts/daddy-deathscreen/preview-command.md).


---

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