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

# Styles

Set `Config.Style` in `config.lua`, or try a style without restarting with the [preview command](/daddy-studios-docs/scripts/daddy-deathscreen/preview-command.md).

## minimal

The screen sits at the bottom centre: title, timer, description and the tip. The cause of death sits in the bottom-right corner. The edges of the screen are darkened a little, so the text stays readable on bright ground.

## center

A card in the middle of the screen with a ring that empties while the timer runs. The description, the cause of death and the tip sit inside the card.

## cinematic

Two black letterbox bars slide in. The title and the timer sit just above the bottom bar, the description is centred in the bottom bar like a subtitle and the cause of death is pinned to its right edge. The rotating tip is shown in the top bar.

## Accent color

`Config.AccentColor` accepts any CSS color, for example `'#3b82f6'`. It colors the title line, the timer ring and the icon of the cause of death. Under `Config.LowTime` seconds everything turns red.

{% hint style="info" %}
The UI is made for the browser of FiveM: no `border`, no `backdrop-filter` and no `color-mix()`. Keep that in mind when you edit `web/`.
{% endhint %}


---

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