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

# Overview

Co-op paranormal investigations – gather evidence, survive the hunts, name the ghost.

**rayn\_ghosthunting** turns your city into a haunted playground. Players take a case from the ghost hunter, drive to a haunted location and use real inventory items – EMF reader, thermometer, spirit box, night vision camera – to collect evidence. The ghost answers with whispers, footsteps, flickering lights, thrown objects and apparitions. When the team's sanity drops, it starts to hunt.

* **10 ghosts, 5 evidence types** – every ghost leaves 3 kinds of evidence and has its own behaviour.
* **Item-based equipment** – standard usable items for ox\_inventory, ESX, QBCore and Qbox.
* **Sanity, hunts and jumpscares** – cinematic close-up when the ghost catches you, hallucinations at low sanity.
* **Dynamic creepy music** – drone, music box and heartbeat that speeds up as the ghost gets closer. Generated in code, nothing to upload.
* **Shared journal** – the team marks evidence together, the ghost list narrows itself, payout report at the end.
* **In-game location editor** – free camera and a move/rotate gizmo for rooms, decorations and NPCs.
* **Positionable UI** – every HUD block and notification can be placed anywhere on screen.
* **Multi-language** – English and Polish included, add your own in one file.

The resource works with ESX, QBCore, Qbox or without a framework.

## Where to go next

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h3><i class="fa-rocket" style="color:$primary;">:rocket:</i></h3></td><td><strong>Installation</strong></td><td>Get rayn_ghosthunting running.</td><td><a href="/rayn-scripts-docs/rayn_ghosthunting/installation.md">Installation</a></td></tr><tr><td><h3><i class="fa-box-open" style="color:$primary;">:box-open:</i></h3></td><td><strong>Items</strong></td><td>Add the equipment to your inventory.</td><td><a href="/rayn-scripts-docs/rayn_ghosthunting/items.md">Items</a></td></tr><tr><td><h3><i class="fa-magnifying-glass" style="color:$primary;">:magnifying-glass:</i></h3></td><td><strong>How to play</strong></td><td>Cases, evidence, sanity and hunts.</td><td><a href="/rayn-scripts-docs/rayn_ghosthunting/how-to-play.md">How to play</a></td></tr><tr><td><h3><i class="fa-cube" style="color:$primary;">:cube:</i></h3></td><td><strong>Location editor</strong></td><td>Build haunted places in-game.</td><td><a href="/rayn-scripts-docs/rayn_ghosthunting/location-editor.md">Location editor</a></td></tr><tr><td><h3><i class="fa-sliders" style="color:$primary;">:sliders:</i></h3></td><td><strong>Configuration</strong></td><td>Every option in config.lua.</td><td><a href="/rayn-scripts-docs/rayn_ghosthunting/configuration.md">Configuration</a></td></tr><tr><td><h3><i class="fa-circle-question" style="color:$primary;">:circle-question:</i></h3></td><td><strong>Troubleshooting</strong></td><td>Fixes for the most common issues.</td><td><a href="/rayn-scripts-docs/rayn_ghosthunting/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

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