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

# Changelog

Every release of Vision Weapon Hub.

## 1.0.0

*First release.*

* **3D workbench** for ox\_inventory: the real weapon model in a lit studio, live preview of every part, callouts that follow the model, staged changes applied in one save.
* **Every base-game weapon (95) and attachment (414 parts)** built in, generated from the GTA files: optics, suppressors, muzzle brakes, grips, flashlights, barrels, clips and drums, MK II special ammunition, finishes, MK II camos and pistol slides, knuckle-duster variants.
* **22 ox\_inventory items** for every base-game part ox\_inventory has no item for, and **92 icons**.
* **Tints** with renamable, priced palettes, and custom palettes for add-on weapons.
* **MK II camo colours** (32 livery colours), saved on the weapon and applied on every draw.
* **Add-on weapons** in `config/weapons.lua`, and `tools/addon-to-config.js` to write those entries from a pack's `.meta` files and list parts that still need an item.
* **Workbenches** with job / grade rules, required items, open or per-change fees, blips and props. `/weaponhub` and `/weaponhub_here` for admins. Optional "Customize" button in ox\_inventory.
* **Issued equipment** rule, with metadata kept on issued parts.
* **Frameworks:** Qbox, QBCore, ESX, ox\_core and standalone. **Targets:** ox\_target, qb-target or an ox\_lib prompt.
* **Languages:** English and Egyptian Arabic.
* **Developer API:** exports `OpenHub` and `IsCustomizing`, event `vision_weaponhub:saved`.

{% hint style="info" %}
**Updating?** Back up `config/`, `locales/`, `bridge/` and `stage/`, replace the folder, then copy your changes back.
{% 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/changelog.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.