Evidence System
Configure scene evidence, forensic tools, persistent lockers, lab analysis, and chain of custody on a Qbox server.
On this page
Choose the guide for your package
Evidence System records scene traces, turns collected samples into inventory evidence, and tracks their movement and analysis. It includes locker, forensics bench, and consent interfaces. The resource runs as BigB_evidence; keep that name for its item exports and integrations.
From a scene to an investigation
- Use a normal flashlight to discover blood and casings, and a forensic UV light to reveal prints and impacts.
- Bag the selected trace with E, or clean eligible blood/casings with Y. Keys are configurable; civilians must wait for the configured fresh-evidence delay.
- Take GSR, DNA, and fingerprint samples with configured tools and the sampling/consent flow.
- Store evidence in persistent inventory lockers, submit it at a lab bench, and review the resulting records and custody history.
- Build biometric records before expecting a sample to resolve to a person's name. Unknown people do not become identified just because a trace was collected.
The default lifetimes are 30 minutes for casings/impacts and one hour for blood/prints. Lab analysis defaults to two to four minutes depending on the type. Change these values for your server in shared/config.lua.
Required and optional components
Required: OneSync, Qbox (qbx_core), ox_lib, oxmysql, ox_target, ox_inventory, and a working database. The resource calls Qbox APIs and uses its player schema; generic QBCore, ESX, and standalone framework operation are not included.
A full MDT, station maps/interiors, camera/upload service, and extra medical or police integrations are separate. The default medical adapter uses the FiveM damage event and does not require a separate medical resource. Optional peer integrations start disabled.