Configuration

CCTV ships with conservative defaults and does not require a roleplay framework. It still requires the free Events Core package. Test configuration changes before using the system for production evidence workflows. Administrators can manage terminals, cameras, capture settings, and placement from the CCTV interface.

​

Configuration files

​

Events Core

​

CCTV

Keep API tokens, Discord webhooks, and private endpoints in server-only files. Never place credentials in client configuration or NUI files.

​

Important shipped defaults

​

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 available on the server. ACE remains the default permission source.

​

Recording and retention

Events Core stores the incident data used for historic playback under eventsCore/data/recordings by default. CCTV stores terminal and camera configuration in eventsCctv/data/cctv.json. Measure available disk space and establish a backup policy before increasing retention. Recordings can contain player, vehicle, and incident information.

​

Optional integrations

Discord, remote viewing, external storage, and recording uploads are optional and disabled or restricted by default. Enable one integration at a time on a test server, keep credentials server-side, and grant only the required permissions.

​

Map and MLO cameras

Automatic discovery of compatible camera props is disabled by default. Configure and verify a manual camera first, then follow Camera Setup before enabling discovery.