Description
A courier delivery-run system for ESX, QB, or QBox servers: requesting a run picks a random drop zone, routes the player there via a GPS blip on a countdown, and pays a base fee plus a speed bonus on arrival. Servers sell this because a timed delivery loop is the bread-and-butter content layer for any dealing or trucking job, even saturated, a clean drop-in version moves on price.
Prompt Template
You are writing a FiveM resource for a generic framework via exports (esx/qb/qbox).
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/drugs/20-courier-delivery-runs.lua. It implements a server-picked random drop, a server-stamped start time, an owner-verified delivery with a speed…
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-trusted completion/payout, a spoofed deliver event mints money; the server owns the run, drop, and pay.
- Client-only timer, alt-tabbing dodges the fail; stamp
startedon the server and validate elapsed on delivery. - Spoofable proximity, keep the client distance check render-only; the server is the source of truth for the run lifecycle.
Corrective re-prompt: "Generate the drop coords on the server in courier:request, stamp os.time() as started, and in courier:deliver verify the owner and recompute the elapsed-time bonus server-side before calling addMoney, never accept a payout amount from the client."
Framework Integration
- ESX: swap
gen_coreforexports['es_extended']:getSharedObject(); pay withxPlayer.addMoney(amount)and notify viaESX.ShowNotification. - QBCore:
exports['qb-core']:GetCoreObject(); pay withPlayer.Functions.AddMoney('cash', amount)and route blips via the standard map config. - QBox: use
exports.qbx_core:GetPlayer(src)andPlayer.Functions.AddMoney, drop config sits in shared/config for easy zone edits.
Profit Potential
$80-$1200/mo on Tebex (expected ~$300), within the $50-389 script band against a corpus of comparable Tebex sellers (median ~$11.85K/mo), set for a saturated, heavily-cloned delivery niche.
Trend Signal
↘ saturated, corpus: Timed delivery-run loop is among the most-cloned drug mechanics on Tebex, saturated.
Sales Angle
Position as the clean, framework-agnostic delivery primitive a server bolts onto any dealing or trucking job, beat the cloned packs on a low price and a tidy codebase. Recommended Tebex price $59.
Difficulty & Ship Time
beginner · ships in 2-4h.
