> For the complete documentation index, see [llms.txt](https://visionstore.gitbook.io/visionstore-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://visionstore.gitbook.io/visionstore-docs/scripts/crafting/troubleshooting.md).
# Troubleshooting
Fixes for the most common problems.
{% hint style="info" %}
First step, always: look at the **server console** and the player's **F8 console**. Most problems print a clear message there, starting with `[Chapo_Crafting]`. Then run `crafting validate` in the server console.
{% endhint %}
## Startup
"You lack the required entitlement" / the resource won't start
See [Escrow and common errors](/visionstore-docs/getting-started/escrow-and-common-errors.md). The server key must belong to the account that bought the script.
The console says framework: standalone but I use Qbox / QBCore / ESX
The script started before your framework. Move `ensure Chapo_Crafting` **below** your framework in `server.cfg`, or set `Config.Framework` to `'qbox'`, `'qb-core'` or `'esx'` explicitly.
The console lists missing items
Those items don't exist in ox\_inventory. Add them from `install/ox_inventory_items.lua` to `ox_inventory/data/items.lua`, then restart the server. Until then, only the recipes that use them are switched off. Everything else works.
## Benches
Using the bench item does nothing
The item in `ox_inventory/data/items.lua` needs all three of these:
```lua
stack = false,
consume = 0,
server = { export = 'Chapo_Crafting.usePortableBench' },
```
And the resource folder must be named exactly `Chapo_Crafting`.
"Unknown bench type" when using a plain crafting_bench item
The generic `crafting_bench` item doesn't say which bench it is until a bench id is written in it. Give benches with `/crafting give `, or use the per-type items (`tools_crafting_bench`, `medical_crafting_bench`...), which work even when given with `/giveitem`.
The bench is invisible
The prop isn't in your game build. The default bench (`xm3_prop_xm3_bench_04b`) needs build 2944+. Either raise `sv_enforceGameBuild`, or set `model = 'workbench2'` on the bench type in `config/benches.lua`.
I can't pick up a bench
* It still has **running or unclaimed crafts**. Claim or cancel them first (`blockPickupWithActiveCrafts`).
* It's a **static** bench (`Config.StaticBenches`) or was placed with `/crafting place fixed`. Those can never be picked up.
* The bench type has `portable = false`.
Placement is always refused
The preview says why. The usual causes: the ground is steeper than `maxSlope` (12°), the bench overlaps an object or another bench, there's no room to stand at it, or you're inside a no-build zone (`Config.RestrictedZones`). See [Placement](/visionstore-docs/scripts/crafting/configuration/placement.md).
A bench placed inside a house shows up on the street (or vanishes)
Benches belong to the instance they were placed in (the `instance` state bag, then the routing bucket). If your housing script changes the routing bucket without telling the script, wire its door events in `bridge/client.lua`. See [Housing](/visionstore-docs/scripts/crafting/developers/bridges.md#housing).
## Crafting
A recipe doesn't show on the bench
* Run `crafting validate` and read the problems.
* Its `category` must be listed in the bench type's `categories` (and in its `recipes` allow-list, if it has one).
* Every item it uses must exist in ox\_inventory.
* With `hideUnavailableRecipes = true`, recipes above the bench level are hidden.
I edited a recipe but nothing changed
Config files are read on start. Run `restart Chapo_Crafting`. (`crafting reload` only rebuilds from the config already in memory.)
"This workbench is out of service" / crafting is slow
The bench is worn. Open it and use a maintenance kit (**Service Bench**). A dead bench needs the Precision Overhaul Kit. See [Wear and maintenance](/visionstore-docs/scripts/crafting/configuration/condition.md).
Players get very little Mastery XP
That's the anti-farm rules working: short crafts, repeating the same recipe and the daily soft cap all reduce XP. Run `crafting mastery-why ` to see the exact breakdown. Tune it in [Crafting Mastery](/visionstore-docs/scripts/crafting/configuration/mastery.md#anti-farm), or lower `xpScale`.
## Screen and UI
The screen sits in the wrong spot on a custom prop
Stand at the bench, run `/craftingcalibrate`, line it up, press **Enter** and paste the printed block into `config/models.lua`. See [Bench props and the screen](/visionstore-docs/scripts/crafting/configuration/models.md).
The screen is mirrored or upside down
Set `flipU` / `flipV` in `Config.RendererAxis` (or per model in `dui.axis`) in `config/models.lua`.
The screen is blank or broken
Run `/craftingduireload` (staff) to rebuild the bench screens without restarting. `/craftingdui` prints their state to F8.
My HUD stays visible at the bench
The minimap and native HUD are hidden automatically. List your HUD in `Config.Hud.resources`, or edit `Bridge.HideHud` / `Bridge.ShowHud` in `bridge/client.lua`. See [Hiding your HUD](/visionstore-docs/scripts/crafting/configuration/general.md#hiding-your-hud-at-the-bench).
## Permissions and NPCs
I'm not recognised as an admin
Add your group to `Config.Permissions.adminGroups`, or give your group the ACE:
```properties
add_ace group.admin crafting.admin allow
```
Players can't use a job-locked bench / everyone can use it
Per-bench `access` rules only apply when `Config.Permissions.access = 'benchRules'`, or when the bench has `enforce = true`. See [Who may use a bench](/visionstore-docs/scripts/crafting/configuration/benches.md#who-may-use-a-bench).
I can't talk to the hidden NPCs
They need **ox\_target**, started **before** `Chapo_Crafting`. The console warns when ox\_target isn't running. Also check they aren't in police custody (`crafting npcs`).
Still stuck? [Open a ticket on our Discord](https://discord.gg/ZvHtyhyBp4) with your console errors (see [Support](/visionstore-docs/getting-started/support.md) for what to include).
---
# 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://visionstore.gitbook.io/visionstore-docs/scripts/crafting/troubleshooting.md?ask=&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.