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

# Configuration

Every option in config.lua.

## General

| Option                  | Default           | Description                                          |
| ----------------------- | ----------------- | ---------------------------------------------------- |
| `Config.Framework`      | `'auto'`          | `'auto'`, `'esx'`, `'qb'`, `'qbx'` or `'standalone'` |
| `Config.CreatorCommand` | `'weightcreator'` | Creator command name                                 |
| `Config.AdminGroup`     | `'group.admin'`   | ACE group allowed to use the creator                 |
| `Config.RequireDuty`    | `false`           | Operator must be on duty (QB / Qbox)                 |
| `Config.UseOxInventory` | `true`            | Add trunk + glovebox cargo                           |

The language is set with `setr ox:locale en` (or `pl`) in `server.cfg`.

## Creator lists

```lua
Config.CreatorProps = {
    { label = 'Metal plates', model = 'prop_metal_plates01' },
    -- add your own props here
}

Config.Monitors = {
    { label = 'Flat TV', model = 'prop_tv_flat_01', renderTarget = 'tvscreen' },
}
```

## Weighing

| Option                    | Default | Description                              |
| ------------------------- | ------- | ---------------------------------------- |
| `Config.DefaultRadius`    | `4.0`   | Default weigh point radius               |
| `Config.Trailers`         | `true`  | Weigh trucks together with their trailer |
| `Config.WeighTime`        | `4000`  | Weighing duration (ms)                   |
| `Config.Cooldown`         | `5`     | Seconds between weighings on one station |
| `Config.ComputerRadius`   | `0.6`   | ox\_target radius at the operator spot   |
| `Config.ComputerDistance` | `2.5`   | Max operating distance                   |
| `Config.ResultTime`       | `20`    | Seconds the result stays on the monitor  |
| `Config.LiveDisplay`      | `true`  | Show live weight to everyone             |
| `Config.Webhook`          | `''`    | Discord webhook for weighing logs        |

## Visuals

| Option                   | Default | Description                                     |
| ------------------------ | ------- | ----------------------------------------------- |
| `Config.SpawnDistance`   | `150.0` | Station prop spawn distance                     |
| `Config.DrawDistance`    | `40.0`  | Monitor draw distance                           |
| `Config.ScreenTextScale` | `1.0`   | Monitor text size (0.8 = smaller, 1.2 = bigger) |

## Blip

```lua
Config.Blip = {
    defaultEnabled = true,   -- default state of the checkbox in the creator
    sprite = 477,
    color = 5,
    scale = 0.8,
    display = 4,             -- 4 = map + minimap, 3 = map only, 5 = minimap only
    shortRange = true,
    category = nil,
    useStationName = true,   -- blip name = station name
    label = nil,             -- custom name when useStationName = false
}
```


---

# 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_weightstation/configuration.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.