Police, MDT & Evidence

Three separate integrations that often live in the same script.

• Police — who cuffed, robbed, searched or escorted whom, for the proof log.
• MDT — where camera reports and witness statements are filed.
• Evidence — fingerprint and DNA matches, which grant a Lab ID.

#Police jobs first

None of this works until the job names are right.

Both lists ship with 'police' only, the one police job stock QBCore, Qbox and ESX all have. config.lua keeps a commented example line under each list for your other departments:

Config.Jobs = {
    Police = { 'police' },
    -- Police = { 'police', 'sheriff', 'fib' },   -- example: add your other departments
    HintJobs = { 'police' },
    -- HintJobs = { 'police', 'sheriff', 'fib' },   -- example: add your other departments
    AcceptTypes = { 'leo' },
}

#Police scripts

Config.PoliceSystem = 'auto'

Config.Proof.CuffStateKeys = { 'ishandcuffed', 'isHandcuffed', 'isCuffed', 'cuffed', 'cuffs' }
Config.Proof.OxInventoryHooks = true

#When nobody is named

Some scripts cuff a player without saying who did it. Then the nearest facing player within Config.Proof.InferActorRadius (2.5 m) is logged as the likely actor — marked as such, never as proven. Treat it as a lead in the timeline.

#MDTs

Config.MDTSystem = 'auto'

#Auto-detect checks the exports, not just the name

A resource that runs under the right name can still be a build without the export the bridge calls. lb-tablet 1.5.3 is one: it has no CreateMDTReport. So before an MDT is used, the bridge checks that the export it would call is really there. It only looks at the export and never runs it.

• 'auto' skips a running MDT whose build has none of the exports it would be picked for, prints one line with the resource, its version and the missing export, and moves on to the next MDT in the auto order. If nothing is left, it uses 'none'.
• A named MDT (for example Config.MDTSystem = 'lb-tablet') gets the same check. If it has none of those exports, you get one warning and the bridge uses 'none' until it has them, so pushes are not tried and then failed one by one.
• A missing optional export turns off only that feature. An lb-tablet without AddDispatch still takes statements and camera reports, and only the dispatch alert is off. A tk_mdt with createPoliceReport but no registerEvidence still takes statements, and only camera reports are off. This is also checked at the moment of each push, so a resource restarted into a different build is picked up without restarting 5code-recognition.
• A skip is never final. Many MDTs create their exports a moment after they start, once their database is up. So a skipped MDT is checked again a few times in the first minute after the server (or that MDT) starts, and after that each time a statement or camera report is sent, at most every 10 seconds. When the export is there, the MDT is used from then on, without a restart, and the console says so once.
• Updating the MDT is enough. When the resource that was skipped starts again with a build that has the export, it is picked up, even if auto had picked another MDT lower in the list in the meantime.

[5code-recognition] MDT auto-detect skips lb-tablet (version 1.5.3) for now: it does not export CreateMDTReport (yet), which statements and camera reports need. It is checked again, so an export that turns up later is used without a restart.
[5code-recognition] MDT lb-tablet (version <its version>) has its export(s) now, so statements and camera reports go to it.

The second line only appears if the export turns up later.

#Per-MDT options

Case-sensitive. Only the selected MDT's entry is used.

Config.MDT = {
    ['lb-tablet']     = { Mdt = 'Police', TabId = 'reports', TextFieldId = 'description' },
    ['tk_mdt']        = { Page = 'police' },
    ['redutzu-mdt']   = {},
    ['drx_mdt']       = {},
    ['origen_police'] = { Job = 'police' },
    ['wasabi_mdt']    = {},
}

#Report and statement settings

#Evidence and Lab ID

Config.EvidenceSystem = 'auto'

A fingerprint or DNA match produces a Lab ID — a separate record that says "the lab matched this sample to this person". It is not a memory and it is not a recognition.

#Any evidence script

exports['5code-recognition']:GrantLabIdentification(officerSrc, targetCharKey, opts)

Add your resource to ServerConfig.Api.TrustedResources, and call it from your server code after your own checks — never straight from a client event.

#Lab settings

#Client-side evidence scripts

Some evidence resources run the whole match on the player's own game instead of on the server. Lab IDs from those get these extra settings:

#Camera reports and the police cap

A hidden-camera recording does not drop a paper by itself. Once the camera's recording reaches 50 % (the HUD shows REC n%, green from 50 %), it waits in the owner's F3 menu → Camera recordings (last 24 h). The owner prints it there once, with the hidden camera in their inventory (3 s "Printing..."). Where an MDT is supported and the owner is police, the MDT copy is sent when the recording is saved. See Hidden Camera & Reports.

An officer who reads a hidden-camera report gets a memory of that person capped:

#The "possible match" hint

After any scan, a player holding a matching report or description may see "Looks like someone you were told about".

An empty Config.Jobs.HintJobs = {} turns the hint off for everyone.

#Custom

Set Config.PoliceSystem, Config.MDTSystem or Config.EvidenceSystem to 'custom' and fill the branch in bridge/police_server.lua, bridge/mdt.lua or bridge/evidence.lua.

See Writing a Custom Adapter.