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

# Theme colours

Recolour the Weapon Hub interface from config/theme.lua.

Match the hub to your server's brand. The colours are in `config/theme.lua` and are applied when the hub opens: no rebuild of the interface is needed.

The defaults are the Vision palette: warm cream text on near-black panels with a crimson accent.

```lua
Config.Theme = {
    accent = '#c4122f',         -- buttons, selected tabs and cards, rings
    accentHover = '#e01c3c',    -- primary button on hover
    accentText = '#ef5b6c',     -- accent coloured text (lighter than accent so it stays readable)
    ok = '#c7d7b0',             -- "equipped" marks and success messages
    warn = '#d9a55a',           -- issued-equipment marks and warnings
    text = '#e7dbbe',           -- main text
    dim = '#a69e8d',            -- secondary text
    faint = '#7d7566',          -- hints and disabled text
    panel = '#111214',          -- panel background (drawn at 92 % opacity)
    card = '#19191b',           -- attachment cards
    control = '#202022',        -- buttons and inputs
}
```

| Key           | Default   | Used for                                                                 |
| ------------- | --------- | ------------------------------------------------------------------------ |
| `accent`      | `#c4122f` | Buttons, selected tabs and cards, rings                                  |
| `accentHover` | `#e01c3c` | Primary button on hover                                                  |
| `accentText`  | `#ef5b6c` | Accent-coloured text. Keep it lighter than `accent` so it stays readable |
| `ok`          | `#c7d7b0` | "Equipped" marks, success messages                                       |
| `warn`        | `#d9a55a` | Issued-equipment marks, warnings                                         |
| `text`        | `#e7dbbe` | Main text                                                                |
| `dim`         | `#a69e8d` | Secondary text                                                           |
| `faint`       | `#7d7566` | Hints and disabled text                                                  |
| `panel`       | `#111214` | Panel background (drawn at 92 % opacity)                                 |
| `card`        | `#19191b` | Attachment cards                                                         |
| `control`     | `#202022` | Buttons and inputs                                                       |

## Example: blue

```lua
Config.Theme = {
    accent = '#1f6feb',
    accentHover = '#388bfd',
    accentText = '#79b8ff',
    ok = '#a5d6a7',
    warn = '#f0b35a',
    text = '#e6edf3',
    dim = '#9aa7b4',
    faint = '#6e7b88',
    panel = '#0d1117',
    card = '#161b22',
    control = '#21262d',
}
```

{% hint style="success" %}
Use hex colours only (`'#rrggbb'`). Your server name in the footer is set by `Config.UI.ServerName` in `config/config.lua` (see [General settings](/visionstore-docs/scripts/weaponhub/configuration/general.md#sound-and-interface)).
{% endhint %}


---

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