> 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-patienttransport/configuration/poses.md).

# Patient Poses

EMS picks a pose with **Change Position** on the stretcher. Poses live in `config/cfg_stretcher.lua`:

```lua
Config.Positions = {
    { localeKey = 'pos_lay_back',  anim = 'savecouch@', lib = 't_sleep_loop_couch', x = 0.0, y = 0.2, z = 1.1, r = 180.0 },
    { localeKey = 'pos_sit_right', anim = 'amb@prop_human_seat_chair_food@male@base', lib = 'base', x = 0.0, y = -0.2, z = 0.55, r = -90.0 },
    { localeKey = 'pos_sit_left',  anim = 'amb@prop_human_seat_chair_food@male@base', lib = 'base', x = 0.0, y = -0.2, z = 0.55, r = 90.0 },
    { localeKey = 'pos_sit_up',    anim = 'amb@world_human_stupor@male_looking_left@base', lib = 'base', x = 0.0, y = 0.3, z = 1.5, r = 180.0, openDoor = true },
}
```

* `localeKey`: the label in `locales/`
* `anim`, `lib`: animation dictionary and clip
* `x`, `y`, `z`, `r`: offset and rotation on the stretcher
* `openDoor`: raises the back rest

## Downed patients

A dead or last stand patient keeps the death animation of your medical script. The script only moves them to a flat stretcher with `Config.DownedPosition`, and **Change Position** is hidden for them.

Downed state is read from qbx\_medical on Qbox, from the player metadata on QBCore and from the ped on ESX. For another medical script, set `Config.IsDowned` in `config/config.lua`.


---

# 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-patienttransport/configuration/poses.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.