QBCore · Police job
QBCore Police Job: Server-Side Authority Checklist
Police scripts touch permissions, player state, inventories and roleplay trust. The biggest rule is simple: the server decides what is allowed.
Validate every sensitive action
- Check the officer job and grade on the server before cuffing, searching, fining, jailing or opening evidence storage.
- Re-check target distance server-side where possible instead of relying only on a client marker.
- Log important actions with officer ID, target ID, time and reason so staff can review abuse reports.
Keep jail and evidence predictable
- Put jail timer limits in config and clamp any incoming value before saving it.
- Restrict evidence lockers by job and grade; never expose stash names through random client input.
- Separate roleplay text from enforcement logic so UI changes do not weaken permission checks.
Test rejected paths
- Try cuffing while off duty, from the wrong job, too far away and with a spoofed client event.
- Restart the resource while a player is jailed and confirm the state recovers correctly.
- Confirm low-grade officers cannot access high-grade tools unless config allows it.
Use this with Stellar AI
Ask Stellar for a police job plan with duty checks, server validation and test cases before adding visual polish.