> For the complete documentation index, see [llms.txt](https://rqver-resources.gitbook.io/rq-dogs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rqver-resources.gitbook.io/rq-dogs/script-configuration/vehicle-configuration.md).

# Vehicle Configuration

## Shared.Vehicles

Vehicles that can be used by Police Dog's must be added to the configuration file. \
Each vehicle requires the following options:\
\- `model`: The spawncode of the vehicle you are configuring\
\- `doors`: A list of doors to open when the dog exits/enters a vehicle. Options: `'trunk'` (With Quotes), `0` (Without quotes - Left Front Door), `1` (Without quotes - Right Front Door), `2` (Without quotes - Left Rear Door), `3` (Without quotes - Right Rear Door), `4` (Without quotes - Hood/Bonnet)\
\- `seat`: The seat ID that the dog should be placed in. Options: `-1` (Drivers Seat), `0` (Passenger Seat), `1` (Back Seat Drivers Side), `2` (Back Seat Passenger Side).\
\
You can also optionally add a `secondarySeat` parameter. This takes the same seat ID's as the above option, and is used if the primary seat is occupied.

```lua
Shared.Vehicles = {
    {
        model = "spawncode", -- Vehicle Model/Spawncode
        doors = { 'trunk' }, -- A list of doors to open on that vehicle as the dog gets in/out. Leave empty to not open any doors. Options are "trunk" (in quotes), 0 - Left front door, 1 - Right Front Door, 2 - Left Rear Door , 3 - Right Rear Door, 4 - Hood (All numbers should NOT be in quotes)
        seat = 1, -- The seat ID the dog should get into. Drivers Seat: -1, Passenger Seat: 0, Back Drivers Side: 1, Back Passengers Side: 2
        secondarySeat = 2 -- The seat ID of the dog should get into if the primary seat is occupied. This option is OPTIONAL and can be removed from the config without issue.
    }
}
```

\ <br>


---

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

```
GET https://rqver-resources.gitbook.io/rq-dogs/script-configuration/vehicle-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.