> For the complete documentation index, see [llms.txt](https://docs.privalo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.privalo.dev/scripts/essentials/dj/config.md).

# CONFIG

#### 2.1 Framework y comandos

| Clave                        | Por defecto     | Descripción                                       |
| ---------------------------- | --------------- | ------------------------------------------------- |
| `PVConfig.Framework`         | `'auto'`        | `auto` \| `qbx` \| `qb` \| `esx` \| `standalone`  |
| `PVConfig.Locale`            | `'es'`          | Archivo `locales/<x>.json`                        |
| `PVConfig.AdminCommand`      | `'djadmin'`     | Comando del panel admin                           |
| `PVConfig.PlayerCommand`     | `nil`           | Si defines `'dj'`, `/dj` abre la mesa más cercana |
| `PVConfig.AdminAce`          | `'pv_dj.admin'` | ACE requerido para `/djadmin`                     |
| `PVConfig.AutoGrantAdminAce` | `true`          | Auto-otorga `group.admin` → `pv_dj.admin`         |

#### 2.2 Audio y límites

| Clave                      | Por defecto | Descripción                             |
| -------------------------- | ----------- | --------------------------------------- |
| `PVConfig.DefaultRadius`   | `30.0`      | Radio (m) por mesa si no se especifica  |
| `PVConfig.MaxRadius`       | `120.0`     | Máximo permitido (evita mesas gigantes) |
| `PVConfig.MaxPlaylistSize` | `40`        | Canciones máximas por mesa              |
| `PVConfig.MaxFxPads`       | `12`        | Slots FX (visual/lógica)                |
| `PVConfig.UseTarget`       | `true`      | Habilita ox\_target sobre las mesas     |
| `PVConfig.UseEKey`         | `true`      | Habilita prompt con E                   |
| `PVConfig.EKeyDistance`    | `1.8`       | Distancia máxima para el prompt E       |

#### 2.3 Mesas (`PVConfig.Stations`)

Se pueden definir **desde config** (permanentes) o **desde `/djadmin`** en vivo (guardadas en DB). Las de config no se pueden borrar desde el juego.

```lua
{
    id      = 'palace',                       -- slug único
    label   = 'DJ Palace',                    -- nombre visible
    coords  = vec3(353.30, 204.34, 98.08),
    heading = 305.0,
    radius  = 35.0,                           -- m
    public  = false,                          -- true = cualquiera abre
    jobs    = { 'dj', 'palace', 'admin' },    -- solo si public=false
    blip    = true,
    lights  = { enabled = true, color = { 255, 122, 98 } },
}
```

#### 2.4 FX Pads iniciales

Si la tabla `pv_dj_fx` está vacía al iniciar, se **sembrará** con lo que haya en `PVConfig.FxPads`. Luego, los admins los editan desde `/djadmin`.

```lua
PVConfig.FxPads = {
    { label = 'Air Horn', url = 'https://.../air-horn.mp3' },
    { label = 'Applause', url = 'https://.../applause.mp3' },
}
```

#### 2.5 URLs permitidas

Por seguridad, sólo se aceptan URLs de dominios en `PVConfig.AllowedDomains` o extensiones en `PVConfig.AllowedExtensions`. Ajusta a tu gusto.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.privalo.dev/scripts/essentials/dj/config.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.