Free Fingerprint Scanner
Free fingerprint prop scanner with a synced two-player UI
This is a browsing view rather than a shelf with an argument. It gathers every resource here that states Qbox support, and each product page says whether that support is native to qbx_core or reached through a compatibility bridge.
Free fingerprint prop scanner with a synced two-player UI
Turns one ATM hack into seven configurable street thefts
Players run their own dealerships and sell cars on pinkslips
Own the pump, set the price, run the missions
Mechanic job, customs bay and NOS in one qb-menu build
Cuff and cable tie arrests that stay at 0.00ms
Ticket flow that lives inside the game, not on Discord
Sold cars keep every mod, from turbo to suspension
Every billiards table on the map becomes playable, fully synced
Four-stage cocaine production on its own handcrafted island
Standalone PIN cracking with configurable attempts and open source
A medic tablet for reports, invoices and evidence photos
Own a laundromat, or break into someone else's
NoPixel-flavoured reskin of illenium-appearance with ox_lib menus
17 lightweight YMAP locations, no more teleporting into shells
Five roles, one bank, one coordinated crew
House break-ins where powder reveals the lasers guarding the safe
A Qbox base that runs your QBCore scripts with zero config
Bahama Mamas club job that ships preconfigured for two MLOs
Declare wars, hold turf, collect tribute from local businesses
Let players tag the map with their own art
Crack an armored truck and choose what you steal
Preset roleplay channels with JSON and Discord message logs
One free jail script that runs multiple prisons on the same map
A resource written against qbx_core talks to it directly. One reached through the bridge carries its older calls along with it, which usually works and occasionally does not. Neither is wrong, but it is worth knowing which you are buying, especially if your core carries custom job or gang logic.
The dependency line, whether items and interactions are registered with the resources your server already runs, and the update history. Qbox moves faster than the framework it forked from, so a recently maintained resource is worth more here than elsewhere.
Usually not. The bridge handles most older calls, and plenty of servers run bridged resources without trouble. Native support skips that translation layer, which is why product pages distinguish the two.
Many assume them because most servers on this framework run them. The dependency line on each product page is the place to confirm it before buying.
On the type shelves. This view is filtered by framework support, so it is for browsing what exists rather than for weighing two alternatives.