Scripts That Read qb-core's Player State
QBCore is the framework most FiveM roleplay servers grow up on, and the reason is the ecosystem: shared player state, a job and gang system every resource can read, and an item table the whole server agrees on. Everything in this collection is written against that contract.
Scripts in this category
37 products
What makes a script a QBCore script
Any Lua resource will run on a QBCore server. What makes something a QBCore script is that it reads and writes the framework's state instead of inventing its own. In practice that means four hooks:
- Player data.
QBCore.Functions.GetPlayerfor identity, money, metadata and licences, so a payout lands in the same wallet the rest of your city uses. - Jobs and grades. Gating an interaction behind
PlayerData.job.nameand a grade level, so your police whitelist actually applies. - Items. Registering with
qb-inventoryorox_inventoryso the thing a player just looted is a real item they can drop, sell or lose. - Targeting. Exposing interactions through
qb-targetorox_targetrather than a proximity key press, so the interaction obeys the same rules as everything else on the map.
A resource that skips those and stores state in its own table will work in a showcase video and drift out of sync the first time a player relogs.
Jobs, crime and the economy in between
A roleplay economy needs both directions of money flow. The legal side is jobs, whether a delivery run, a restaurant shift or a mechanic bay, and the value of a job script is not the payout but the reason to be somewhere with other people. The illegal side is robberies, drug production and laundering, and its value is risk: something that can be interrupted, reported and lost. The collection covers both, plus the laundering and selling loops that connect them.
Compatibility, and the words that hide problems
"QBCore compatible" covers a wide range. Ask which QBCore: current qb-core on the Cfx.re release line behaves differently from a two-year-old fork, and inventory is the usual break point, because qb-inventory, ox_inventory and ps-inventory do not share an item schema. Every product page here states the framework and dependency list before you buy, and the dependency list is the part worth reading twice.
Adding scripts without destabilising a live server
Add one resource per restart. Watch resmon for the new resource specifically rather than just the server total, and give it a full population cycle before adding the next. When something breaks after installing three at once, you have three suspects and no way to narrow them down. Every order here is delivered by email within minutes, so there is no reason to rush the install.
Frequently asked questions
Will QBCore scripts run on Qbox?
Usually, and often with no changes, because Qbox keeps QBCore compatibility deliberately so resources transfer. The exceptions are scripts that call internal qb-core functions directly rather than going through the exported API. Each product page lists the frameworks that specific script supports.
Which inventory do these scripts expect?
It varies by creator. ox_inventory and qb-inventory are the two common targets and they do not share an item schema, so check the dependency list on the product page before buying and match it to what your server already runs.
Do I need qb-target or ox_target?
For most interaction-based scripts, yes, one target resource or the other. They are free, open resources rather than paid dependencies, and most servers already run one.
How do I add items a script needs to my inventory?
Paid scripts ship the item definitions and any images in the download, along with the SQL for jobs or gangs where needed. You paste the item block into your inventory's shared items file and drop the images into its image directory.