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

# Troubleshooting

**The console says "no supported framework found".** Start `daddy-carcrafting` after `qbx_core`, `qb-core` or `es_extended` in `server.cfg`.

**The console shows a `CONFIG ERROR`.** The line names the station or recipe and the field that is wrong, for example a missing `partsPed` or a recipe step that depends on a step that does not exist. Fix it in `location.json` / `recipes.json` and restart.

**There is no option to open the workbench.** `ox_target` or `qb-target` must run. The client console prints a warning when none is found.

**Item images are missing on the screen.** Copy `install/images/*.png` into your inventory's image folder, or set `Config.ItemImagePath`.

**A vehicle shows the placeholder picture.** Only base game vehicles have a picture online. Add `web/dist/vehicles/<model>.png` for add-on vehicles.

**The finished vehicle has no keys.** Your key script is not one of the built-in ones. Add its "give key" call to `Vehicles.giveKeys` (server) or `Vehicles.giveKeysClient` (client) in `bridge/vehicles.lua`.

**The vehicle does not appear at the delivery point.** Every delivery point is blocked by another vehicle. The player gets a message and the vehicle spawns as soon as a spot is free. Add more `deliveryPoints` to the station.

**A build is stuck after a crash.** Builds are saved and continue after a restart. If one is stuck anyway, run `/carcraft_cancel <station id> refund`.

**I want to turn on logs.** Set `Config.Debug = true` and send us the `[daddy-carcrafting:debug]` lines from both consoles.


---

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