Evidences by noobsystems adds item-based forensic roleplay to FiveM: blood and saliva DNA, fingerprints, bullets, casings, magazines and gunshot residue. Version 1.3.1 includes laptop tools for citizen records and firearms, with optional voice interception. These are game mechanics, not a guarantee that a roleplay investigation proves guilt.
Use the release package and its dependencies
Download evidences.zip from the official release, not only the repository source ZIP. Server startup checks for html/dui/laptop/dist/index.html and stops initialization when the built laptop interface is missing. The inspected v1.3.1 release contains that file. Keep the resource named evidences because supplied item exports use it.
Enable OneSync and start your framework, oxmysql, ox_lib, ox_inventory and ox_target before evidences. Included framework adapters cover ESX Legacy, ND_Core, ox_core, QBCore and Qbox. The selector chooses a started framework; do not assume running several cores together is supported.
Merge the supplied language-specific item definitions into ox_inventory/data/items.lua without renaming their keys. Extract the official item_images.zip into ox_inventory/web/images. Missing required items stop server initialization. The evidence_box container uses 20 slots and maxWeight=5000; version 2.44.4 or later is configured through the inventory export, while older versions need the documented container setup.
Configure access and your server integrations
config.permissions separates laptop placement, pickup, access and evidence collection. Defaults allow police and fib from grade 0. Server handlers perform job/grade checks for these actions; test both permitted and denied users. Review cuff, death and glove checks when using custom police systems or clothing.
Citizen synchronization is enabled by default and reads framework records; manual citizen management is a different configuration path. Wiretap functionality needs pma-voice and its own permissions. Disable config.wiretap.enabled if you do not use it. General external logging is disabled by default, so a configured logging service is not proof that events are being recorded.
Check persistence and item ownership before launch
Back up the database: resource modules create their own tables during initialization. Test laptop placement, pickup, full inventories and restarts. The pickup handler checks query success rather than an affected-row count before returning a laptop item, and placement has no server-side item-possession or proximity check. Add authoritative inventory and one-time pickup checks for this workflow.
Evidence collection checks permissions, carrying capacity and a forensic kit. This does not certify every evidence operation: validate client-supplied evidence references and container ownership, and test collection, analysis and destruction with two players. Existing gallery images are retained below.
Existing image gallery
Reviewed on 10 September 2026 at source revision 0d15876e9a08fd89976ffd64acc5b1338558d92e. Official v1.3.1 resource and image archives passed published SHA256 checks. Setup, configuration, framework selection and selected server data/item handlers were inspected; no FiveM runtime or full security audit was performed.