> 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/effects-and-timers.md).

# Effects & Timers

## Screen effects

```lua
Config.Effects = {
    laststand = { blur = false, desaturate = false },
    dead      = { blur = false, desaturate = true },
}
Config.EffectStrength = 0.9
```

`desaturate` greys out the screen with a game timecycle modifier, `blur` blurs it. Set either one per state. The effects are removed when the screen closes.

{% hint style="warning" %}
If your ambulance script or another resource sets its own timecycle modifier, switch `desaturate` off so the two do not fight.
{% endhint %}

## Low time warning

Under `Config.LowTime` seconds (default 30) the timer, the title line and the ring turn red and the digits pulse. With `Config.LowTimeSound = true` there is a beep every second during the last 10 seconds.

## Timers

| Framework  | Where the timer comes from                                                                                                   |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Qbox       | The real timers of `qbx_medical`, nothing to set                                                                             |
| QBCore     | `Config.Timers.qb`: `dead` = your `Config.DeathTime` (default 300), `laststand` = your `Config.ReviveInterval` (default 360) |
| ESX        | `Config.Timers.esx.dead` = your `Config.EarlyRespawnTimer` divided by 1000 (default 60)                                      |
| standalone | `Config.Timers.standalone`                                                                                                   |

QBCore and ESX do not expose their timers, so these values must match the settings of your ambulance script, otherwise the screen and the script disagree.

## Respawn keys

`Config.Keys` only decides which keys are **shown**. Your ambulance script handles the real keys. The texts follow the rules of each script: on Qbox the player is taken to the hospital automatically when the timer ends, on QBCore and ESX the player holds a key after the timer, and the medic call key is only offered where it works.


---

# 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/effects-and-timers.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.