Description
An ESX tow dispatch that turns NPC-spawned and player-submitted tow calls into a shared job queue: drivers see pending jobs, claim one to get a GPS route to the stranded vehicle, and on completion the customer is billed a server-charged invoice while the driver is paid out. It's the job-board pattern tow servers run as the spine of their tow economy.
Prompt Template
You are writing a FiveM resource for esextended (stable, exports getSharedObject).
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth, both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access, pay once
- All 510 prompts, the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates, new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence, one-time, no subscription.
Expected Output
The reference Lua lives at content/expected-outputs/mechanic/29-tow-dispatch-invoicing.lua. It implements one server-owned job queue (NPC + player requests), atomic claim so only one driver gets a…
The full prompt template and its reference Lua are part of a one-time pack. Pick your depth, both are lifetime access, no subscription, ever.
- 60 prompts + syntax-validated reference Lua
- Lifetime access, pay once
- All 510 prompts, the full library
- Per-prompt profit/trend intelligence (CSV + playbook)
- Lifetime free updates, new niches as the market moves
$49 for 60 · $199 for all 510 + intelligence, one-time, no subscription.
Known Failure Modes & Corrective Prompt
- Client-side money, billing/paying on the client lets payouts be forged; route every invoice and payout through the server.
- Per-client queue, a local queue lets two drivers claim one job; the server owns a single queue with an atomic claim.
- One-sided net event, request/claim/complete on a single side never flows; both sides need
RegisterNetEvent+AddEventHandler.
Corrective re-prompt: "Keep a single jobs table on the server and make tow:claim set claimedBy only when it is currently nil. In tow:complete verify source == claimedBy, then xCustomer.removeMoney(fee) and xDriver.addMoney(payout) server-side before removing the job. Remove any client balance changes and confirm both sides register the events."
Framework Integration
- ESX: native,
xPlayer.addMoney/removeMoneyhandle payout and invoice;ESX.GetPlayerFromIdresolves driver and customer. - QBCore: swap to
Player.Functions.AddMoney/RemoveMoney; resolve viaQBCore.Functions.GetPlayer. - QBox: identical to QBCore via
exports.qbx_core:GetPlayer; money and resolve calls map one-to-one.
Profit Potential
$150-$2000/mo on Tebex (expected ~$500), $50-389 script band × est units/mo for a stable niche, against a corpus of comparable Tebex sellers (median ~$11.85K/mo).
Trend Signal
→ stable, corpus: Dispatch/job-board pattern on ox_lib; steady tow-economy demand (scraper-observed).
Sales Angle
This is the connective tissue of a tow business, price $129-189 and bundle it with the flatbed (#26) and impound (#27) so a server buys one coherent tow economy instead of three loose scripts.
Difficulty & Ship Time
intermediate · ships in 2-4h.