> 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/ghosts-and-evidence.md).

# Ghosts & evidence

All 10 ghosts, their evidence and behaviour.

| Ghost           | EMF 5 | Freezing | Spirit Box | Orbs | Writing | Behaviour                                                        |
| --------------- | :---: | :------: | :--------: | :--: | :-----: | ---------------------------------------------------------------- |
| **Spirit**      |   ✔   |          |      ✔     |      |    ✔    | No special traits                                                |
| **Wraith**      |   ✔   |     ✔    |      ✔     |      |         | Can appear right behind a player                                 |
| **Banshee**     |   ✔   |     ✔    |            |   ✔  |         | Always hunts the player with the lowest sanity                   |
| **Demon**       |   ✔   |     ✔    |            |      |    ✔    | Hunts from 70% sanity, very active                               |
| **Phantom**     |   ✔   |          |      ✔     |   ✔  |         | Seeing it drains twice as much sanity                            |
| **Jinn**        |   ✔   |          |            |   ✔  |    ✔    | Very fast when its target is far away                            |
| **Mare**        |       |     ✔    |      ✔     |   ✔  |         | Flickers the lights often, hunts from 60%                        |
| **Shade**       |       |     ✔    |      ✔     |      |    ✔    | Shy – barely active when the team stays together, hunts from 35% |
| **Revenant**    |       |     ✔    |            |   ✔  |    ✔    | Slow, but sprints once it sees its target                        |
| **Poltergeist** |       |          |      ✔     |   ✔  |    ✔    | Throws objects a lot                                             |

Every combination of 3 evidence types belongs to exactly one ghost, so three found evidence types always identify the ghost. On **Nightmare** one of the three is hidden – use behaviour to tell the ghosts apart.

## Tuning ghosts

Each ghost in `Config.Ghosts` can be adjusted:

```lua
{ id = 'demon', evidence = { 'emf', 'freeze', 'writing' }, huntAt = 70, speed = 1.8, activity = 1.3, throws = 0.20 },
```

| Key        | Meaning                                                                    |
| ---------- | -------------------------------------------------------------------------- |
| `huntAt`   | Average team sanity below which the ghost may hunt                         |
| `speed`    | Hunt speed: 1.0 walk, 2.0 run, 3.0 sprint                                  |
| `activity` | Multiplier for how often events happen                                     |
| `throws`   | Weight of throwing objects among events                                    |
| `special`  | `teleport`, `target_weakest`, `shy`, `fast_chase`, `jinn`, `dark`, `drain` |

Names and descriptions are in the language files (`ghost_<id>` and `ghost_<id>_desc`).


---

# 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/ghosts-and-evidence.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.