> 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/weaponhub/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, ESX and ox\_core are detected automatically. Standalone works too: money comes from the ox\_inventory `money` item and jobs from aces.

</details>

<details>

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

No. ox\_inventory is required: attachments are ox\_inventory items, and installed parts, tints and camo colours are stored in ox\_inventory's weapon metadata.

</details>

<details>

<summary>Do I need to configure every GTA weapon?</summary>

No. All 95 base-game weapons and their 414 parts are built in. You only configure add-on weapons.

</details>

<details>

<summary>Does it work with add-on weapon packs?</summary>

Yes. Run the included helper on the pack and paste the output into `config/weapons.lua`, or write a few lines by hand. See [Add-on weapons](/visionstore-docs/scripts/weaponhub/guides/add-on-weapons.md).

</details>

<details>

<summary>Do players lose their parts if something goes wrong?</summary>

No. Saves are all or nothing: if anything fails (inventory full, not enough money, the weapon moved), items, weapon metadata and fees are rolled back.

</details>

<details>

<summary>Will my existing attachments still work?</summary>

Yes. The hub saves parts in ox\_inventory's own format (`metadata.components`), the same way ox\_inventory's "attach" does, so other scripts keep working. Parts it doesn't know are never touched.

</details>

<details>

<summary>Is it secure? Can cheaters fit parts they don't own?</summary>

Every request is checked on the server: distance, ownership, compatibility, money and rate limits. Players can preview parts they don't own (`Config.AllowUnownedPreview`), but fitting always needs the item.

</details>

<details>

<summary>Does it use resources while nobody is at a bench?</summary>

No. There are no loops while idle: the hub costs nothing until a bench is opened.

</details>

<details>

<summary>Can I charge money for customizing?</summary>

Yes. Benches can charge per save or on open, and every tint and camo colour can have its own price. See [Workbenches](/visionstore-docs/scripts/weaponhub/configuration/workbenches.md#fees) and [Prices](/visionstore-docs/scripts/weaponhub/configuration/colors.md#prices).

</details>

<details>

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

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

</details>

<details>

<summary>Can I change the colours to match my server?</summary>

Yes: [Theme colours](/visionstore-docs/scripts/weaponhub/configuration/theme.md). You can also put your own studio photo behind the weapon ([3D preview and studio](/visionstore-docs/scripts/weaponhub/configuration/preview-and-stage.md#use-your-own-photo)).

</details>

<details>

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

We recommend keeping `vision_weaponhub`. The exports (`exports.vision_weaponhub`), the event names and the default admin ace use it.

</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/weaponhub/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.