DG-EvidenceLockers 1.0.7 by Greken creates named evidence stashes with search, list, clear and delete interfaces. Its bridges include qbx, qb and esx, but the default manifest still requires qbx_core and ox_target and imports sleepless_interact unconditionally. Those declarations must match the framework and interaction mode you intend to use.
Align dependencies and locker configuration
Use the dg-evidencelockers folder, with ox_lib, ox_inventory and oxmysql plus the selected framework and interaction resource. Resolve unused hardcoded manifest dependencies/imports before assuming ox_target and sleepless_interact are interchangeable options. Back up the database and apply install/sql.sql to create police_lockers before starting the resource.
Config.Framework defaults to qbx and Config.Interact to ox_target. The example locker allows police, requires grade 2 to clear and grade 4 to delete, and uses 20 slots with stashWeight=500000. Verify the configured coordinates rather than assuming the VinewoodPoliceDep key points to a particular station. Disable Config.Debug if not needed.
Validate inventory access and destructive actions
The resource handlers check job access, and clear/delete handlers also check configured grades. However, RegisterStash is called without inventory groups or coordinates. Add inventory-level access restrictions or an appropriate openInventory hook; protecting the custom menu alone does not establish protection of the stash itself.
The clear handler accepts a supplied stash name after checking permission for a configured locker, without verifying that the stash belongs to that locker. Bind the target stash to the authorized locker on the server and enforce proximity before clearing. The delete path does check the database locker/stash pair and affected rows before clearing contents; keep that distinction when testing.
Stash names are derived from a cleaned person name and are unique across all lockers. The same normalized name at two stations therefore collides. Creation checks and insertion are separate, with no checked insert outcome. Test accented names, duplicates and concurrent creation, and define a naming scheme that fits your departments.
Deleting removes the police_lockers row and clears contents, but does not explicitly unregister the loaded inventory. Verify immediate access after deletion and after restart. Back up both locker records and inventory contents before migration or cleanup. Test denied jobs/grades, direct inventory access, cross-locker clear attempts, failures and reconnects with disposable evidence.
Reviewed on 11 September 2026 at revision b7ce33e89f171fac01f085cc1bfc7afb5b9ba583. All Lua, bridges, configuration, manifest, SQL, README and NUI HTML/JavaScript were inspected. No evidence stash was opened, cleared or deleted and no FiveM runtime was tested.