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

# Installation

1. Put the `rayn_dyno` folder into `resources/`.
2. In `server.cfg`, add it **after** `ox_lib` and your framework:

   ```
   ensure ox_lib
   ensure ox_target   # optional
   ensure rayn_dyno

   add_ace group.admin rayn_dyno.admin allow
   ```
3. Restart the server.
4. Join the server as an admin and run `/dynocreator` to set up your first dyno – see [Creator](/rayn-scripts-docs/rayn_dyno/creator.md).

{% hint style="warning" %}
**After the first install, players have to reconnect once** so the game downloads the dyno model. Later, `restart rayn_dyno` works without leaving the game.
{% endhint %}

On the first start, the dynos from `Config.Dynos` in `config.lua` are moved into the creator and the console prints:

```
[rayn_dyno] moved X dyno(s) from config.lua to data/dynos.json
```

{% hint style="info" %}
Dynos are saved to `rayn_dyno/data/dynos.json` – no database is needed. The resource folder must be writable (it is on standard hosting).
{% endhint %}

## Who can use the creator

A player can open `/dynocreator` when any of these is true:

* they have the `rayn_dyno.admin` ACE (`Config.AcePermission`),
* they have the `command` ACE and `Config.AllowCommandAce = true` (usually txAdmin admins),
* their ESX group / QB permission is in `Config.AdminGroups` (on QBX these are checked as ACEs).


---

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