Description
A speed-enforcement radar/LIDAR gun for roleplay servers: an officer aims at a vehicle, the tool captures its speed and plate with a timestamp, and the server records a citation whenever the reading is over the limit. Servers buy it because radar enforcement is a staple patrol tool that feeds straight into a citation or MDT system.
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 at content/expected-outputs/police/16-speed-radar-lidar-enforcement.lua implements a forward shape-test to lock a vehicle, captures its speed and plate, and files a timestamped…
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 citation store — keeping the citation table on the client lets a cheater forge or wipe records.
- Unvalidated client speed — trusting the client speed/plate with no server bound lets it send arbitrary values.
- Half-registered event —
radar:logCitationwithoutRegisterNetEventmeans the server never receives the capture.
Corrective re-prompt: Keep the citation table and the over-limit comparison entirely server-side, reject a non-string plate or non-positive speed before storing, and declare radar:logCitation and radar:notify with RegisterNetEvent plus handlers on their receiving sides.
Framework Integration
ESX: local ESX = exports['es_extended']:getSharedObject(); gate radar:capture behind xPlayer.job.name == 'police' and persist citations to your MDT table.
QBCore: local QBCore = exports['qb-core']:GetCoreObject(); check Player.PlayerData.job and notify via QBCore:Notify.
QBox: exports.qbx_core:GetPlayer(src); the shape-test capture and citation table are framework-agnostic.
Profit Potential
$150–$2000/mo on Tebex (expected ~$500). [INFERRED] priced inside the $50-389 script band against the signal-scraper tebex_snapshot corpus (n=100, median seller $11.85K/mo), scaled to a stable traffic-enforcement niche.
Trend Signal
→ stable — inferred: Speed radar/LIDAR traffic enforcement is an established patrol tool; distinct from ANPR (speed capture, not plate read).
Sales Angle
Position as a staple traffic-enforcement tool that feeds a citation/MDT pipeline — recommended Tebex price $89, cross-sold with an ANPR or charge-sheet module.
Difficulty & Ship Time
intermediate · ships in 2-3h.