Documentation
Install Robberies Creator on your FiveM server: requirements, server.cfg load order, automatic database setup, granting admin access and the in-game settings panel.
Before installing Robberies Creator, make sure your server meets the requirements. Four resources are mandatory; the rest of your stack — framework, target, inventory and dispatch — is detected on its own.
Requirement | Status | Notes |
|---|---|---|
| Required | Database access. The tables install themselves. |
| Required |
Callbacks, progress bars and skill checks. |
| Required | The laser grids used by the security nodes. |
| Required | Lockpick, thermite, pin cracker, roof running, chopping and word memory hacks. |
Framework | Required |
|
Inventory | Recommended | 14 inventories supported. Fills the item picker and handles item rewards and checks. |
Target | Optional |
|
Dispatch | Optional | Six police dispatch systems supported. Without one, a built-in alert with a blip and a route is sent to officers. |
Everything framework- or third-party-specific sits behind a small, editable bridge file, and the resource picks the right one by looking at what is already running:
Layer | Detection order |
|---|---|
Framework |
|
Target |
|
Inventory |
|
Dispatch |
|
Doors need nothing at all: they run on GTA's own door system, so no doorlock resource is required or used. Integrations has the details and how to pin one by hand.
After purchasing Robberies Creator, the resource is automatically linked to your CFX Portal account.
Sign in to the CFX Portal using the same account used during checkout, open Granted Assets, and download Robberies Creator.
After extracting the download, you should have the following folder:
qs-robberies-creator/
├── config/ -- main.lua: language, command, permissions, detection
├── client/custom/ -- bridges: framework, target, dispatch, progress bar (editable)
├── server/custom/ -- bridges: framework, inventory, dispatch, custom nodes (editable)
├── shared/ -- settings schema and helpers (editable)
├── locales/ -- 20 languages
├── web/build/ -- the interface, already built
└── CHANGELOG.mdKeep the folder named
qs-robberies-creator. The interface and every event are tied to that name, so a renamed copy opens a blank creator.
Move the qs-robberies-creator folder into your server's resources directory. It can live anywhere inside it, including a category folder:
resources/
└── [qs]/
└── qs-robberies-creator/Once copied, open your server.cfg and make sure every dependency — and everything it should detect — starts before Robberies Creator:
ensure oxmysql
ensure ox_lib
ensure mka-lasers
ensure minigames
# Framework
ensure es_extended
# ensure qb-core
# ensure qbx_core
# Inventory, target, dispatch
ensure ox_inventory
ensure ox_target
ensure qs-dispatch
ensure qs-robberies-creatorThe loading order matters. Detection only picks a resource that is started. If one is installed but still booting, the script waits up to ten seconds for it; after that, that layer falls back to standalone for the whole session.
There is no SQL file to import. Robberies Creator creates its own tables a second after it first starts, and upgrades them on later versions by itself.
Table | Holds |
|---|---|
| Every robbery you build: its name, category, whether it is enabled, who created it, and its whole node graph. |
| One row per attempt: the leader, success or failure, the money earned and how long it took. |
| Active cooldowns — global, per player or per job — so they survive a restart. |
| The values changed in the in-game settings panel. Only what you changed is stored. |
Deleting a robbery also deletes its statistics and its cooldowns. A fresh server starts with an empty list: load one of the six ready-made templates from the creator to get a working heist in seconds.
The creator is where robberies are built and the server is configured, so it is behind an admin check. A player is an admin when they hold one of the admin aces or belong to one of the admin groups:
The recommended route. The accepted aces are admin, command, group.admin and qbox.admin. Add one of them for your identifier in server.cfg:
add_ace identifier.license:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx admin allow
# or put yourself in the admin group
add_principal identifier.license:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx group.adminRestart the server after adding it.
Automatic. A player whose framework group — or job name — is admin, superadmin or god is accepted. On ESX this is the usual xPlayer group.
Once you are in, the accepted groups and aces are edited live in /robberiesconfig → Permissions — add mod, owner or your own staff ace there. A list left empty falls back to the defaults, so nobody can lock every admin out.
Not getting in? When somebody is refused, the server console prints their identifiers, the aces and groups it checked, and the exact add_ace line that would let them in.
Almost nothing is configured in files. Language, number formatting, permissions, police jobs, cooldown persistence and the command names all live in the in-game settings panel (/robberiesconfig), changed live and stored in the database. Everything about a robbery itself — police required, cooldowns, crew size, rewards — is a node in the creator.
Panel section | Settings |
|---|---|
General | Language (20 available), debug logging, number locale, currency or plain number style, the currency symbol, and muting the interface's click sounds. |
Gameplay | Whether robbery cooldowns survive a restart. |
Permissions | Admin groups, admin aces, and the extra ace that opens only the settings panel ( |
Police | The jobs that receive dispatch alerts, picked from your framework's real job list. |
Commands | The names of the creator, settings and development-mode commands. These need a resource restart. |
The only file is config/main.lua, for plumbing and first-boot defaults:
Config.Language = 'en' -- default language until changed in the panel
Config.Intl = { locales = 'en-US', options = { style = 'currency', currency = 'USD' } }
Config.Debug = false -- ships as true: turn it off for production
Config.Command = 'robberiescreator' -- the creator's command
Config.PersistCooldowns = true -- keep cooldowns across restarts
Config.NotificationSounds = nil -- nil = built-in sounds, false = muteA value saved in the panel always beats the file. Admin groups, admin aces and police jobs in particular should be edited in the panel — that is where they are read from. Framework, target, inventory and dispatch are the exception: they are detected at boot and pinned only in
config/main.lua.
Restart your server and read the console. About a second after start, one line says what was picked for each layer:
[qs-robberies] detected: framework=esx target=ox_target inventory=ox dispatch=qs-dispatchstandalone means it found nothing for that layer — if you do have that resource, move it above ensure qs-robberies-creator. Then join your server and work through the first loop:
/robberiescreator opens on the Statistics screen. Go to Robbery Creator.
Press Templates, pick Store Robbery, give it a name and a category and press Save. It is live immediately — the start peds appear at the store.
In Robberies, press Test Start on the card. The robbery starts where you stand, police and cooldown checks are skipped, and no cooldown is set. Type /robberiesdev first to let every minigame pass on its own while you test. Creating a Robbery covers building your own.
Nothing needs a restart from here on. Every robbery, setting and permission is edited in game, and a saved robbery reloads on its own.