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

# Troubleshooting

## The stretcher or wheelchair is stuck to me

Type `/emsfix`. It safely drops the equipment and detaches any patient, then resyncs with the server.

## The items do nothing

* The items are missing from your inventory, see [Items](/daddy-studios-docs/scripts/daddy-patienttransport/items.md)
* Your character is not on the job in `Config.JobName`, or is off duty
* `daddy-patienttransport` started before your framework, move it lower in `server.cfg`

## The models are invisible or I fell through them

`daddy-patienttransport-props` is not started, or you did not reconnect after installing. Start it before the script and reconnect.

## E does not load the stretcher into the ambulance

The ambulance model is not in `Config.Ambulance.vehicles`, or `detection` is too small for it. See [Installation](/daddy-studios-docs/scripts/daddy-patienttransport/installation.md#ambulances).

## The patient floats or sinks on the stretcher

Adjust `x`, `y`, `z` of the pose in `Config.Positions`, or `Config.DownedPosition` for downed patients.

## A stretcher or wheelchair disappeared

Equipment left on the ground with nobody using it is removed after `Config.Sync.idleCleanup` seconds (15 minutes by default). Set it higher, or `0` to keep it forever.

## Admin diagnostics

`/emsdiag` prints the sync state to the server console. It needs the ACE:

```cfg
add_ace group.admin daddypt.diag 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-patienttransport/troubleshooting.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.