> 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/recipes.md).

# Recipes

Build plans are in `recipes.json`. Restart the resource after editing it.

```json
{
  "id": "jester",
  "label": "Dinka Jester",
  "model": "jester",
  "category": "sports",
  "access": { "mode": "public_blueprint", "minLevel": 3, "blueprintItem": "blueprint_jester", "consumeBlueprint": true },
  "result": { "mode": "chance", "baseChance": 90 },
  "xpReward": 160,
  "materials": [
    { "item": "car_chassis", "count": 1, "consume": true },
    { "item": "crafting_toolkit", "count": 1, "consume": false }
  ],
  "graph": [ ... ]
}
```

| Field                     | What it does                                                                                   |
| ------------------------- | ---------------------------------------------------------------------------------------------- |
| `id`                      | Unique name of the plan                                                                        |
| `label`                   | Name on the screen                                                                             |
| `model`                   | Spawn name of the vehicle                                                                      |
| `category`                | One of the `categories` at the top of the file                                                 |
| `access.mode`             | `public`, or `public_blueprint` (needs `blueprintItem`)                                        |
| `access.minLevel`         | Crafting level needed                                                                          |
| `access.consumeBlueprint` | `false` keeps the blueprint after the build                                                    |
| `result.mode`             | `guaranteed_quality`, or `chance` with `baseChance` (1-100). A failed roll loses the materials |
| `xpReward`                | XP for the owner, helpers get a share (`Config.HelperXpShare`)                                 |
| `materials`               | Items taken when the build starts. `consume: false` only checks that the player has it         |
| `graph`                   | The assembly steps                                                                             |

## Assembly steps

Each step has a `part` (from `parts`), an optional `bone` (where on the car it goes) and the steps it depends on. Steps unlock when their dependencies are done, and several players can work on unlocked steps at the same time.

Bones: `engine`, `wheel_lf`, `wheel_rf`, `wheel_lr`, `wheel_rr`, `door_dside_f`, `door_pside_f`, `door_dside_r`, `door_pside_r`.

Recipes in the `motorcycles` category skip doors and the right side wheels automatically.

## Parts

`parts` sets each part type: the prop the player carries, the install time in ms and the ox\_lib skill check (`easy`, `medium`, `hard`, or a list for several checks in a row).

## Categories and groups

![Categories on the crafting screen](https://2487709298-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FqcEXX242M9YYHjASblGi%2Fuploads%2Fgit-blob-2b227cb6f0d2da0888dbb99db5ffe3ebf0d6b6cb%2Fdaddy-carcrafting-catalog.jpg?alt=media)

* `categories`: id and label of each category, shown in this order
* `materialGroups`: how materials are grouped in the material list

## Levels and quality

`Config.LevelXp` sets the XP needed for each crafting level. The quality score starts at 100, every failed skill check or cancelled step costs `Config.SkillFailPenalty` points, and `Config.QualityGrades` turns the score into a grade and the health of the delivered vehicle.

## Vehicle images

The screen looks for `web/dist/vehicles/<model>.png` or `.webp` first, then the picture of base game vehicles on docs.fivem.net, then a placeholder. For add-on vehicles, drop a picture named after the model into `web/dist/vehicles/`.


---

# 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/recipes.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.