- ESX
- QBCore
- Qbox
DRC Beanmachine Job
DRC Bean Machine brings a NoPixel-inspired coffee shop job to ESX, QBCore, and Qbox with 57 interactive items, multi-step cooking, 40 delivery routes, and a full boss management suite.
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.
Most respray scripts treat every location the same — same prices, same access, same everything. This Pay and Spray script works differently. Each location you place on the map has its own config block: its own cost, its own repair duration, its own job lock setting, and its own required items if you want that layer of gating. That per-location granularity is the core feature, and it changes how you design your server economy.
You can run a cheap public spray shop out in Paleto, a mechanic-job-locked premium location downtown, and a high-cost luxury detailing shop near the airport — all from one script, each with independent settings. Job locking through ox_target or qb-target means only your mechanic whitelisted players can bill through a shop location, which gives mechanic job owners a real revenue stream instead of competing with free public sprays. For locations you want fully open, disable job locking per location and let any player walk in.
The script runs on ESX, QBCore, and Qbox with ox_lib as the core dependency. Targets default to qb-target or ox_target. The wide notification and banking compatibility means you most likely won't need to add anything to your stack — just drop it in, configure your locations, and start placing zones.
Server owners who care about player economy know that blanket access to cheap resprays kills mechanic job income. The ability to lock specific locations to whitelisted jobs — while keeping others open — lets you design around that. Put the cheap public spray shops in low-income map areas. Lock the better ones to mechanics. Charge premium rates at high-traffic intersections. The config makes all of that possible without writing a single line of Lua.
Use the documentation included with the download as the final authority. This plan helps you prepare a rollback, install in the right order, and verify the resource before it reaches players.
Open the supplied documentation before moving files or changing the database. Build the install order from the package, not from assumptions.
Ready when Every dependency and required file has a place in your install plan.
Prepare the server so the change can be reversed cleanly if the resource conflicts with your current stack.
Ready when You can restore the previous database, files, and configuration.
Apply only the changes supplied for this resource, keeping dependency and startup order intact.
Ready when The resource starts without missing files, exports, tables, or dependencies.
Restart the test server, watch both server and client consoles, and exercise the resource before opening it to players.
Complete when The intended flow works twice with no new console errors.
Pay And Spray
Contact support
The script works perfect on our QBCore city. Only the documentation link was missing one step for ox_target, but script itself runs without errors.
Picked this up during a sale last week without really thinking it through. Setup was dead easy on qbcore and the chameleon paint preview actually looks super clean in game. We ended up taking it off the server after a few days though, mostly because our player base is heavily focused on strict mechanic roleplay so public spray booths just didn't fit the vibe of our city. Solid resource if you want per-location pricing, just wasn't right for our economy.
Reviews are moderated before appearing. Purchased the product? Your review gets a VERIFIED badge automatically.
Pay And Spray is a FiveM resource for esx, qbcore, qbox servers. Review the product details, requirements, and compatibility notes before ordering.
Use the included files and documentation as the source of truth for installation, configuration, dependencies, and any stated performance information.