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

# Installation

Get rayn\_ghosthunting running.

1. Upload `rayn_ghosthunting` to `resources/`.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>Keep the folder name exactly <code>rayn_ghosthunting</code> – the ox_inventory items call exports by this name.</p></div>
2. Add it to `server.cfg` **after** your framework and ox resources:

   ```
   ensure ox_lib
   ensure ox_inventory
   ensure ox_target
   ensure rayn_ghosthunting
   ```
3. Give admins access to the location editor:

   ```
   add_ace group.admin rayn_ghosthunting.editor allow
   ```

   ESX `admin` / `superadmin` and QBCore `admin` / `god` have access as well while `Config.Editor.frameworkAdmins = true`.
4. Add the items to your inventory – see [Items](/rayn-scripts-docs/rayn_ghosthunting/items.md).
5. Set the language in `config.lua` → `Config.Locale` (`en` or `pl`).
6. Restart the server, join and type **`/ghosteditor`** to set up your locations and the hunter NPC.

{% hint style="info" %}
The default locations in `config.lua` use example coordinates. Rebuild them in the [Location editor](/rayn-scripts-docs/rayn_ghosthunting/location-editor.md) or check them with `/ghostpos`.
{% endhint %}

## Updating from an older version

If you used the earlier `ghosthunt` resource, remove it from `resources/` and `server.cfg`. Running both creates two NPCs and two sets of blips in the same place.


---

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