9 min read
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.
This is the central resource hub. Use the grouped reference below for upstream resources, compare inventories for replacement and migration decisions, or download the framework for a reproducible qb-core snapshot and txAdmin setup.
If you are installing an unfamiliar resource, review its fxmanifest.lua and Lua file references
with the Compatibility Analyzer, then compare its findings
against the exact upstream resource version. The tool does not run Lua or certify compatibility.
Character login and spawn setup
Follow the actual player-onboarding chain rather than configuring character slots and spawn locations in the wrong resource:
- qb-core loads and persists the player.
- qb-multicharacter controls character slots, login and the transition to spawning.
- qb-spawn reads
QB.Spawnsto display public spawn locations. - qb-apartments and qb-clothing supply the installed housing and appearance flows.
If players get stuck between these steps, use the multicharacter loading checklist before changing SQL or registering additional login events.
Customization guides
For visual changes, follow the qb-target redesign guide or qb-inventory reskin workflow without replacing gameplay logic. Use Pleb Masters Forge for model lookup when configuring vehicles, doors, NPCs or props.
Core integrations
- qb-core — framework object, player lifecycle, and shared data
- qb-menu — action menus
- qb-input — form dialogs
- progressbar — cancellable progress UI
- qb-radio — pma-voice radio integration
- qb-cityhall — licenses and job applications
- 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
- qb-minigames - NUI skill checks used as a dependency by other resources
- qb-interior - interior shell spawning exports
- qb-loading - loadscreen shown while players join
- qb-scoreboard - player count, duty count, and activity state
Gameplay resources
- qb-ambulancejob — medical job workflow
- qb-apartments — starter housing
- qb-banking — accounts and transactions
- qb-crafting — recipes, benches and reputation; review server-side safety before deployment
- qb-crypto - the qbit currency, price movement, and transfers
- qb-clothing — character clothing integration
- qb-diving — diving activity
- qb-drugs — drug gameplay resources
- qb-fitbit — upstream status, retained item/metadata context, and migration notes
- qb-houses — player housing
- qb-inventory — inventories, shops, and stashes
- qb-mechanicjob — mechanic job
- qb-multicharacter — character selection
- qb-phone — phone applications
- qb-policejob — police job
- qb-shops — shops and stock
- qb-spawn — spawn selection
- qb-prison — jail and prison flows
- qb-weed — persistent plant growth
- qb-streetraces — street races
- qb-lapraces - persistent lap race tracks and leaderboards
- 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
- qb-vehicleshop — vehicle dealership
- qb-vehiclesales - player to player used car lot
- qb-weapons — weapon durability and repair
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.
- qb-busjob - bus route job with NPC passengers
- qb-garbagejob - randomized garbage routes with a truck deposit
- qb-hotdogjob - hot dog stand with a reputation track
- qb-recyclejob - recycling plant and the material price list
- qb-towjob - flatbed towing with a deposit and shift payout
- qb-vineyard - grape, juice, and wine production chain
- qb-newsjob - reporter equipment and liveried van
- qb-pawnshop - buys stolen goods and melts jewellery
- qb-scrapyard - rotating wanted vehicle list for materials
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.
- qb-bankrobbery - Fleeca, Paleto, Pacific Standard, power stations
- qb-storerobbery - convenience store registers and safes
- qb-houserobbery - scripted house interiors and furniture searches
- qb-jewelery - jewelry store display cases, note the repository spelling
- qb-truckrobbery - armored truck mission with an activation fee
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 still lists qb-fitbit, but no repository of that name exists in either
current QBCore GitHub organization. The qb-fitbit status page documents
that upstream gap, the remaining core item/metadata context, and a safe migration workflow without
inventing exports or events.
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.
Upstream downloads by task
These repositories belong to the upstream QBCore organization. This is a task-based starting list, not a popularity ranking or a promise that every resource works with every fork. Read the license, manifest and setup instructions at the revision you choose.
| Server task | Upstream source / download | Setup and API reference |
|---|---|---|
| Inventory, stashes and shops | qb-inventory | QBCore inventory setup and exports |
| Character selection | qb-multicharacter | qb-multicharacter configuration |
| Spawn selection | qb-spawn | qb-spawn setup |
| Player and vehicle HUD | qb-hud | QBCore HUD configuration |
| Police job | qb-policejob | qb-policejob configuration |
| Mechanic job | qb-mechanicjob | qb-mechanicjob setup |
| Banking and accounts | qb-banking | qb-banking integration |
| Clothing | qb-clothing | qb-clothing configuration |
| Phone applications | qb-phone | qb-phone setup |
| Weapon durability and repair | qb-weapons | qb-weapons configuration |
| Garage and impound storage | qb-garages | qb-garages setup |
| Target interactions | qb-target | qb-target zones and exports |
Sources at a glance
| Source | Type | Review boundary |
|---|---|---|
| QBCore upstream repositories | Upstream | Pin each resource and inspect its manifest |
| GitHub QBCore projects | Community | Source access alone does not establish compatibility |
| RPScripts | Commercial | Review dependencies, license and support terms independently |
Evaluate third-party open-source resources
Open-source projects can be useful when you need behavior outside the official resource set. Before adopting one:
- inspect
fxmanifest.luafor dependencies and load requirements, - search for direct database access and assumptions about QBCore tables,
- identify the QBCore exports, callbacks and events it consumes,
- review recent commits, issues and release notes,
- pin the revision you tested instead of deploying an unbounded moving branch,
- run the resource on staging with your actual inventory, target, UI and database stack.
The qbcore GitHub topic is a discovery surface, not a
compatibility registry. Treat every repository as unverified until you inspect it.
Compatibility checklist
Use the same checklist for free and paid resources.
Framework API
- Does the resource call documented QBCore exports/events or reach into
qb-coreinternals? - Does it expect a specific
qb-coreversion or a legacy API? - Does it modify core files instead of using supported extension points?
Dependencies
Record every required resource, including:
- database connector,
- inventory,
- target/interactions,
- menu/UI library,
- phone,
- dispatch,
- banking,
- housing or garage integrations.
A resource can support QBCore while still being incompatible with the rest of your selected stack.
Persistent data
Check whether the resource:
- adds SQL migrations,
- reads or writes QBCore-owned tables directly,
- stores identifiers that must survive a migration,
- assumes a particular item/job/gang schema.
Back up files and the database together before schema changes.
Source and update model
Record whether the deployed code is:
- official upstream,
- third-party open source,
- escrow/encrypted,
- partially open,
- pinned to a release or commit.
Source access affects how you debug and migrate a resource, but it does not by itself prove quality.
Staging acceptance
Do not stop at "the resource starts without errors." Test the complete workflows it changes, such as reconnects, restarts, failed purchases, inventory capacity, job changes, character switching and permission denials.
For rollout planning, see updating customized resources safely.
Commercial alternatives
Commercial discovery is intentionally secondary on qbcore.net. If the official or open-source ecosystem does not meet the requirement, a marketplace can be another source to evaluate.
RPScripts is the portfolio's commercial FiveM marketplace; its QBCore scripts category is the relevant starting point, and its server templates page compares complete pre-configured servers. Check each product's declared framework support, dependencies, source/escrow model, update history and support terms. A paid listing is not independent proof that it works with your server.
RPScripts and qbcore.net are operated by the same owner. Start with the upstream options above when you need inspectable source code; compare a commercial product only against a specific unmet requirement.
Installation workflow
For any selected resource:
- read its upstream installation instructions,
- install required dependencies first,
- place the resource in the intended resource group,
- apply reviewed migrations to a staging database,
- set load order explicitly where dependencies require it,
- restart and test complete user journeys,
- monitor logs and resource performance before production rollout.
See the QBCore scripting guide and resource load-order troubleshooting for the technical workflow.
Resource alternatives
Compare inventory systems, browse the HUD overview, or review resource purchasing checks. Upstream downloads above come first; third-party and commercial resources need their own source, dependency and license review.
Frequently asked questions
Are official QBCore resources free?
The QBCore core and official repositories linked above are open source. Check each repository's license and current upstream documentation before redistribution or modification.
Where can I find free QBCore scripts?
Start with the official QBCore organization, then inspect community releases on GitHub and Cfx.re. "Free" describes price, not compatibility or maintenance status.
Will every QBCore resource work on Qbox?
No universal guarantee is justified. Qbox documents a QB compatibility bridge for resources that use supported QBCore interfaces, but direct database access, private core-file access and unsupported API usage can break compatibility. See QBCore vs Qbox before planning a migration.
How do I install a QBCore script?
Follow the resource's own instructions first. In general, install dependencies, add the resource, apply any reviewed data migration, ensure the correct load order, and test on staging before production.
Found an issue in this guide?
Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.
