Qbox Scripts

Installing QB-tagged scripts on a Qbox server

This shelf mirrors the QBCore catalog on purpose. Qbox’s qbx_core declares provide ‘qb-core’ in its manifest, so a script that asks for exports[‘qb-core’]:GetCoreObject() gets an answer. What changes is everything around the core. Qbox assumes ox_inventory, ox_target and ox_lib from the first boot, and the notes below are about those three.

Items go in ox_inventory, not qb-core

On Qbox, item definitions live in ox_inventory/data/items.lua and the icons in ox_inventory/web/images. When a listing such as Cocaine Production, Advanced Crafting by Pickle or Metal Detecting hands you a shared/items.lua snippet, convert it to the ox format (label, weight, stack, close, description) and drop the CreateUseableItem call, because ox_inventory wires usable items through the client and server fields of the item definition instead.

Menus, inputs and notifications

A fresh Qbox install has no qb-menu and no qb-input. A script written against them, which is common for 2022-era QB heists and job scripts, either needs those two archived resources added back or a config toggle switched to ox_lib. Most listings here (Pacific Bank Heist, Vehicle Shop V2, the Electus gang and bodyguard scripts) expose that toggle. Search the product page for the word ox_lib before you assume.

Jobs and gangs are defined in qbx_core

Job grades and gang ranks are read from qbx_core/shared/jobs.lua and gangs.lua, not from a database table, so a job script’s SQL file is usually only for its own data: stock, owned businesses, vehicles. Add the job entry by hand, restart qbx_core, then start the script. Door locks go through ox_doorlock, so copy the coordinates from a listing’s qb-doorlock config into an ox_doorlock entry. For the interiors those jobs run in, see the MLO collection; for the plain qb-core builds, the QBCore shelf.