> For the complete documentation index, see [llms.txt](https://docs.cuxial.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cuxial.com/scripts/gangs/cuxial-gang.md).

# Cuxial Gang

Organizations and gangs for FiveM: boss menu, tablet, territory, activities and a staff panel.

Cuxial Gang gives your server criminal organizations with their own headquarters, ranks, money and territory. Staff create and manage everything from an in-game panel; bosses run their organization from a boss menu and members follow it from a tablet.

## What it does

* **Organizations created by staff**, of type gang or cartel, each with its colour, headquarters points, ranks and member limits.
* **Boss menu**: members and invitations, ranks with permissions, clean and dirty money, upgrades, vehicles, season pass, arsenal, mules and an activity log.
* **Tablet** for members: ranking, map, dark chat, season pass, missions and mules.
* **Headquarters services**: shared stash and extra stashes, cloakroom with saved outfits, garage, port and helipad, clandestine medic and a money laundering route.
* **Territory**: fixed capture zones, turf zones drawn by staff, loyalty, wars between organizations and zone control decided by sales.
* **Street activities**: drug selling with a burner phone, graffiti, racketeering points, cartel supply points, favelas to conquer and timed airdrops.
* **Mules network**: outsiders recruited by an organization who take contracts for it.
* **Interaction menu** on nearby players (handcuff, escort, search, bag, vehicle) and control of NPC hostages.
* **Police raids** on headquarters, with job, schedule and cooldown limits. Disabled by default.
* **Staff panel** to create organizations and edit locations, vehicle catalogue, prices, zones, rewards and airdrops without touching files.
* **Discord logs** for player and staff actions, and live refresh of every open window.

See the [Features guide](/scripts/gangs/cuxial-gang/features.md) for how each part is used in game.

## Requirements

| Resource                | Required | Used for                                                      |
| ----------------------- | -------- | ------------------------------------------------------------- |
| OneSync                 | Yes      | Server-side position and entity checks                        |
| `ox_lib`                | Yes      | Callbacks, commands, key bindings, locales                    |
| `oxmysql`               | Yes      | All persistent data                                           |
| `cuxial_bridge`         | Yes      | Connects to your framework, inventory and target              |
| `ox_inventory`          | Yes      | Stashes, player search, items, clean and dirty money as items |
| `cuxial_police`         | No       | Dispatch alerts, on-duty police count, intelligence feed      |
| `cuxial_garages`        | No       | Vehicle keys and impounding stored vehicles in a raid         |
| `cuxial_medical`        | No       | Revive at the clandestine medic                               |
| `cuxial_appearance`     | No       | Saving and applying cloakroom outfits                         |
| `nextgenfivem_crafting` | No       | Arsenal and favela crafting benches                           |
| `lb-phone`              | No       | Phone notifications and mail, and the companion phone app     |

{% hint style="warning" %}
Cuxial Gang requires **QBox** or **QBCore**. Organizations are registered as gangs in the framework and their vehicles are stored in the `player_vehicles` table.
{% endhint %}

{% hint style="info" %}
Integrations marked "No" are detected when they are running. Each one adds what the table says; without it, that part stays off and the rest keeps working.
{% endhint %}

## Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Installation</strong></td><td>Dependencies, items, convars, permissions and start order.</td><td><a href="/scripts/gangs/cuxial-gang/installation.md">Installation</a></td></tr><tr><td><strong>Features guide</strong></td><td>How the panels, territory and activities work in game.</td><td><a href="/scripts/gangs/cuxial-gang/features.md">Features guide</a></td></tr><tr><td><strong>Configuration</strong></td><td>Every option in <code>shared/config.lua</code> and the files in <code>data/</code>.</td><td><a href="/scripts/gangs/cuxial-gang/configuration.md">Configuration</a></td></tr><tr><td><strong>Commands &#x26; permissions</strong></td><td>Staff and player commands, keys and rank permissions.</td><td><a href="/scripts/gangs/cuxial-gang/commands.md">Commands &amp; permissions</a></td></tr><tr><td><strong>Exports &#x26; events</strong></td><td>Read organizations and reward them from your own resources.</td><td><a href="/scripts/gangs/cuxial-gang/developers.md">Exports &amp; events</a></td></tr><tr><td><strong>Troubleshooting</strong></td><td>Common problems and how to fix them.</td><td><a href="/scripts/gangs/cuxial-gang/troubleshooting.md">Troubleshooting</a></td></tr></tbody></table>


---

# 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://docs.cuxial.com/scripts/gangs/cuxial-gang.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.