Jobs
Duty toggle, grades, blips, bosses, garages, menus and payouts.
QBCore script generator
Build jobs, shops, items, commands, stashes, events and configs with the right QBCore structure before you touch your live server.
Duty toggle, grades, blips, bosses, garages, menus and payouts.
Usable items, metadata, shop stock, prices and inventory checks.
Server validation, cooldowns, permissions, logging and abuse prevention.
A useful QBCore response should make the file boundaries obvious. For many resources that means fxmanifest.lua, config.lua, client logic and server logic, plus any item, SQL or dependency notes your stack needs. Keep framework-specific calls in the right layer rather than mixing unrelated exports from different inventories or menu systems.
Targets, menus, animations, key input and visual feedback belong on the client. The client can request an action but should not award money or inventory.
Validate jobs, items, locations, cooldowns, permissions and rewards on the server using the installed QBCore and inventory APIs.
Keep item names, prices, locations, job grades and tunable values in configuration so balancing changes do not require rewriting core logic.
Run generated resources on a development server first. Try missing dependencies, wrong item names, invalid job grades, repeated network events, two players using the same interaction and resource restarts. Watch both client and server consoles, then bring the exact error back for a focused fix.
Useful next guides: QBCore drug system architecture, QBCore + ox_inventory setup, and QBCore script not starting.
Open the app with the QBCore prompt ready, then upgrade when you need bigger scripts and more usage.