> For the complete documentation index, see [llms.txt](https://docs.boii.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.boii.dev/fivem-paid-resources/list-inventory/guides/customising-vehicle-inventories.md).

# Customising Vehicle Inventories

Vehicle inventories (trunk + glovebox) are automatically assigned based on vehicle class or model. \
You can override defaults for specific vehicles, or rely on fallback class-based sizes.

***

## Defaults (By Class)

If a specific vehicle model is **not defined**, the system will fall back to these default sizes:

| Class        | Trunk | Glovebox |
| ------------ | ----- | -------- |
| `compact`    | 60    | 4        |
| `sedan`      | 70    | 6        |
| `suv`        | 80    | 6        |
| `coupe`      | 60    | 4        |
| `muscle`     | 70    | 5        |
| `sports`     | 50    | 5        |
| `super`      | 40    | 4        |
| `motorcycle` | 16    | 2        |
| `offroad`    | 90    | 6        |
| `industrial` | 120   | 6        |
| `utility`    | 100   | 6        |
| `van`        | 110   | 6        |
| `service`    | 90    | 6        |
| `emergency`  | 100   | 8        |
| `military`   | 130   | 10       |
| `commercial` | 120   | 8        |

***

## Custom Model Overrides

To override default inventory for a **specific vehicle**, just define it directly by model name:

```lua
adder = {
    trunk = 35,
    glovebox = 10
}
```

This will override both the class defaults and any fallback behavior.

***

## Notes

* All values are **slot-based**, not weight-based.
* Containers are created automatically when you access the vehicle trunk or glovebox.
* Custom sizes allow better balancing for loot-heavy or RP-specific vehicles.
* Do have plans to add in a `trailer` type for vehicles, soon as I get round to it, if people want it.

To modify these, just update `data/vehicles.lua` with new entries or changes.


---

# 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://docs.boii.dev/fivem-paid-resources/list-inventory/guides/customising-vehicle-inventories.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.