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

# Configuration

| File                               | What it holds                                                             |
| ---------------------------------- | ------------------------------------------------------------------------- |
| `config/config.lua`                | Language, framework, job, duty and test options                           |
| `config/cfg_stretcher.lua`         | Stretcher, color, item, ambulances and patient poses                      |
| `config/cfg_wheelchair.lua`        | Wheelchair, color, item, brakes and access                                |
| `config/cfg_sync.lua`              | Sync timings, idle cleanup and diagnostics                                |
| `locales/en.lua`, `locales/tr.lua` | All texts                                                                 |
| `bridge/`                          | Framework, inventory, target and fuel integration (open in both editions) |

## config.lua

```lua
Config.Language = 'en'                  -- 'en' or 'tr', see locales/
Config.Framework = 'auto'               -- 'auto', 'qbx', 'qb' or 'esx'

Config.JobName = 'ambulance'            -- job allowed to use the equipment, or a list: { 'ambulance', 'doctor' }
Config.RequireOnDuty = true             -- Qbox/QBCore only, ESX has no duty state

Config.EnableTestCommands = false       -- /testped and /deltestped spawn a local injured NPC to practise with
Config.TestBypassJob = false            -- test only: skips the job check for everyone, only works while EnableTestCommands is true

Config.IsDowned = nil                   -- function() return exports.my_medical:IsDead() end
Config.GiveKeys = nil                   -- function(target, vehicle) end
```

## cfg\_sync.lua

Leave the timings as they are. The one setting you may want to change:

```lua
idleCleanup = 900,                  -- seconds an unused stretcher/wheelchair may stand on the ground before it is removed, 0 = never
```

Equipment that is carried, stored in an ambulance or has a patient is never removed.

## Pages

* [Colors & Models](/daddy-studios-docs/scripts/daddy-patienttransport/configuration/colors.md)
* [Patient Poses](/daddy-studios-docs/scripts/daddy-patienttransport/configuration/poses.md)
* [Wheelchair Access](/daddy-studios-docs/scripts/daddy-patienttransport/configuration/wheelchair-access.md)
* [Framework Support](/daddy-studios-docs/scripts/daddy-patienttransport/configuration/framework.md)


---

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