New Sale
Player Owned Chopshop by Pug Development
$30.00
$20.00
Buy a garage, run a crew, strip cars for parts
Lifetime updates
Pug Development FiveM Scripts
Pug Development focuses on player-owned jobs for FiveM, the kind where one player buys the business and other players actually work shifts inside it. The current lineup runs on ESX, QBCore and Qbox, and leans on standard scene libraries so it drops into most existing servers without a rebuild.
Pug Development's catalog is small and focused on one idea: jobs where one player owns the operation and other players clock in under them. That is a specific corner of the FiveM economy, and it is where most of the interesting server drama comes from, so it makes sense as a niche to specialise in.
The three products currently listed are Advanced Chopshop [Player Owned], Advanced Fishing Job, and a FREE Advanced Coke Job [Player Owned]. The free coke job is a useful way to try the studio's config style and code quality before paying for the chopshop, and it also gives smaller servers a solid drug loop without spending anything.
Signature work and style
The pattern across the catalog is clear. A business location, an owner who paid for it in-game, a hiring flow so other players can be employees, and a work loop with progression on top. In the chopshop that means players bringing in stolen vehicles, the owner setting cut rates and part prices, and staff actually doing the stripping. In the fishing job it means a licensed operation with gear tiers and a shop, not just /fish on a pier.
Because these are player-owned resources, the interesting configuration lives around the owner side: who can hire, who can fire, what percentage the boss takes, what stock the shop carries, what the buy-in costs. Server owners buying Pug scripts are usually looking to replace a static NPC job with something roleplay can actually build a story around, and the catalog is built for that use case rather than for solo grind loops.
The naming convention ('Advanced <Job>') signals what to expect: not a one-file quickie, but a fuller system with UI, permissions, and enough config to be worth installing over the framework default.
Compatibility & installation
Everything on this page targets ESX, QBCore and Qbox, which covers most active FiveM servers. Installation is the standard drag-and-drop into your resources folder, an entry in server.cfg, and imports for whichever framework you run. Because Qbox is included alongside QBCore, servers that have migrated off legacy qb-core do not need to patch anything up themselves.
Dependencies follow the modern scene defaults, so expect ox_lib and ox_target style interactions rather than qb-menu or nh-context. That is worth knowing before you buy: if your server is still on the old menu stack, plan the ox_lib install at the same time, it is a one-time job that pays off across every modern script you add after.
Database changes for the player-owned jobs are limited to the tables the job itself needs (ownership, employees, stock, transactions). Nothing here rewrites your core player or inventory tables, so uninstalling later is clean.
Why buy Pug Development scripts here
Buying through this store gets you the same files you would get direct from the creator, with an account that keeps every FiveM purchase in one place instead of scattered across a dozen Tebex receipts. Updates and re-downloads sit on your library page, which matters for the paid Advanced Chopshop where you will want the latest version whenever a framework bump breaks something upstream.
The free coke job is the honest starting point. Install it, look at the config, see how the studio structures a player-owned loop, and decide from there whether the chopshop is worth the spend for your server. Most owners who like one Pug script end up running all three, because they share a config style and a mental model of how a boss/employee job should work.
Frequently asked questions
What frameworks do Pug Development scripts support?
The current catalog targets ESX, QBCore and Qbox. Qbox is treated as a first-class target alongside QBCore, so servers that migrated off legacy qb-core do not need to patch the scripts themselves.
What kind of scripts does Pug Development make?
Player-owned jobs. Rather than static NPC jobs, these resources let one player own the business (chopshop, fishing operation, coke lab) and hire other players as employees, with configurable cuts, stock, and permissions.
Is there anything I can try before buying?
Yes. The FREE Advanced Coke Job [Player Owned] is a full script at no cost. It is a good way to see Pug's config style and code quality before spending on the paid chopshop.
What are the dependencies?
Expect the modern scene defaults: ox_lib and ox_target for menus and interactions, plus your framework's core exports. If your server still uses qb-menu style stacks, plan the ox_lib install at the same time.
Will installing these mess up my database?
No. Each job adds only the tables it needs for ownership, employees, stock and transactions. Nothing rewrites your core player or inventory tables, so removal later is clean.
How do updates work when I buy here?
Purchases sit on your library page, so re-downloads and updates are always one click away. That matters most for the paid Advanced Chopshop, where you will want the current build whenever a framework update shifts something upstream.
Are these scripts escrowed or open source?
Check the individual product page for each release. The config files are always editable so you can tune prices, cuts, locations and stock without touching protected code.
