A heist engine with a live in-game editor, profiles and run tracking for Qbox.
Overview#
| Data-driven heists | A heist is one Lua table: sites, points, doors, props, guards, zones, ordered steps and actions. Other resources register it with the engine, so there is no engine code to edit. |
| Server-side checks | The server checks distance, items, weapon, busy state, cooldowns and police count for every step, rolls luck and loot, and pays rewards. The client only plays the minigame. |
| Live editor | /heisteditor edits a running heist, with item pickers, minigame previews, position capture and a gizmo for props and points. |
| Profiles | Save named snapshots of a heist, load one, or let a random profile from a pool go live on each restart. |
| Live controls | Switch a heist off, change its cooldowns, see every site's cooldown and active run, end a run or clear a cooldown. |
| Persistent cooldowns | Site cooldowns and pity counters are kept in resource KVP and survive restarts. There is no database. |
| Late joiners | Run state is published through GlobalState with secret values removed, so a player who joins mid-run sees the current state. |
| Cleanup | Doors, tablet heist slots, guards and scene props are released when a run ends or the resource stops. |
| Optional integrations | ox_doorlock, ps-dispatch, glitch-criminaltablet, glitch-xpSystem, glitch-crafting, glitch-economy, glitch-minigames and others, each checked at run time. |
This resource is the engine. It ships no heists of its own. Heists come from separate resources that register a definition with it. Until one is installed, /heisteditor opens with an empty list.
Availability#
Coming soon. Installation and API documentation are available now; purchase and download links will be added when the package is released.
Stuck on a step?Ask in the Discord →