dp-evidencebag by Dzejkop adds item-backed containers for evidence roleplay. The original release dates from April 2025; the inspected repository revision from March 12, 2026 declares version 4.0.0. Bag metadata can identify a container, but this is not a complete chain-of-custody audit system.
Choose the inventory backend
The current source requires ox_lib and supports ox_inventory or qb-inventory with qb-core. Config.Inventory accepts auto, ox or qb; auto prefers ox_inventory if both are running. Start the chosen dependencies before dp-evidencebag. The QB adapter uses legacy inventory events, so verify them against your installed qb-inventory version.
Use evidencebag consistently in the inventory definition and Config.EvidenceBagItem. For ox_inventory, the creator definition uses stack = false and client export dp-evidencebag.openEvidenceBag. For QB, bags must be unique and usable. The old paperbag example with stack = true should not be copied into this version.
Capacity, images and existing bags
The default capacity is 30 slots and 34000 grams. The package includes evidencebag.png, while the README still mentions paperbag.png; make the item image name and installed file agree. Back up existing item definitions and inventory data before changing names or metadata, so already issued bags remain accessible.
The ox_inventory adapter registers a swapItems hook to block placing evidence bags inside other bags. The QB adapter does not implement the equivalent hook; the README calls for a separate inventory-side restriction. Do not promise the same nesting protection on both backends.
Access control and review limits
Creating an identifier checks the owned item and slot. However, the server event that opens a bag inventory checks the identifier format without confirming possession of that bag or a police job. Add the intended server-side ownership and permission checks before relying on this for restricted evidence storage. The client opening cooldown is not a server authorization check.
Identifiers, labels, descriptions and creation timestamps do not record every transfer or evidence-handling action. Add separate audit logging if your police workflow requires it. The archive passed integrity checks and the full relevant Lua, configuration and README were read; no inventory migration or FiveM gameplay was executed.