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

# Configuration

***

**Configuration**

All configuration lives in `config.lua`.

**Full Config**

lua

```lua
Config.LobbyLocation = vector3(-90.16, -2103.68, 16.72)

Config.MaxBet = 50000
Config.MinBet = 0

Config.JoinRadius = 30.0

Config.Countdown = 5

-- Payment type: 'money' (cash), 'bank', or an item name like 'black_money'
Config.MoneyType = 'money'

Config.KartSpawns = {
    team1 = { coords = vector4(-90.16, -2103.68, 16.72, 106.04), model = 'veto',  label = 'TEAM 1' },
    team2 = { coords = vector4(-88.76, -2105.88, 16.72, 105.8),  model = 'veto2', label = 'TEAM 2' }
}

Config.Checkpoints = {
    vector3(-99.28,  -2106.88, 16.72),
    vector3(-140.12, -2146.24, 16.72),
    vector3(-30.68,  -2102.24, 16.72),
    vector3(-98.04,  -2072.08, 17.48),
    vector3(-73.56,  -2020.04, 18.0),
    vector3(-79.6,   -1995.76, 18.0),
    vector3(-116.2,  -2043.8,  17.72)
}

Config.Laps = 1

Config.RaceTimeout = 600

Config.CheckpointRadius = 4.0
```

**Options**

| Option             | Description                                                                          |
| ------------------ | ------------------------------------------------------------------------------------ |
| `LobbyLocation`    | Coordinates of the go kart lobby marker                                              |
| `MaxBet`           | Maximum bet amount players can place                                                 |
| `MinBet`           | Minimum bet amount — set to `0` to allow free races                                  |
| `JoinRadius`       | Distance in metres a player must be within to join the lobby                         |
| `Countdown`        | Seconds before the race starts after all players ready up                            |
| `MoneyType`        | Payment type — `money` for cash, `bank` for bank, or an item name like `black_money` |
| `Laps`             | Number of laps per race                                                              |
| `RaceTimeout`      | How long in seconds before the race automatically ends                               |
| `CheckpointRadius` | How close a player needs to be to trigger a checkpoint                               |

**Kart Spawns**

| Team  | Model | Label  |
| ----- | ----- | ------ |
| team1 | veto  | TEAM 1 |
| team2 | veto2 | TEAM 2 |

You can change the kart models and spawn coordinates to any location on the map. Make sure both teams have valid spawn points set.

**Checkpoints**

Checkpoints are defined as a list of `vector3` coordinates in `Config.Checkpoints`. Players must pass through each checkpoint in order to complete a lap. You can add, remove, or reposition checkpoints to create a custom race track anywhere on the map.


---

# 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://quannsstudios.gitbook.io/quannsstudio-docs/gokart-racing/configuration.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.
