FiveM Scripts, MLOs & Vehicles Catalog
About 270 FiveM and RedM resources, each tagged with the frameworks it runs on, so you can filter by ESX, QBCore, Qbox or Standalone before reading a single changelog. Pay once, download right after checkout, keep every update.
Framework tagged
Every listing names its ESX, QBCore, Qbox or Standalone support.
Ready after checkout
Your download is live the second the order completes.
Updates included
Re-download the newest version from your account, no extra charge.
Free to start
41 free scripts to try before you spend anything.
Jump to a category
QBCore Scripts
162 resources for qb-core based servers
Qbox Scripts
Qbox-ready jobs, systems and admin tools
ESX Scripts
144 scripts for ESX Legacy servers
FiveM MLOs
122 interiors, shops, stations and hideouts
Free Scripts
41 zero-cost resources, full downloads
Jobs Scripts
39 jobs, from burgers to heists
FiveM Cars
9 debadged, lore-friendly vehicle packs
Showing 1–15 of 273 resultsSorted by latest
Buying FiveM scripts for your framework: a short field guide
Match the framework before you look at features
Start with the framework line on the listing, not the feature list. A script written for ESX Legacy expects es_extended exports and an ESX player object; the QBCore version talks to qb-core and QBCore.Functions. They are not interchangeable without a rewrite.
Qbox is a different story. It forked from QBCore and ships a compatibility bridge, so a lot of qb scripts run on it unchanged. Still, where a creator publishes a Qbox build, buy that one. It will usually assume ox_lib, ox_inventory and ox_target instead of their qb equivalents, which is exactly what a fresh Qbox install runs.
Standalone means no framework dependency. It does not mean no dependencies at all. Read the dependency list on the product page and compare it with what your server.cfg already ensures.
What the resmon number is actually telling you
Resmon is the F8 overlay that shows CPU time per frame and memory for every running resource on the client. The number worth caring about is the idle figure. A job script sitting at 0.08 ms while nobody is on shift has a thread looping every tick without a proper Wait.
Scale matters here. 150 resources idling at 0.05 ms each burns 7.5 ms of the 16.6 ms a client has per frame at 60 fps, before the game itself draws anything. When a creator quotes a resmon figure on a product page, they almost always mean the idle number, so treat 0.00 ms idle as the target for background resources and ask what it costs under load.
Installing an MLO: stream, ensure, walk it
Put the folder in your resources directory and add an ensure line to server.cfg. Anything inside the stream folder (ydr, ytd, ybn, ymap) is sent to clients automatically, which is why a FiveM MLO rarely needs more than that one line.
Then walk the whole interior before you open it to players. Check doors, stairs and the roof for missing collisions. If walls flicker or two interiors overlap, a second resource is streaming a ymap for the same coordinates, and one of them has to go.
How updates reach you
There is no auto-updater. When a creator releases a new version, the file attached to your order changes and you download it again from your account. Before you overwrite anything, copy your edited config.lua out of the old folder and diff it against the new one, because defaults move between versions.
The same flow applies to every free script in the catalog. Install one of the 41 free resources, sit through one update cycle with it, and you will know exactly where the new files land before a paid job pack needs the same treatment.
Questions buyers ask before checkout
The resource runs without ESX, QBCore or Qbox installed. It can still depend on shared libraries such as ox_lib or a target resource, so check the dependency section on the product page before you ensure it, and confirm those resources start before the script does.
Often, yes. Qbox keeps a qb-core compatibility layer, so plain qb scripts tend to work. Scripts that hook qb-inventory directly are the usual exception, since Qbox servers normally run ox_inventory. Where a listing offers a Qbox version, pick it and skip the bridging.
No. An MLO is map data, so it streams the same way on ESX, QBCore, Qbox or a framework-free server. Framework only enters the picture when you pair the interior with a job or shop script that needs a matching player object and inventory.
Usually not on its own. Check whether debug mode is enabled in the config, whether a missing dependency is forcing a retry loop, and whether another resource is hooking the same event. Compare the idle value against the in-use value with resmon 1 before you blame the code.
Four things: your framework, your inventory (qb-inventory, ox_inventory or ESX default), your target system (qb-target or ox_target) and your notification resource. Job scripts touch all four, and a mismatch on any one of them means editing the bridge files before the job works.