# Configuration

`msk_bridge` uses configuration files located inside the `data/` folder.

### Configuration Files

* `data/config.lua` — main bridge configuration
* `data/logs.lua` — logs configuration

### Main Configuration

File: `data/config.lua`

```lua
return {
    Framework = 'auto',
    Target = 'auto',
    FloatingNotification = 'msk_interactions',
    ProgressBar = 'auto',
    Fuel = 'auto',
}
```

#### Framework

Defines which framework should be used.

Supported values:

* `auto`
* `prp`
* `qbox`
* `qb`
* `esx`
* `standalone`

When set to `auto`, `msk_bridge` will detect the framework automatically.

> QBOX is checked before QB because some QBOX servers may still use QB-based compatibility resources.

#### Target

Defines which target system should be used.

Supported values:

* `auto`
* `prp_target`
* `ox_target`
* `qtarget`
* `bt-target`
* `standalone`

When set to `auto`, `msk_bridge` will detect the target system automatically.

#### FloatingNotification

Defines which floating notification system should be used.

Supported values:

* `msk_interactions`
* `standalone`

> This option does not use auto-detection.

#### ProgressBar

Defines which progress bar system should be used.

Supported values:

* `auto`
* `msk_progressbar`
* `ox_lib`
* `esx`
* `qb`
* `qs-interface`
* `none`

When set to `auto`, `msk_bridge` will detect the progress bar system automatically.

#### Fuel

Defines which fuel system should be used.

Supported values:

* `auto`
* `ox_fuel`
* `Renewed-Fuel`
* `lc_fuel`
* `cdn-fuel`
* `x-fuel`
* `qs-fuelstations`
* `okokGasStation`
* `rcore_fuel`
* `myFuel`
* `LegacyFuel`
* `msk_fuel`
* `none`

When set to `auto`, `msk_bridge` will detect the fuel system automatically.

### Logs Configuration

File: `data/logs.lua`

This file is used to configure Discord webhooks for supported MSK Scripts logs.

Example:

```lua
return {
    ['scenes'] = 'https://discord.com/api/webhooks/...',
    ['greenzones'] = 'https://discord.com/api/webhooks/...',
    ['plate'] = 'https://discord.com/api/webhooks/...',
    ['keys'] = 'https://discord.com/api/webhooks/...',
    ['impound_police'] = 'https://discord.com/api/webhooks/...',
    ['impound_cash'] = 'https://discord.com/api/webhooks/...',
    ['garage_admin'] = 'https://discord.com/api/webhooks/...',
    ['garage'] = 'https://discord.com/api/webhooks/...',
    ['dialogs'] = 'https://discord.com/api/webhooks/...',
    ['sprays'] = 'https://discord.com/api/webhooks/...',
    ['pausemenu'] = 'https://discord.com/api/webhooks/...',
}
```

#### Available Log Keys

* `scenes`
* `greenzones`
* `plate`
* `keys`
* `impound_police`
* `impound_cash`
* `garage_admin`
* `garage`
* `dialogs`
* `sprays`
* `pausemenu`

Add your Discord webhook URL to each key you want to use.

### Notes

* Most bridge options can be detected automatically
* If a system is detected incorrectly, you can force it manually in `data/config.lua`
* Only add webhook URLs for logs you actually want to use


---

# 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://mskscripts.gitbook.io/mskscripts/general-information/msk_bridge/configuration.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.