> 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/commands-and-keys.md).

# Commands and keys

Every command and key binding of the Weapon Hub on one page.

## Commands

| Command           | Who    | What it does                                                                              |
| ----------------- | ------ | ----------------------------------------------------------------------------------------- |
| `/weaponhub`      | Admins | Opens the hub where you stand, with no job, item or fee rules                             |
| `/weaponhub_here` | Admins | Copies a ready-made `config/locations.lua` entry for where you stand (also printed in F8) |

Admins are players with the ace `vision_weaponhub.admin` or one of `Config.Admin.groups`. Set `Config.Admin.commands = false` to remove both commands.

## At the workbench

| Key   | Action                                                                   |
| ----- | ------------------------------------------------------------------------ |
| **E** | Use the bench (only with the `[E]` prompt, when no target resource runs) |

With ox\_target or qb-target, use your target key on the bench instead.

## Inside the hub

| Key                    | Action                                                                                |
| ---------------------- | ------------------------------------------------------------------------------------- |
| **Left mouse** (drag)  | Rotate the weapon                                                                     |
| **Mouse wheel**        | Zoom                                                                                  |
| **A / D** or **← / →** | Turn the weapon left / right                                                          |
| **W / S** or **↑ / ↓** | Tilt the weapon up / down                                                             |
| **+** / **-**          | Zoom in / out                                                                         |
| **R**                  | Reset the view                                                                        |
| **Escape**             | Close a dialog, stop a preview, then leave the hub (asks first if changes are staged) |

{% hint style="info" %}
The pause menu and the weapon wheel are disabled while the hub is open. The hub closes by itself on death, ragdoll, entering a vehicle or walking further than `Config.MaxDistance` from the bench.
{% endhint %}

## Inventory

| Action        | Where                                                                                                                                                  |
| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Customize** | Right-click menu of every gun in ox\_inventory, once the button is installed (see [Installation](/visionstore-docs/scripts/weaponhub/installation.md)) |


---

# 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/commands-and-keys.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.