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

# Changelog

Every release of Vision Badges Creator.

## 1.0.0

*First release.*

* **Nine badges ready to use**: police, sheriff, state police, federal, EMS, fire, justice, press and a company example, for any job or gang.
* **Badge Studio** (`/badgestudio`, admins): create and edit badges with a live preview, place issuing desks where you stand, search the Registry and revoke badges. Changes reach every player at once, no restart.
* **5 badge shapes** (shield, federal eagle, sheriff star, fire cross, seal), 4 centre symbols, custom logos, 6 metals plus any custom colour, 9 colours per badge.
* **Leather wallet** with the metal badge and a photo ID card. The photo is taken once when the badge is issued and stored with it.
* **Issuing desks** (ox\_target, qb-target or an `[E]` prompt) and `/issuebadge` for admins.
* **Permanent badge numbers** per person, with shared number pools.
* **Validity** shown to viewers: valid, revoked, or inactive when the holder left the job.
* **One shared inventory item** for every badge type (ox\_inventory label / image / tooltip per badge).
* **Frameworks**: Qbox, QBCore, ESX, ox\_core and standalone. **Inventories**: ox\_inventory, qs-inventory, qb-style inventories or none. All auto-detected, with open-source bridges.
* **Languages**: English and Arabic (full right-to-left layout).

{% hint style="info" %}
**Updating?** Back up `config/`, `locales/`, `bridge/` and any logos you added in `web/logos/`, replace the folder, then copy your changes back. Badges, desks and Studio changes in the database are kept.
{% 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/badges/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.