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

# Installation

1. Download the resource (escrow edition from your [Keymaster](https://keymaster.fivem.net), open source edition from your Tebex purchase) and put the `daddy-carcrafting` folder in your `resources` folder. Do not rename it.
2. Add the items to your inventory, see [Items](/daddy-studios-docs/scripts/daddy-carcrafting/items.md).
3. Start it after its dependencies in `server.cfg`:

```cfg
ensure oxmysql
ensure ox_lib
ensure qbx_core          # or qb-core / es_extended
ensure ox_inventory      # your inventory
ensure ox_target         # or qb-target
ensure daddy-carcrafting
```

4. Restart the server. The console shows:

```
[daddy-carcrafting] framework: qbx | inventory: ox
[daddy-carcrafting] started
```

The database tables are created on the first start. `install/schema.sql` is only needed when your database user is not allowed to create tables.

{% hint style="info" %}
`location.json` and `recipes.json` are checked on every start. A mistake prints a `CONFIG ERROR` line that names the station or recipe, and the resource stops there.
{% endhint %}

## Where the station is

One station is set up out of the box. To move it or add more, see [Stations](/daddy-studios-docs/scripts/daddy-carcrafting/stations.md).

## Detection

`config.lua` detects the framework, the inventory and the target script by itself. Set `Config.Framework`, `Config.Inventory` or `Config.Target` only if you run a renamed or forked resource.


---

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