> For the complete documentation index, see [llms.txt](https://docs.nwrrp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nwrrp.com/staff-admin/custom-resources.md).

# Custom Resource Administration

## Current conflict-corrected baselines

| Resource                   | Version           | Key operational change                                           |
| -------------------------- | ----------------- | ---------------------------------------------------------------- |
| `nwrrp_ers_investigations` | v0.6.3-beta.1     | Scene, evidence, witness, and lead interactions use `qb-target`. |
| `nwrrp_ers_crew`           | v0.5.1-beta.1     | `Y`/`N` invitation keys; no E/G control suppression.             |
| `nwrrp_doj`                | v2.0.0-beta.10.18 | Duplicate commands consolidated; shared NUI cleanup.             |
| `medic_bridge_als`         | v0.9.38-beta.1    | `qb-target` patient treatment; F4 disabled by default.           |
| `nwrrp_dispatch_system`    | v2.8.1-beta.1     | Test event/commands permission-protected.                        |
| `osp_ambulance`            | v1.7.4-nwrrp.1    | OSP patient medical menu disabled; MedicBridge is authoritative. |

## Recommended startup order

```cfg
ensure ox_lib
ensure oxmysql
ensure qb-target
ensure osp_ambulance
ensure nwrrp_doj
ensure nwrrp_ers_investigations
ensure nwrrp_ers_crew
ensure medic_bridge_als
ensure nwrrp_dispatch_system
```

Adjust for actual framework dependencies and keep only one active copy of each resource. Only `Stretcher_NWRRP` should run.

## Production principles

* Keep Investigations legacy key fallback disabled.
* Keep MedicBridge F4/open-UI keybind disabled.
* Keep OSP medical menu disabled.
* Keep dispatch and MedicBridge development commands disabled.
* Protect all diagnostics with ACE/QBCore permissions.
* Test NUI close, character unload, duty loss, and resource restart cleanup.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nwrrp.com/staff-admin/custom-resources.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.