QBCore resource references
This hub links implementation notes to current upstream repositories. A resource name alone does not establish compatibility: record the commit you deploy, inspect its manifest and configuration, and test the whole dependency chain on staging.
Looking for new scripts rather than documentation of official ones? Compare marketplaces and community hubs on our QBCore script sources page.
Core integrations
- qb-target — entity and zone interaction
- qb-adminmenu — administration UI
- qb-management — job and gang employee management
- qb-doorlock — door state and authorization
- qb-vehiclekeys — vehicle keys and locks
- qb-smallresources — collection of small gameplay modules
- qb-radialmenu — contextual action menu
- qb-weathersync — synchronized weather and time
Gameplay resources
- qb-prison — jail and prison flows
- qb-weed — persistent plant growth
- qb-streetraces — street races
- qb-taxijob — taxi job
- qb-truckerjob — trucking job
- qb-fuel — vehicle fuel system
- qb-garages — garage and impound storage
- qb-hud — status HUD and UI setup
Community categories
QBCore does not currently publish official repositories named qb-casino, qb-fishing, or
qb-hunting. Use the casino,
fishing, and hunting selection guides
to evaluate third-party resources without assuming an upstream endorsement.
Safe deployment
- Start with the QBCore GitHub organization and record a commit SHA.
- Read
fxmanifest.lua, README, config, SQL, exports, and event handlers at that commit. - Confirm dependency order and compare local modifications before updating.
- Back up persistent data, deploy to staging, and run feature-specific smoke tests.
- Keep the previous code and schema rollback procedure until production verification is complete.