> For the complete documentation index, see [llms.txt](https://wiki.dough.land/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dough.land/doughdealership/additional-settings.md).

# Additional Settings

### Adding your first (and additional) dealership(s)

* Go into `shared/config.lua` and change the default (“vehicleshop”) details into correct ones
* Most items should be explained within the config itself

```
{ -- DEALERSHIP 1
        name = 'vehicleshop', -- KEEP THIS THE SAME AS THE MAIN JOB ACCESSING THE DEALERSHIP! THIS IS THE SOCIETY & JOB REQUIRED
        label = 'Vehicleshop', -- DEALERSHIP LABEL USED EVERYWHERE WHERE A LABEL IS NEEDED (BLIP ETC.)
        coords = vector3(547.2, -182.06, 54.49), -- COORDS FOR DEALERSHIP MENU + MAP BLIP
        spawn = {coords = vector3(548.4, -198.29, 54.49), heading = 180.0}, -- COORDS WHERE VEHICLE WILL SPAWN WHEN SOLD TO ANOTHER PLAYERR
        showcaseVehicles = { -- SHOWCASE SPOTS (SHOULD SUPPORT A INFINITE AMOUNT! UI WILL PROBABLY BECOME MESSED UP WITH TO MANY, KEEP IT BELOW 6)
            {id = 1, coords = vector3(547.45, -190.61, 54.49), heading = 63.0, model = nil, vehicle = nil}, -- ID = INCREMENTAL VALUE || COORDS = VEHICLE SHOWCASE SPOT || HEADING = VEHICLE HEADING || MODEL = LEAVE THIS NIL || VEHICLE = LEAVE THIS NIL
            {id = 2, coords = vector3(547.9481, -175.6810, 54.0807), heading = 139.0, model = nil, vehicle = nil},
            {id = 3, coords = vector3(544.2737, -181.7314, 54.0809), heading = 33.0, model = nil, vehicle = nil},
            {id = 4, coords = vector3(545.9059, -168.8376, 54.0813), heading = 71.0, model = nil, vehicle = nil},
        },
    },
```

{% hint style="info" %}
See Above as 1 dealership-block, if you wish to add another dealership you simply copy-paste the whole block {}
{% endhint %}

```
{ -- DEALERSHIP 1
        name = 'vehicleshop', -- KEEP THIS THE SAME AS THE MAIN JOB ACCESSING THE DEALERSHIP! THIS IS THE SOCIETY & JOB REQUIRED
        label = 'Vehicleshop', -- DEALERSHIP LABEL USED EVERYWHERE WHERE A LABEL IS NEEDED (BLIP ETC.)
        coords = vector3(547.2, -182.06, 54.49), -- COORDS FOR DEALERSHIP MENU + MAP BLIP
        spawn = {coords = vector3(548.4, -198.29, 54.49), heading = 180.0}, -- COORDS WHERE VEHICLE WILL SPAWN WHEN SOLD TO ANOTHER PLAYERR
        showcaseVehicles = { -- SHOWCASE SPOTS (SHOULD SUPPORT A INFINITE AMOUNT! UI WILL PROBABLY BECOME MESSED UP WITH TO MANY, KEEP IT BELOW 6)
            {id = 1, coords = vector3(547.45, -190.61, 54.49), heading = 63.0, model = nil, vehicle = nil}, -- ID = INCREMENTAL VALUE || COORDS = VEHICLE SHOWCASE SPOT || HEADING = VEHICLE HEADING || MODEL = LEAVE THIS NIL || VEHICLE = LEAVE THIS NIL
            {id = 2, coords = vector3(547.9481, -175.6810, 54.0807), heading = 139.0, model = nil, vehicle = nil},
            {id = 3, coords = vector3(544.2737, -181.7314, 54.0809), heading = 33.0, model = nil, vehicle = nil},
            {id = 4, coords = vector3(545.9059, -168.8376, 54.0813), heading = 71.0, model = nil, vehicle = nil},
        },
},

{ -- DEALERSHIP 2
        name = 'vehicleshop', -- KEEP THIS THE SAME AS THE MAIN JOB ACCESSING THE DEALERSHIP! THIS IS THE SOCIETY & JOB REQUIRED
        label = 'Vehicleshop', -- DEALERSHIP LABEL USED EVERYWHERE WHERE A LABEL IS NEEDED (BLIP ETC.)
        coords = vector3(547.2, -182.06, 54.49), -- COORDS FOR DEALERSHIP MENU + MAP BLIP
        spawn = {coords = vector3(548.4, -198.29, 54.49), heading = 180.0}, -- COORDS WHERE VEHICLE WILL SPAWN WHEN SOLD TO ANOTHER PLAYERR
        showcaseVehicles = { -- SHOWCASE SPOTS (SHOULD SUPPORT A INFINITE AMOUNT! UI WILL PROBABLY BECOME MESSED UP WITH TO MANY, KEEP IT BELOW 6)
            {id = 1, coords = vector3(547.45, -190.61, 54.49), heading = 63.0, model = nil, vehicle = nil}, -- ID = INCREMENTAL VALUE || COORDS = VEHICLE SHOWCASE SPOT || HEADING = VEHICLE HEADING || MODEL = LEAVE THIS NIL || VEHICLE = LEAVE THIS NIL
            {id = 2, coords = vector3(547.9481, -175.6810, 54.0807), heading = 139.0, model = nil, vehicle = nil},
            {id = 3, coords = vector3(544.2737, -181.7314, 54.0809), heading = 33.0, model = nil, vehicle = nil},
            {id = 4, coords = vector3(545.9059, -168.8376, 54.0813), heading = 71.0, model = nil, vehicle = nil},
        },
},
```

{% hint style="info" %}
Each dealership you add will require their own society + job setup to function with receiving money
{% endhint %}

* In `dealership_vehicles` create a new entry

```
INSERT INTO `dealership_vehicles` (`dealership`, `data`) VALUES ('vehicleshop', '[]');
```

* In `dealership_shop` you will need to add all vehicles accessible to the shop with their model, name (label), price, category and how many there is available

```
INSERT INTO `dealership_shop` (`dealerships`, `model`, `name`, `price`, `category`, `available`) VALUES ('[{\"name\":\"vehicleshop\"}]', 'adder', 'Adder Label', 1000, 'standard', 100);
```

{% hint style="info" %}
If you wish to make a car accessible to more than 1 dealership, simply change the `dealerships` in `dealership_shop` for that specific vehicle, and update the `[{"name":"vehicleshop"}]` into `[{"name":"vehicleshop"}, {"name":"vehicleshop2"}]`
{% endhint %}


---

# 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://wiki.dough.land/doughdealership/additional-settings.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.