> For the complete documentation index, see [llms.txt](https://rayn-scripts.gitbook.io/rayn-scripts-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_ghosthunting/troubleshooting.md).

# Troubleshooting

Fixes for the most common issues.

<details>

<summary>Nothing happens when I click “Use” on an item</summary>

* Make sure the item definitions from `install/ox_inventory_items.lua` are the current ones (`client = { export = 'rayn_ghosthunting.…' }`) and restart ox\_inventory.
* The folder must be named exactly `rayn_ghosthunting`.
* Items only work during an investigation – outside of one you get a notification.

</details>

<details>

<summary>No NPC / the case board does not open</summary>

* Check the NPC position in `/ghosteditor` → Hunter NPCs, or `Config.Hunters`.
* Start the resource after `ox_target` / `qb-target`. Without them use **\[E]** next to the NPC.

</details>

<details>

<summary>A location is missing on the case board</summary>

A location needs at least one ghost room. Locations already taken by another team are shown as *taken*.

</details>

<details>

<summary>Blips appear twice or behave strangely</summary>

Remove the old `ghosthunt` resource if it is still on the server. Adjust or disable blips in `Config.Blips`.

</details>

<details>

<summary>No sound</summary>

Check `Config.Volume` and the FiveM NUI volume. If you set `Config.CustomSounds`, the files must exist in `html/sounds/`.

</details>

<details>

<summary>The editor does not open</summary>

You need the ACE `rayn_ghosthunting.editor` or a framework admin group. The editor cannot be opened while you are in an investigation.

</details>

<details>

<summary>Tool props sit wrong in the hand</summary>

Tweak `offset` and `rot` of the tool in `Config.Tools`.

</details>


---

# 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://rayn-scripts.gitbook.io/rayn-scripts-docs/rayn_ghosthunting/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.