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

# Preview Command

```
/deathscreentest [seconds] [dead|laststand|off] [minimal|center|cinematic]
```

| Example                                  | Result                                  |
| ---------------------------------------- | --------------------------------------- |
| `/deathscreentest 120 dead cinematic`    | Dead screen, 2 minutes, cinematic style |
| `/deathscreentest 25 dead center`        | Try the low time warning                |
| `/deathscreentest 120 laststand minimal` | Last stand screen                       |
| `/deathscreentest 0 off`                 | Close it                                |

Your character lies down and the screen opens with a sample cause. **Nothing of the real death flow runs**: no ambulance script, no hospital, no item loss. It is safe on a live server. You can still open the chat (T) to close it. Controls are locked while it runs.

If you are really down when you type it, your real state is left alone.

## Permission

The command needs the permission `command.deathscreentest`:

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


---

# 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/preview-command.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.