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

# Installation

1. Download the resource (escrow edition from your [Keymaster](https://keymaster.fivem.net), open source edition from your Tebex purchase). It contains two folders:

   * `daddy-patienttransport`: the script
   * `daddy-patienttransport-props`: the stretcher and wheelchair models

   Put both in your `resources` folder. Do not rename them.
2. Add the `stretcher` and `wheelchair` items, see [Items](/daddy-studios-docs/scripts/daddy-patienttransport/items.md).
3. Start them after your framework, inventory and target in `server.cfg`:

```cfg
ensure daddy-patienttransport-props
ensure daddy-patienttransport
```

4. Restart the server. Players reconnect once to download the models.

{% hint style="info" %}
OneSync must be on. The stretcher and the wheelchair are created by the server.
{% endhint %}

## Ambulances

Only the base game `ambulance` is set up. Add your own ambulance models in `config/cfg_stretcher.lua`:

```lua
Config.Ambulance = {
    vehicles = {
        { model = 'ambulance', detection = 5.0, depth = -1.3, height = -0.15 },
        { model = 'my_addon_ambulance', detection = 5.0, depth = -1.8, height = -0.15 },
    },
}
```

`detection` is the distance from the vehicle center to the rear doors. `depth` and `height` place the stretcher inside the vehicle; test them in game for every model.

## How to use

| Action                  | How                                                                               |
| ----------------------- | --------------------------------------------------------------------------------- |
| Unfold a stretcher      | Use the `stretcher` item, you are carrying it right away                          |
| Drop the stretcher      | **G** while carrying                                                              |
| Take the stretcher      | Target the stretcher, **Take Stretcher**                                          |
| Lay a patient           | Target the player next to the stretcher, **Lay on Stretcher**                     |
| Change the pose         | Target the stretcher, **Change Position**                                         |
| Load into the ambulance | Carry the stretcher to the rear doors and press **E**                             |
| Fold it back            | Target an empty stretcher, **Fold Stretcher**                                     |
| Wheelchair              | Use the `wheelchair` item, then **Push**, **Seat in Wheelchair**, **Lock Brakes** |


---

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