# Overview

This guide shows where each VibesEZ-Race setting lives so you can change behavior safely without breaking startup or race flow.

## Before You Start

* VibesEZ-Race installed and starting without Lua errors.
* Access to edit files in `config/`.
* Access to restart resources from your server console.

## Configuration File Map

* `config/main.lua`: default merge helper.
* `config/shared.lua`: framework bridge, database table aliases, permissions, admin system, daily rewards, phasing.
* `config/racing.lua`: race logic, anti-cheat, cache tuning, tracker, visual behavior, crew competition timing.
* `config/seasons.lua`: rank tiers, season points, season rewards, season rotation.
* `config/ui.lua`: race setup defaults, HUD defaults, ranking view limits, UI safety caps.
* `config/chat.lua`: chat channels, moderation, rate limits, quick chat.

## Apply A Production Baseline

1. Open `config/shared.lua`.
2. Set `Framework`.
3. Set `Bridge` resource names.
4. Set `AdminSystem.MasterAdmins`.
5. Confirm `DatabaseTables` matches physical table names from `install/racing.sql`.
6. Open `config/ui.lua`.
7. Set `UI.raceSetup` defaults.
8. Open `config/seasons.lua`.
9. Set `Seasons` defaults.
10. Open `config/racing.lua`.
11. Set `Performance` values.
12. Set `Racing.antiCheat` values.
13. Restart the `VibesEZ-Race` resource.

## Verify

1. Restart the `VibesEZ-Race` resource.
2. Join the server with a test account.
3. Open the laptop racing app.
4. Create and run one test race.
5. Check the console for callback or SQL errors.

> **Note:** Restart the resource after every config change set, even when you only changed one key.

## See Also

* [Shared Config](/vibesez/docs/configuration/shared-config.md)
* [Race Config](/vibesez/docs/configuration/race-config.md)
* [Season Config](/vibesez/docs/configuration/season-config.md)
* [UI Config](/vibesez/docs/configuration/ui-config.md)
* [Chat Config](/vibesez/docs/configuration/chat-config.md)


---

# Agent Instructions: 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:

```
GET https://vibesez.gitbook.io/vibesez/docs/configuration/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.