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

# Changelog

What changed in each version.

## 1.0.1 – final release

The script leaves beta. This version includes:

* **Per-location mission settings** in the location editor – possible ghosts, allowed difficulties, time limit and reward multiplier.
* Case board shows the real time and payout per difficulty and greys out difficulties a location does not allow.
* **Device screens** – EMF LEDs, thermometer LCD and spirit box radio instead of text hints.
* **Mission kit** – equipment is handed out when a case starts and taken back when it ends, a player leaves or disconnects.
* Only the search zone is shown on the map while investigating (point blip and GPS route optional).
* Fixed: a case was cancelled as "too far" right after starting when the hunter NPC stood far from the location.
* Console warnings when inventory items are missing.

## 1.0.0 BETA

* First public beta.


---

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