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

# Configuration

Which files you can edit, and where each setting lives.

The core of the script is protected, but everything you might want to change is in **open files**:

```
vision_weaponhub/
├── config/
│   ├── config.lua        ← language, integrations, admins, rules, preview, studio backdrop
│   ├── locations.lua     ← the workbenches
│   ├── weapons.lua       ← add-on weapons, descriptions, calibers, blacklist
│   ├── colors.lua        ← tints, palettes, camo colours and their prices
│   └── theme.lua         ← colours of the interface
├── bridge/
│   ├── framework/server.lua  ← money, jobs, admins, issued equipment, notifications
│   └── target/client.lua     ← ox_target, qb-target or the [E] prompt
├── locales/
│   ├── en.json           ← English texts
│   └── ar.json           ← Egyptian Arabic texts
├── install/              ← ox_inventory items, 92 icons, the "Customize" button
├── stage/                ← the studio backdrop (put your own photo here)
└── tools/
    └── addon-to-config.js  ← writes config entries for add-on weapon packs
```

{% hint style="info" %}
After changing a config file, **restart the resource** (`ensure vision_weaponhub` or `restart vision_weaponhub`). Mistakes in `config/weapons.lua` and `config/colors.lua` are printed in the server console.
{% endhint %}

## Settings by topic

| Page                                                                                            | What's inside                                                                                              |
| ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| [General](/visionstore-docs/scripts/weaponhub/configuration/general.md)                         | Language, debug, framework and target, admins, inventory button, inventory rules, issued equipment, sounds |
| [Workbenches](/visionstore-docs/scripts/weaponhub/configuration/workbenches.md)                 | Bench locations, job rules, required items, fees, blips, props, display spots                              |
| [Weapons](/visionstore-docs/scripts/weaponhub/configuration/weapons.md)                         | Add-on weapons, slots, factory parts, descriptions, calibers, blacklist                                    |
| [Tints and camo colours](/visionstore-docs/scripts/weaponhub/configuration/colors.md)           | Tint palettes, your own palettes, MK II camo colours, prices                                               |
| [3D preview and studio](/visionstore-docs/scripts/weaponhub/configuration/preview-and-stage.md) | Camera, lights, depth of field and the studio backdrop                                                     |
| [Theme colours](/visionstore-docs/scripts/weaponhub/configuration/theme.md)                     | Recolour the interface                                                                                     |

## Languages

Set `Config.Locale` to `'en'` or `'ar'`. To add a language:

1. Copy `locales/en.json` to `locales/<code>.json` (for example `locales/fr.json`).
2. Translate the values (keep the keys and the `%s` placeholders).
3. Set `Config.Locale = 'fr'`.

Missing keys automatically fall back to English. Colour names can be translated too, see [Colour names in other languages](/visionstore-docs/scripts/weaponhub/configuration/colors.md#colour-names-in-other-languages).


---

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