> For the complete documentation index, see [llms.txt](https://visionstore.gitbook.io/visionstore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visionstore.gitbook.io/visionstore-docs/scripts/boxing-creator/configuration/general.md).

# General

Language, debug, admin commands, events, ring defaults and world interaction.

## Language and debug

```lua
Config.Locale = 'en'   -- any file in locales/ ('en', 'ar', or your own)
Config.Debug = false   -- prints every counted hit to the server console
```

## Admin

```lua
Config.Admin = {
    Command = 'boxingcreator',     -- opens the ring creator
    StopCommand = 'boxingstop',    -- /boxingstop [ringId]: ends a fight as a no contest
    EventCommand = 'boxingevent',  -- run the ring you stand at as an admin event
    Principal = 'group.admin',     -- who gets the commands
}
```

Admin rights are checked **on the server** for every request, through the ACE `command.<Command>`. To give a staff group access:

```properties
add_ace group.mod command.boxingcreator allow
```

## Admin events

```lua
Config.Event = {
    Radius = 15.0,    -- players this close to the admin can be put in a corner
    MaxListed = 24,   -- how many nearby players the admin panel lists
}
```

## Ring defaults

New rings start with these values. Every ring can change them in the creator.

```lua
Config.RingDefaults = {
    size = { x = 3.2, y = 3.2 },  -- half width / half length inside the ropes (metres)
    blip = true,
    rules = {
        gloves = 'optional',   -- 'optional' (fighters choose) | 'required' | 'off' (bare knuckle)
        bets = true,           -- spectators may bet
        purse = true,          -- fighters may put up a purse
        maxPurse = 50000,
        maxRounds = 5,
    },
}
```

## World interaction

```lua
Config.Interact = {
    Key = 38,              -- E (GTA control id)
    KeyLabel = 'E',        -- shown on the prompt
    Distance = 1.8,        -- metres from the join point to open the menu
    MarkerDistance = 18.0, -- the join marker shows from this far
}

Config.Blip = { Sprite = 311, Colour = 1, Scale = 0.8 }

Config.Spectate = { Radius = 40.0 }  -- players this close get the fight HUD, crowd and bell
```

{% hint style="info" %}
Need a list of GTA control ids or blip sprites? See the [FiveM controls](https://docs.fivem.net/docs/game-references/controls/) and [blips](https://docs.fivem.net/docs/game-references/blips/) references.
{% endhint %}


---

# 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://visionstore.gitbook.io/visionstore-docs/scripts/boxing-creator/configuration/general.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.