New
- ESX
- QBCore
- Qbox
Weapon Attachment UI
Visual FiveM weapon attachment UI with inventory persistence, addon weapon support, job/item gates, and 0.01ms active cost. Standalone or integrated with ox, ESX & QBCore inventory.
Everything filed here names QBCore among the frameworks it supports. That is a starting point, not a guarantee: a resource can target qb-core and still expect a particular inventory, targeting system or database layout. Open the listing and read the requirements before you buy.
New
Visual FiveM weapon attachment UI with inventory persistence, addon weapon support, job/item gates, and 0.01ms active cost. Standalone or integrated with ox, ESX & QBCore inventory.
Sale
Advanced Scuba Diving V3 builds a full underwater economy: boat rental, oxygen-tracked dive tanks, shipwreck loot, skill-based crate minigames, and a quest system with XP leaderboard. ESX, QBCore, Qbox — one purchase.
Sale
FiveM slaughterhouse job with a full catch-to-grind processing chain, XP-gated success rates, dynamic market pricing, and dual delivery options for ESX, QBCore and Qbox servers.
Sale
Sale
Free standalone FiveM dodgeball script with 1v1 to 5v5 match formats and a Vespucci Beach court included. No framework dependency — compatible with ESX, QBCore, Qbox, and Gamzky Scripts.
Popular
Give FiveM officers a proper equipment trunk — visual prop layout, per-vehicle item config, clothing slots, job-gated access, and 0.03ms active usage. ESX, QBCore & Qbox.
CS2-style FiveM gun menu with configurable colors, stock, and pricing. Delivers weapons to inventory or hand. Minimal setup. ESX, QBCore, Qbox and standalone compatible.
FiveM outfit items script with job and grade-based access, live character previews, and wearable inventory items that apply full uniforms instantly. QBCore, ox_inventory, ox_target ready.
FiveM electrician job with a 4×4 circuit-board puzzle, randomized fusebox dispatch, auto-detecting ESX and QBCore support, and a verified 0.00ms active resmon — white-collar civilian work at £5.99.
Per-location Pay and Spray script for FiveM with individual pricing, job locking, livery preview, chameleon paint, and vehicle repairs. Runs on ESX, QBCore, and Qbox with broad inventory, banking, and fuel compatibility.
Sale
JG Mechanic gives FiveM servers a full RGB and chameleon respray system, OneSync-synced visuals, engine swaps, dyno testing, and mileage-based servicing at 0.0-0.1ms resmon on ESX, QBCore, and Qbox.
Sale
A listing that names QBCore is telling you the resource speaks the framework's
player, job and money exports. It is not telling you which inventory it draws
into, which targeting resource it hooks, or which version of qb-core it was
built against. Those are separate answers and they live in the listing's own
requirements section.
qb-core version. A resource written against an older core can calloxmysql or another wrapper.A fork that renamed exports is a different target, however close it looks. If you
run one, treat QBCore support as a strong hint and verify against the fork's own
documentation rather than assuming a clean drop-in.
Framework compatibility is a filter, not a shelf. Most resources here also appear
under ESX or Qbox because they
support more than one. If you are starting from nothing rather than adding to a
running server, the readymade builds are assembled
rather than assorted. For the map side of a build, see the
MLO interiors.
It means the resource uses QBCore's framework exports. Your inventory, targeting resource, database wrapper and core version still have to line up. Each listing states what it was built and tested against; read that section before you buy.
Sometimes. A fork that kept the original export names usually works. One that renamed or removed them does not, and no framework label can tell you which you have. Check the resource's requirements against your fork's documentation.
Because many of them genuinely support more than one framework. The framework pages are filters over the same catalogue, not separate stock.
Treat the dependency as part of the price. Some are free and widely used, others are paid resources in their own right. The listing names them so you can check before checkout rather than after.
Where the resource publishes them, yes. The listing is the authoritative place for supported versions, required resources and what changed; this page only groups by framework.