Configuration files
Events Core
Dashcam
Keep API tokens, Discord webhooks, and private endpoints in server-only files. Never place credentials in client configuration or NUI files.
Important shipped defaults
Branding and units
Config.Brand controls the department name, product name, accent color, speed unit, timezone label, and privacy disclosure. SpeedUnit supports the shipped mph behavior or km/h presentation. The trigger threshold in Config.Triggers.SpeedMps is always configured in metres per second.Framework selection
Events Core is standalone by default. Set its supported framework option to esx, qbcore, qbox, or automatic detection only when that framework is installed and available. Framework jobs can provide standard or elevated Dashcam actions using the grade tables in eventsDashcam/config/permissions.lua.Recording and storage
Events Core stores the incident data used for historic replay under eventsCore/data/recordings by default. Measure available disk space and establish a backup policy before raising capture limits or retention periods. Recordings can contain player, vehicle, location, and incident information.Optional integrations
CAD, Discord, dispatch, phone, inventory, voice metadata, and generated clips require separate configuration. Their shipped bridges are disabled, empty, or metadata-only until you connect a compatible system. Enable one integration at a time on a test server and keep credentials server-side. Dashcam’s standard historic replay works without an encoded video file. Any separate video-generation or upload workflow requires a compatible, trusted recorder or processing setup in Events Core.
The Mobile Evidence terminal keeps recording controls, searchable evidence, replay, and record details in one interface.