> For the complete documentation index, see [llms.txt](https://daddy-studios.gitbook.io/daddy-studios-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-carcrafting/items.md).

# Items

The default recipes use 13 items. The `install` folder has them ready for every inventory:

| Inventory                                | File                             | Where it goes                            |
| ---------------------------------------- | -------------------------------- | ---------------------------------------- |
| ox\_inventory                            | `install/ox_inventory_items.lua` | paste into `ox_inventory/data/items.lua` |
| qb-inventory, ps-inventory, lj-inventory | `install/qb_items.lua`           | paste into `qb-core/shared/items.lua`    |
| ESX default inventory                    | `install/esx_items.sql`          | run on your database                     |

| Item                 | Label                | Used for                              |
| -------------------- | -------------------- | ------------------------------------- |
| `car_chassis`        | Vehicle Chassis      | every car                             |
| `car_engine`         | Engine Block         | every car                             |
| `car_sparkplugs`     | Spark Plug Set       | every vehicle                         |
| `car_battery`        | Car Battery          | every vehicle                         |
| `car_door`           | Car Door             | cars, one per door                    |
| `car_wheel`          | Car Wheel            | cars, four per car                    |
| `bike_frame`         | Motorcycle Frame     | motorcycles                           |
| `bike_engine`        | Motorcycle Engine    | motorcycles                           |
| `bike_wheel`         | Motorcycle Wheel     | motorcycles, two per bike             |
| `crafting_toolkit`   | Workshop Toolkit     | must be in the inventory, not used up |
| `blueprint_jester`   | Blueprint: Jester    | Dinka Jester                          |
| `blueprint_sultanrs` | Blueprint: Sultan RS | Karin Sultan RS                       |
| `blueprint_bati`     | Blueprint: Bati 801  | Pegassi Bati 801                      |

## Item images

`install/images` has a 256x256 PNG for every item. Copy them into your inventory's image folder:

* ox\_inventory: `ox_inventory/web/images`
* qb-inventory, ps-inventory, lj-inventory: `<inventory>/html/images`

![The item images](https://2487709298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqcEXX242M9YYHjASblGi%2Fuploads%2Fgit-blob-44f2bded04908dfd9954daeb985a0a8164c22773%2Fdaddy-carcrafting-items.png?alt=media)

{% hint style="info" %}
If the crafting screen shows no images, set `Config.ItemImagePath`, for example `'nui://ox_inventory/web/images/%s.png'`.
{% endhint %}

You can use any of your own items instead: change the `materials` of the recipes in `recipes.json`, see [Recipes](/daddy-studios-docs/scripts/daddy-carcrafting/recipes.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://daddy-studios.gitbook.io/daddy-studios-docs/scripts/daddy-carcrafting/items.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.