> 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/reference/troubleshooting.md). # Troubleshooting ## Third Eye option is missing * Confirm `qb-target` is running. * Confirm you are close enough and looking at the correct entity/zone. * Confirm your job, duty, ERS shift, and authorization. * Wait for the patient, witness, or scene entity to finish spawning. ## E or G no longer performs the documented custom action That is intentional. Investigations now use Third Eye, ERS crew uses `Y`/`N`, and MedicBridge opens from the patient target. ## Interface closes but input remains captured Press `Escape`. Investigations users may run `/clearinvestigation`. Record recurring incidents with the resource name and F8 output. ## Duplicate or unexpected menu options Confirm only one copy of each resource is started. The old `Stretcher` resource must remain removed; only `Stretcher_NWRRP` should run. Do not start embedded or backup copies of the dispatch resource. ## MedicBridge does not open Third-eye the correct ERS patient and choose **Treat ERS Patient**. `/ersmedbridge` is the fallback. F4 and `/ersmedui` are disabled by default. ## Court portal or DOJ workstation does not open Confirm the character is loaded. `/mycourt` is for regular players. `/doj` requires the appropriate job/duty/permission. Use `/dojstatus` during support troubleshooting. --- # 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/reference/troubleshooting.md?ask=&goal= ``` `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.