Warrant Request & Service Workflow

Description

A full warrant pipeline for civic roleplay: an officer files an arrest or search warrant with evidence, a judge reviews the pending queue and approves, and only a served, approved warrant unlocks entry/arrest authority. It is distinct from an MDT warrant lookup — this is the file→approve→serve state machine that puts a judge between an officer and a forced entry.

Prompt Template

You are writing a FiveM resource (client.lua + server.lua) for a warrant request and…

Expected Output

The reference Lua at content/expected-outputs/police/23-warrant-request-service-workflow.lua implements a server-owned pending→approved→served state machine: officers file, a judge approves from the…

Known Failure Modes & Corrective Prompt

• Officer self-approval — tracking status on the client lets an officer skip the judge; the server owns the state machine and only a judge moves pending→approved.
• Unchecked service — granting authority without verifying status == 'approved' unlocks pending/unfiled warrants; validate the transition server-side.
• Half-registered round-trip — RegisterNetEvent without AddEventHandler on one side makes approvals no-op; register and handle on both sides.

Corrective re-prompt: "Enforce the state machine on the server: warrant:approve requires isJudge and only moves pending→approved; warrant:service requires isOfficer AND status=='approved' before it sets served and grants authority. Wire RegisterNetEvent + AddEventHandler on both client and server for file, list, approve, and service."

Framework Integration

• ESX: resolve exports['es_extended']:getSharedObject(); isJudge checks xPlayer.job.name == 'judge', isOfficer checks 'police'; persist warrants in a warrants table via MySQL.
• QBCore: use exports['qb-core']:GetCoreObject() and Player.PlayerData.job.name; surface the pending queue inside the MDT for judges.
• QBox: call exports.qbx_core:GetPlayer(src) and store warrant rows with oxmysql, exposing an export so the entry/arrest scripts can query served-warrant authority.

Profit Potential

$280–$3500/mo on Tebex (expected ~$1100). [INFERRED] priced inside the $50-389 FiveM script band for a rising civic-RP niche; corpus median seller $11.85K/mo (signal-scraper tebex_snapshot n=100).

Trend Signal

↗ rising — strategy: Search/arrest warrants are called out in MASTER-200 id-077 Wanted-Level Overhaul ($99); judge-approval workflow rising in civic-RP. Distinct from MDT warrant lookup.

Sales Angle

Sell as the civic-RP warrant pipeline that puts a judge between an officer and a forced entry — file, approve, serve, authority. Recommended Tebex price $279.

Difficulty & Ship Time

advanced · ships in 1 day.