# configuration

All configuration lives in `config.lua` at the root of the resource.

***

## Target System

```lua
Config.TargetType = 'qb-target' -- 'qb-target' | 'ox_target'
Config.TargetResource = 'qb-target' -- exact resource name on your server
```

* `TargetType` — the interaction library you use. Accepted values: `'qb-target'` or `'ox_target'`.
* `TargetResource` — the *exact* resource name as it appears in your `server.cfg`. This is important if you have renamed the resource.

***

## Vehicle Keys

```lua
Config.VehicleKeys = 'qb-vehiclekeys' -- Supported: 'qb-vehiclekeys', 'qs-vehiclekeys' -- Set to false to disable key handoff entirely
```

* When set to `false`, no keys will be issued on vehicle spawn.
* When the configured resource is not started, key handoff is silently skipped.
* Any resource that exposes a `GiveKeys(plate)` export will also work through the generic fallback.

***

## Fuel System

```lua
Config.FuelSystem = 'LegacyFuel' -- Supported: 'LegacyFuel', 'ps-fuel', 'lj-fuel', 'cdn-fuel', 'qb-fuel', 'ox_fuel' -- Set to false to disable
```

* Vehicles always spawn at **100%** fuel.
* When set to `false` or when the resource is not running, the script falls back to GTA's native `SetVehicleFuelLevel`.
* Any resource that exposes a `SetFuel(vehicle, amount)` export will also work through the generic fallback.

***

## Locations

Garage locations are defined in the `Config.Locations` table, indexed by sequential integers. See the **Location Structure** page for full field documentation.

```lua
Config.Locations = { [1] = { ... }, [2] = { ... }, -- add as many as needed }
```


---

# 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://mohssins.gitbook.io/mohscriptsdocs/moh-jobgarage/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.