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

# FAQ

Quick answers to the questions we get the most.

<details>

<summary>Does it work with ESX / QBCore / Qbox / standalone?</summary>

Yes. Qbox, QBCore and ESX are detected automatically, and standalone works too. The framework bridge is open source, so you can add any other framework (see [Bridges](/visionstore-docs/scripts/crafting/developers/bridges.md)).

</details>

<details>

<summary>Does it work with qb-inventory or another inventory?</summary>

**ox\_inventory is required.** Bench items carry their own id in item metadata, and bench stashes are ox\_inventory stashes. The inventory code is open source in `bridge/inventory/ox_inventory.lua` if your developer wants to port it.

</details>

<details>

<summary>Is it secure? Can cheaters craft for free?</summary>

The client only ever sends a recipe id and a quantity. Ingredients, levels, timers, distances and results are all checked on the server, crafts run on the server's clock, and every action is rate-limited.

</details>

<details>

<summary>What happens to crafts during a restart?</summary>

Nothing is lost. The queue is saved in the database and crafts keep running on the server's clock. Players claim them when they come back.

</details>

<details>

<summary>If a player picks up their bench and gives it to a friend, what does the friend get?</summary>

The **same** bench: its level, XP, condition and stash all travel with it.

</details>

<details>

<summary>Can benches be placed inside houses?</summary>

Yes. Benches placed inside an interior only exist there. Any housing script that uses routing buckets works, and rtx\_housing is supported out of the box.

</details>

<details>

<summary>Can I use benches that are part of my MLO?</summary>

Yes. Give the bench type `model = 'none'` and add it to `Config.StaticBenches`. Only the screen is drawn, no prop is spawned. See [Static benches](/visionstore-docs/scripts/crafting/configuration/benches.md#static-benches).

</details>

<details>

<summary>Can I make a bench only for police / a gang?</summary>

Yes, with `access` rules on the bench type (jobs with grades, gangs, ACE or identifiers). See [Who may use a bench](/visionstore-docs/scripts/crafting/configuration/benches.md#who-may-use-a-bench).

</details>

<details>

<summary>Can I turn off the systems I don't want?</summary>

Yes. Crafting Mastery, wear and maintenance, the bench stash and the hidden NPCs each have their own `enabled = false`. Bench levels can be ignored with `Config.Crafting.disableBenchLevels = true`.

</details>

<details>

<summary>Do I need object_gizmo or ox_target?</summary>

No. The default "ghost" placement needs nothing extra. object\_gizmo is only for the optional drag-and-drop mode, and ox\_target is only needed for the hidden NPC vendors.

</details>

<details>

<summary>Can I change the texts or translate it?</summary>

Yes. Every text is in `config/locales/`. English and Arabic are included. See [Languages](/visionstore-docs/scripts/crafting/configuration.md#languages).

</details>

<details>

<summary>Can I rename the resource folder?</summary>

We recommend keeping `Chapo_Crafting`. If you rename it, update the `server.export` on every bench item and any `exports.Chapo_Crafting` calls in your own scripts.

</details>


---

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