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

# Tints and camo colours

Weapon tints, your own palettes, MK II camo colours and their prices in config/colors.lua.

Everything on this page is in `config/colors.lua`. Two kinds of colour are offered:

| Kind            | What it colours                                                | Tab in the hub                  |
| --------------- | -------------------------------------------------------------- | ------------------------------- |
| **Tint**        | The whole weapon. Normal weapons have 8, MK II weapons 32      | Tint                            |
| **Camo colour** | The colour of an MK II camo or slide camo pattern (32 colours) | Camo Colour (in the Finish tab) |

## Tints

```lua
Config.Tints = {
    enabled = true,
    price = 0,                  -- default price of a tint change (0 = free)
    account = 'cash',           -- 'cash' | 'bank'
}
```

| Option    | Default  | Meaning                        |
| --------- | -------- | ------------------------------ |
| `enabled` | `true`   | `false`: no tints in the hub   |
| `price`   | `0`      | Default price of a tint change |
| `account` | `'cash'` | `'cash'` or `'bank'`           |

GTA has two tint sets, and the hub picks the right one from the game data:

| Palette    | Colours                                                   | Weapons             |
| ---------- | --------------------------------------------------------- | ------------------- |
| `standard` | 8: Black, Green, Gold, Pink, Army, LSPD, Orange, Platinum | Every normal weapon |
| `mk2`      | 32: Classic, Contrast, Bold and Metallic colours          | Every MK II weapon  |

Every colour is one line in `Config.TintPalettes`:

```lua
standard = {
    { index = 0, label = 'Black', color = '#2b2d2f' },
    { index = 1, label = 'Green', color = '#4b5d3a' },
    { index = 2, label = 'Gold', color = '#c9a24a' },
    -- ...
},
```

| Field   | Meaning                                                            |
| ------- | ------------------------------------------------------------------ |
| `index` | The colour number GTA uses. Don't change it on base-game weapons   |
| `label` | The name players see. Rename freely                                |
| `color` | The swatch on the button (the weapon always shows the real colour) |
| `price` | Optional: this colour costs this much instead of the default       |

Remove a line to stop offering that colour. The tint is saved on the weapon (`metadata.tint`) and ox\_inventory applies it whenever the gun is drawn.

## Your own palettes

Add-on weapons often ship more tints than GTA's 8 or 32, or different ones. Describe them in a palette and point the weapon at it:

```lua
Config.TintPalettes.chrome = {
    { index = 0, label = 'Black', color = '#151515' },
    { index = 1, label = 'Mirror Chrome', color = '#d9dde2', price = 25000 },
    { index = 2, label = 'Rose Gold', color = '#e0a890', price = 15000 },
}

Config.WeaponTints = {
    WEAPON_MYRIFLE = 'chrome',
}
```

You can also set it in the weapon's entry in `config/weapons.lua`: `tints = 'chrome'`.

A palette can be reused by any number of weapons. It can also replace the GTA one on a base-game weapon, for example to offer only four tints on duty weapons:

```lua
Config.TintPalettes.duty = {
    { index = 0, label = 'Black', color = '#2b2d2f' },
    { index = 4, label = 'Army', color = '#7b7356' },
    { index = 5, label = 'LSPD', color = '#2f3e5c' },
    { index = 7, label = 'Platinum', color = '#b9bcc0' },
}
Config.WeaponTints = { WEAPON_CARBINERIFLE = 'duty', WEAPON_PUMPSHOTGUN = 'duty' }
```

{% hint style="info" %}
Colours the weapon model doesn't have (an index above its tint count) are left out automatically in game.
{% endhint %}

## MK II camo colours

MK II weapons can wear a camo (Digital, Brushstroke, Woodland, Skull, Sessanta Nove, Perseus, Leopard, Zebra, Geometric, Boom!, Patriotic), and the MK II pistols a slide camo. GTA lets you pick the **colour** of that camo.

The hub shows a **Camo Colour** grid in the Finish tab of every weapon with a camo slot. The colour shows on the 3D preview as soon as a camo is staged or fitted, and is saved on the weapon (`metadata.liveryColor`). The hub paints it onto the camo every time the gun is drawn, including camos fitted later through the ox\_inventory menu.

```lua
Config.Livery = {
    enabled = true,
    price = 0,
    account = 'cash',
    colors = {
        { index = 0, label = 'Gray', color = '#8a8d90' },
        { index = 1, label = 'Dark Gray', color = '#4a4c4f' },
        { index = 2, label = 'Black', color = '#1c1d1f' },
        -- ... 32 colours in total ...
        { index = 31, label = 'Dark Green', color = '#25502f' },
    },
}
```

| Option    | Default               | Meaning                                                                   |
| --------- | --------------------- | ------------------------------------------------------------------------- |
| `enabled` | `true`                | `false`: no Camo Colour grid                                              |
| `price`   | `0`                   | Default price of a camo colour change                                     |
| `account` | `'cash'`              | `'cash'` or `'bank'`                                                      |
| `colors`  | 32 GTA livery colours | Same fields as tints. Remove lines, rename them, or price them one by one |

## Prices

* **Per change:** `Config.Tints.price` and `Config.Livery.price` are charged when a save changes the tint or the camo colour. Applying the same colour again is free.
* **Per colour:** `price` on a colour line overrides the default, for example 0 for the basics and 25,000 for chrome.
* **Accounts:** `'cash'` or `'bank'`, per setting. On ESX, cash is the `money` account. On ox\_core and standalone servers, cash is the ox\_inventory `money` item.

Paid colours carry a small dot in the grid and their price next to the name. The total of all fees (bench fee, tint, camo colour) is shown above **Apply Changes** before the player pays. Payment is taken before anything changes and refunded if the save fails.

## Colour names in other languages

Labels in `config/colors.lua` are shown as written. To translate them per language, add keys to `locales/<lang>.json`:

```json
"tint_standard_2": "دهبي",
"tint_mk2_23": "دهبي ميتاليك",
"tint_chrome_1": "كروم مرايا",
"livery_13": "أحمر"
```

Use `tint_<palette>_<index>` for tints and `livery_<index>` for camo colours. `locales/ar.json` already has every GTA colour in Egyptian Arabic.


---

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