CCTV Cameras
Step-by-step installation guide, common issues & solutions, code snippets, error codes, config previews, locales previews, SQL previews, and changelogs; all in 1 easily accessible place.
2. Unzip the
cd_cctv.zip folder and place this folder in your server's resource folder.3. Add the resource to your server start config:
ensure cd_cctv. If you are using a framework, it must be placed anywhere below your framework resource e.g., es_extended, not above.
You MUST read all configurable options inside the
[cd_cctv/configs/config.lua] file and configure them to suit your server's needs. Please read the ”commented out help text” at the end of each line so you can understand what each config option does.
Introducing our new 'auto_detect' feature! It automatically identifies your framework and applies the appropriate default settings.
In the
[cd_cctv/configs/config.lua] file, scroll down to the PLACING CCTV CAMERAS section. In the 
Config.CCTV table you can configure default cameras or add new ones; everything is explained in the ”commented out help text”. 
This resource is very easy to install, configure and use. Once the steps above are complete, the rest is simple:
- 1.You have 2 ways to place the CCTV cameras, depending on if you use a framework. You can either use the
/cctv1or/cctv2chat commands or use thecctv1orcctv2usable items (if you use a framework). - 2.Now you have placed your camera, use the
/cctvuichat command to open the CCTV management UI; here, you can view the cameras and give other players access to view your cameras.
These chat commands can be renamed and/or disabled in the Keys and Commands section of the
[configs/config.lua].The exact usage for each command will be displayed in the chat suggestions when using the commands in-game.
Command | Description |
|---|---|
/cctvui | Open the cctv UI. |
/cctv1 | Place a 360° camera (with default settings in Config.CCTV). |
/cctv2 | Place a 180° camera (with default settings in Config.CCTV). |
/cctv3 | Place a fixed camera (with default settings in Config.CCTV). |
These events are completely optional; you can use them if needed.
client-side to client-side
server-side to client-side
Open the CCTV management UI
This very simple event will open the UI where you can view your cameras and give other people access.
TriggerEvent('cd_cctv:OpenCCTVUI')
Open the CCTV management UI
This very simple event will open the UI where you can view your cameras and give other people access.
TriggerClientEvent('cd_cctv:OpenCCTVUI', source)
These exports are completely optional; you can use them if needed.
client-side exports
Gain access to view all cameras within a distance
You can trigger this export in robberies for example to gain access to view all cameras for a period of time within a set distance of the coords provided. [ coords = vector3, distance = integer, time = integer (in minutes) ]
exports["cd_cctv"]:GetTemporaryAccessWithinDistance(coords, distance, time)
Gain access to view a specific camera
You can trigger this export in robberies for example to gain access to a specific camera for a period of time. [ camera_id = string , time = integer (in minutes) ]
exports["cd_cctv"]:GetTemporaryAccessByID(camera_id, time)
Temporarily disable all cameras within a distance
You can trigger this export in robberies for example to disable all cameras for a period of time within a set distance of the coords provided. [ coords = vector3, distance = integer, time = integer (in minutes) ]
exports["cd_cctv"]:DisableCamerasInDistance(coords, distance, time)
Temporarily disable a specific camera
You can trigger this export in robberies for example to disable a specific camera for a period of time. [ camera_id = string , time = integer (in minutes) ]
exports["cd_cctv"]:DisableCameraById(camera_id, time)
The use of usable items can be disabled/enabled in the config. You can also add more in the
Config.CCTV table.Item Name | Description |
|---|---|
cctv1 | Place a 360° camera (with default settings in Config.CCTV). |
cctv2 | Place a 180° camera (with default settings in Config.CCTV). |
cctv3 | Place a fixed camera (with default settings in Config.CCTV). |
Inventory Images (100x100)
cd_cctv_inventory_images.zip
26KB
Binary
Add items on ESX
Add items on QBCore
Run these SQL queries in your database.
1
INSERT INTO `items` (`name`, `label`, `weight`, `rare`, `can_remove`) VALUES ('cctv1', 'CCTV 1', 1, 0, 1);
2
INSERT INTO `items` (`name`, `label`, `weight`, `rare`, `can_remove`) VALUES ('cctv2', 'CCTV 2', 1, 0, 1);
3
INSERT INTO `items` (`name`, `label`, `weight`, `rare`, `can_remove`) VALUES ('cctv3', 'CCTV 3', 1, 0, 1);
Add these lines to [qb-core/shared/items.lua].
1
['cctv1'] = {['name'] = 'cctv1', ['label'] = 'CCTV 1', ['weight'] = 500, ['type'] = 'item', ['image'] = 'cctv1.png', ['unique'] = false, ['useable'] = true, ['shouldClose'] = true, ['combinable'] = nil, ['description'] = 'Placeable 360° CCTV camera'},
2
['cctv2'] = {['name'] = 'cctv2', ['label'] = 'CCTV 2', ['weight'] = 500, ['type'] = 'item', ['image'] = 'cctv2.png', ['unique'] = false, ['useable'] = true, ['shouldClose'] = true, ['combinable'] = nil, ['description'] = 'Placeable 180° CCTV camera'},
3
['cctv3'] = {['name'] = 'cctv3', ['label'] = 'CCTV 3', ['weight'] = 500, ['type'] = 'item', ['image'] = 'cctv2.png', ['unique'] = false, ['useable'] = true, ['shouldClose'] = true, ['combinable'] = nil, ['description'] = 'Placeable fixed camera'},
🔔 Folder Name Make sure the name of the folder either
cd_cctv.🔔 Encrypted Files Do not edit the encrypted files in any way.
If you see an error code not listed below, please open a script support ticket in the Codesign Discord.
Server
Client
N/A
Files ChangedNot every update requires you to replace the whole folder. We do this because we understand it's a pain to redo the configs for every update.
- All Files - This means you should make a backup of the
JSON Filesfolder, delete your oldcd_cctvfolder, download and add in the latest version, replace the new JSON Files folder with the one you made a backup of, configure the configs folder and restart your server. - All Files Except config.lua - This means you should do all of the above (in the All Files section) but additionally make a backup of the
config.luafile and replace the new config.lua file with the one you made a backup of. - Specific Files - This means you can copy and paste the SPECIFIC new files over the old ones and restart the server.
Update TypeOn rare occasions, you are forced to update to the latest version. Mostly due to authentication updates where the old versions will no longer work.
- Mandatory - This means you MUST update to this new version, or the old versions will no longer work.
- Optional - This means it's completely your choice whether you wish to update to the latest version. But we do not offer support for old versions for obvious reasons; they are old.
PLEASE READ! (JSON files)
When updating a resource that uses JSON files as a database as this one does, DO NOT delete/replace the files/folders inside the
JSON files folder, as this will overwrite your saved database.Skipping Updates
If you are attempting to update to the latest version but have skipped previous updates, you should update all files just to be safe. For example., let's say you are currently on v4.0.1, you did not update when v4.0.2 was released, and now v4.0.3 is released, and you want to update; you should always use the “All Files” update method.
Last modified 6d ago