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

# FAQ

Quick answers to the questions we get the most.

<details>

<summary>Does it work with ESX / QBCore / ox_core / standalone?</summary>

Yes. Qbox, QBCore, ESX and ox\_core are detected automatically. Standalone works too: jobs then come from aces (see [Bridges](/visionstore-docs/scripts/badges/developers/bridges.md#per-framework-notes)).

</details>

<details>

<summary>Do I need an inventory or a target script?</summary>

No. Without an inventory, badges are kept in the database and shown with `/badge`. Without ox\_target or qb-target, desks use a built-in `[E]` prompt.

</details>

<details>

<summary>Do I need a new inventory item for every badge?</summary>

No. One item, `vision_badge`, carries every badge type. With ox\_inventory each badge even brings its own label, icon and tooltip. Ten icons are included.

</details>

<details>

<summary>Can I make badges for gangs or businesses, not only police?</summary>

Yes, for any job or gang. A mechanic shop badge (`mechanic`) and a press badge are included as examples. Gangs work on Qbox and QBCore.

</details>

<details>

<summary>Do I have to edit files to create a badge?</summary>

No. Admins create badges and desks in game with `/badgestudio`, with a live preview, and every player gets the change at once. Prefer files? `config/badges.lua` works too, and **Copy as Lua** turns a Studio badge into a file entry.

</details>

<details>

<summary>What happens when someone is promoted?</summary>

Issue the badge again. They keep their badge number, the new rank is printed, and the old badge is voided and taken out of their inventory.

</details>

<details>

<summary>What happens when someone is fired?</summary>

Their badge shows **INACTIVE** to everyone automatically. Admins can also revoke it in the Registry, and your job script can call the `RevokeCitizenBadges` export.

</details>

<details>

<summary>Can players fake a badge?</summary>

Every issue is checked on the server (permissions, distance, recipient, photo). The badge shown always comes from the database record, with its live status. A spawned or altered item shows as blank or **UNREGISTERED**.

</details>

<details>

<summary>Can I use my department's logo?</summary>

Yes. Put the image in `web/logos/` and set it on the badge (see [Custom logos](/visionstore-docs/scripts/badges/configuration/designs.md#custom-logos)).

</details>

<details>

<summary>Can I change the texts or translate it?</summary>

Yes. Every text is in `locales/*.lua`. English and Arabic (full right-to-left) are included. See [Languages](/visionstore-docs/scripts/badges/configuration.md#languages).

</details>

<details>

<summary>Can I rename the resource folder?</summary>

No, keep `vision_badges`. The ox\_inventory item calls the export `vision_badges.useBadge`, which uses the folder name.

</details>


---

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