> 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/guides/using-the-hub.md).

# Using the hub

Everything a player needs to know to customize a weapon at a workbench.

{% hint style="info" %}
This page is written for **players**. Feel free to link it in your server's Discord.
{% endhint %}

## Opening the hub

* Find a **Weapon Workshop** on the map and use the bench (target, or **E** at the `[E]` prompt).
* If your server installed it, right-click a gun in your inventory and choose **Customize**. Away from a bench, you get a waypoint to the nearest one.

Some benches are for one job only, need a tool in your pockets, or charge a fee. If you can't use one, a notification tells you why.

## Pick a weapon

**Select Weapon** lists the guns in your inventory that the hub can work on. Your gun swings in front of you in a lit studio.

* **Drag** to rotate it, **scroll** to zoom, **Reset view** to centre it again.
* Callouts on the weapon point at every attachment slot and follow it as it turns.
* The panel shows its stats: damage, fire rate, accuracy, range, capacity, magazine size and weight.

## Fit parts

Each tab is one kind of part: **Optics**, **Muzzle**, **Barrel**, **Underbarrel**, **Magazine**, **Stock**, **Flashlight & Laser** and **Finish**. Only the tabs your weapon has are shown.

| Card state       | Meaning                                               |
| ---------------- | ----------------------------------------------------- |
| **Equipped**     | Fitted on the weapon now                              |
| **Available**    | You own the item. Press **Install**                   |
| **Not owned**    | You can preview it, but you need the item to fit it   |
| **Incompatible** | This weapon can't take it                             |
| **Factory**      | The part GTA fits by itself. **Restore** puts it back |

1. Click a part to **preview** it on the model. The stats show what would change.
2. Press **Install** to stage it, or **Remove** to stage taking a fitted part off.
3. Parts that share a slot replace each other.

Nothing is used up yet. Every staged change is listed under **Changes**, with what it **uses from inventory** and what **returns to inventory**. Press **Undo** to take back a staged part, or **Reset** to drop all changes.

## Colours

* **Tint** colours the whole weapon: 8 colours on normal weapons, 32 on MK II weapons.
* **Camo Colour** (in the Finish tab, MK II weapons) colours a fitted camo or slide camo. It shows once a camo is fitted or staged.

Paid colours carry a small dot and their price next to the name.

## Apply

Press **Apply Changes**. The total of any fees is shown above the button before you pay.

* Fitted parts are taken from your inventory.
* Removed parts go back into your inventory (unless your server destroys them, which the hub warns about).
* If anything fails, for example your inventory is full or you can't afford it, **nothing changes** and your money and items are untouched.

Close the hub and draw the gun: your changes are on it, and they stay on it.

{% hint style="warning" %}
**Stay at the bench.** Walking away, getting in a vehicle, ragdolling or dying closes the hub. Changes you haven't applied are dropped.
{% endhint %}

## Leaving

Press **Escape** or the close button. With changes still staged, you're asked whether to **Discard** them or **Keep editing**.

## Issued equipment

Some departments mark the guns and parts they hand out. An **Issued equipment** weapon can only be changed by its department. Removed issued parts stay issued.


---

# 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/guides/using-the-hub.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.