Skip to content

Troubleshoot Evidence System

Check scene discovery, tool exports, locker access, sample identification, and database setup.

On this page

The resource does not start

  • Match these instructions to a BigB_evidence 1.0.1 manifest, not an older XSC Evidence archive.
  • Confirm the resource folder is named BigB_evidence and fxmanifest.lua is directly inside it.
  • Check OneSync, Qbox, and the ox dependencies. Qbox APIs and its player schema are required.
  • Read the first server error for missing imports, invalid Lua configuration, database connectivity, or table-creation permissions.
  • For an entitlement failure, reinstall the complete entitled Cfx download with its delivery files preserved and verify the server licence account.

No traces or collection prompt appear

  • Test in routing bucket 0. Scene evidence is restricted to that bucket.
  • Use the correct light: free-aim a normal flashlight for blood/casings, or use the UV item for prints/impacts. Move within interaction reach and keep a clear line of sight.
  • Check duty status and the configured job/grade. Civilians have a fresh-evidence delay and do not have the same scene access as an on-duty officer.
  • For missing blood, check Config.Integrations.medical. Standalone handles real positive firearm/blade damage to the local player; custom mode requires your medical script to call ReportWound.
  • Check trace expiry, inventory capacity, and whether another player has already collected the trace. Try a small fresh scene rather than an expired sample.

Scene collection uses the light-guided E/Y prompt, not an ox_target option on every trace. Fixed stations and player sampling still use their own interactions.

A tool does nothing or its image is missing

  • Confirm all required entries from install/ox_inventory_items.lua were merged, including each client export.
  • Match Config.Items to the inventory item names and keep the runtime folder BigB_evidence so the export path resolves.
  • Copy the supplied xev_*.png files to your inventory's configured image path and restart after item-definition changes.
  • Check the client's first export error and the player's role, duty, and current activity. Weapon selection ends UV use.
  • If only the camera is unavailable, check the optional camera provider. A configured item is not a replacement for its capture/upload service.

A locker is unavailable or looks empty

  • Check the officer's LockerJobs access, duty state, routing bucket, configured station proximity, and the locker's archive state.
  • For an upgrade, compare the old and new locker prefixes before creating new lockers. BigB_evidence 1.0.0 used evidence_locker_; 1.0.1 defaults to xev_locker_.
  • Follow docs/UPGRADING.md for the coordinated offline database/inventory mapping. Migration must preserve item metadata and avoid overwriting an existing destination stash.
  • Read storage/database errors. Legacy-storage detection or a failed storage check can intentionally keep a locker unavailable.

Analysis is pending or the identity is unknown

Analysis is queued and uses the configured duration for each type. Check the lab role/location and custody requirements, then allow the processing interval. A serial-recovery chance is not a guarantee. DNA and fingerprint names resolve only when the person is on file; an unknown result can be expected.

A missing MDT tab or case list usually means the optional compatible MDT adapter is absent or disabled. Test the included locker and bench panels independently of the external terminal.

Contact support with the relevant details

Include the manifest version, Qbox/inventory versions, the first console error, affected tool or station, role/duty state, and steps to reproduce. For an upgrade, identify the previous implementation and whether a migration was performed. Redact credentials, webhook URLs, and unrelated player data.