Skip to Content
ResourcesAll QBCore Resources: Guides, Config & Common Fixes

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

Gameplay resources

Jobs

These pay out money or items too. Three of them accept a price or reward argument from the client at the pinned commit, which each page describes in its own words: qb-hotdogjob, qb-pawnshop, and qb-towjob. So does qb-vehiclesales, listed above. The server-authority checklist is the review to run against any of them before deployment.

Robberies and heists

Each of these grants items or money, so read the server-side validation notes on the individual pages before deploying them, alongside the server-authority checklist.

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.

The official documentation also still lists qb-fitbit, but no repository of that name exists in either the qbcore-fivem or the qbcore-framework GitHub organization, and no redirect is served. Without a reachable manifest there is no commit to pin, so this site publishes no setup or API page for it. Treat any third-party copy as an unverified community resource.

Safe deployment

  1. Start with the QBCore GitHub organizationΒ  and record a commit SHA.
  2. Read fxmanifest.lua, README, config, SQL, exports, and event handlers at that commit.
  3. Confirm dependency order and compare local modifications before updating.
  4. Back up persistent data, deploy to staging, and run feature-specific smoke tests.
  5. Keep the previous code and schema rollback procedure until production verification is complete.