Radar
INSTALLATION GUIDE
Step 0 - First Steps
1. Download your resource from FiveM's Keymaster.
2. Unzip the cd_radar.zip folder and place this folder in your server's resource folder.
3. Add the resource to your server start config (server.cfg): ensure cd_radar. If you are using a framework, it must be placed anywhere below your framework resource e.g., es_extended, not above.
ensure es_extended
ensure cd_radarStep 1 - Fxmanifest
Depending on your framework and dependencies, you may need to make some changes inside the [cd_radar/fxmanifest.lua]. We have made this easier by commenting on the lines you possibly need to change.
Step 2 - Configure Resource
You MUST read all configurable options inside the [cd_radar/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.
The most important sections are the options under the Frameworkand Importantsections at the top of the config.lua. Everything else is optional.
Introducing our new 'auto_detect' feature! It automatically identifies your framework and SQL database resource, and applies the appropriate default settings.
Step 3 - Configure Key Binds
Important
Before starting this resource on your main/live server, we highly advise configuring your key binds because this resource uses Fivem's Key Mapping.
Where can I configure my key binds?
You can configure key binds in the Keys and Commands section near the bottom of the [cd_radar/configs/config.lua].
Why do I need to do this?
Well long story short;- once a player has joined your server with this resource running you can no longer force change their key binds for this resource through the config.lua, only they can change it in the in-game pause menu settings. Although it will change for the players who join after you have changed it.
The benefit of this system is that it's much more optimised and players can easily change their key binds on keyboards or controllers. You can also check out the Default Keybinds for this resource.
Optional features
This section is to help you understand how the built-in features of this resource work, and if applicable, how you can make them compatible with other resources. These features are not required, they are optional and can be configured in the [configs/config.lua].
Vehicles Data
What is Vehicles Data used for?
When using ESX or QBCore we take information that most servers will already have stored to get the vehicles to display names of custom vehicles.
Adding/Removing BOLOs & spaners from other resources
Why do I need this?
This is optional, but it is possible to add BOLOs and spaners from other resources, such as MDTs or police resources.
Information
Default Key Binds
These keys can be modified and/or disabled in the Keys and Commands section of the [configs/config.lua].
Please make sure you understand how Key Mapping works.
| Key | Description |
|---|---|
J | Interact with the radar's UI. |
O | Toggle the radar lock. |
Chat Commands
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 |
|---|---|
/radarsettings | Interact with the radar's UI. |
/radartoggle | Toggle the radar UI visibility. |
/radarlock | Toggle the radar lock. |
Events
These events are completely optional; you can use them if needed.
Common Issues
Please check out our Troubleshooting Guide before contacting our support.
Folder Name Make sure the name of the folder is cd_radar.
Encrypted Files Do not edit the encrypted files in any way.
Radar Ignores Emergency Vehicles?
eg., if your radar is ignoring emergency vehicles.
This is normal; by design we have made it so the radar ignores emergency vehicles; as during police chases this could get really annoying. So please be aware of this if testing the resource out emergency vehicles aren't being seen by the speed limit radar.
Radar Locking Below The Limit I Set?
eg., if you have your radar to lock vehicles at 70mph but they are locking at 30mph.
This is because you have not set the limit for all 4 cameras. Each camera has its own individual speed limit for locking vehicles. Set them all to the new limit individually.
Radar Not Visible But I Have The Correct Job/perms?
eg., if you are confident you have the correct job/perms, but the radar still isn't visible when in a vehicle.
This is because the radar is set to only be visible when you are in an emergancy vehicle. To test this theory, spawn in a default gta police car (/car police), then it should work. If a default gta police car works, but your custom police car does not, then the vehicle class for your custom car is not set as an emergancy vehicle (VC_EMERGENCY) in the vehicles.meta.
I'm Not Able To Add Plates To The Radar's Database?
eg., if you are trying to add plates to the radar's database manually or through another script but it doesn't get added and there are no errors.
The most common reason for this is because you do not have permission to use the radar (your job is not in the Config.AllowList table in the config.lua). The only way the script will allow you to add a plate to the radar's database is if your job has permission or the event is being triggered from the server side. There will be no visible error if you try to add a plate to the radar's database without proper permissions.
Error Codes
If you see an error code not listed below please open a script support ticket in the Codesign Discord.
Changelog
Files Changed
Not every update requires replacing the entire folder. To avoid redoing your configs, use the option that applies
| Key | Meaning |
|---|---|
| Full Re-Download Required | Delete the old folder and replace it with the latest version. Reuse your config.lua unless told otherwise. |
| Update Specific Files | Only the files listed below need to be replaced. |
| Config Update Required | Your config.lua must be updated for this version. |
| Requires Auto SQL Enabled | Enable Config.AutoInsertSQL in config.lua to apply required database updates. |
Skipping Updates
If you’ve skipped previous updates, it’s recommended to update all files to avoid issues.
For example, if you're on v4.0.1, skipped v4.0.2, and are updating to v4.0.3, use the Full Download option.
Important
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.
v1.0.7
Released: 20/04/2026 Update Specific Filesfxmanifest.lua
client/client.luaChangelog:
Fixed
- Fixed the radar UI opening and not closing after interacting with garage, dispatch or any codesign UI while having cd_bridge installed.
v1.0.6
Released: 02/09/2025 Update Specific Filesfxmanifest.lua
client/client.luaChangelog:
Fixed
- Significantly improved the radars vehicle detection.
v1.0.5
Released: 03/05/2023 All Files ChangedChangelog:
Added
- Added Turkish locales thanks to Lumisaphy.
- Added pre-configured notification events/exports for some notification scripts that are auto-set by the auto_detect.
- Added "Config.ClearDatabaseOnRestart" config option to delete the BOLO/spaner database on script start.
Updated
- Optimised the events and data that sync the radar's database.
- Error codes will now tell you which script the errors came from for easier debugging.
- Removed unnecessary script start prints.
Fixed
- Fixed the radar database not sometimes syncing when joining the server off-duty and then going on duty on QBCore.
v1.0.4
Released: 15/03/2023 Update All Files Config Update Not RequiredChangelog:
Added
- Added pre-configured cd_dispatch integrations.
Fixed
- Fixed some minor issues with the discord webhook.
v1.0.3
Released: 09/02/2023 Update All FilesChangelog:
Added
- Auto Framework Detection - We have added a new feature we are calling 'auto_detect', which will automatically identify your framework resource and framework notifications and apply the appropriate default settings.
- Multiple Choice Permissions Access: With this new feature, you are no longer forced to choose 1 way of adding permissions, you can use multiple all at the same time. You can choose from the framework's job, discord roles, ace perms and identifiers all at the same time!
Fixed
- Fixed the errors when removing a bolo/spaner.
- Fixed the errors with owner check.
v1.0.2
Released: 06/02/2023 Update All FilesChangelog:
YOUR RADAR DATABASE WILL BE DELETED IF YOU DON'T READ THIS.
Copy all of the data inside the [radar_database.txt] file and paste them inside the [JSON Files/radar_database.json] file.
Added
- Added
Config.UseFrameworkDutySystemso you can choose whether you want to use your framework's built-in duty system.
Updated
- Updated the debug prints.
- The remove bolo/spaner event now only requires the plate to be sent instead of the whole table.
- Removed the SQL query to get a character name on esx and replaced it with the ESX getName function.
Fixed
- Fixed the radar database not being synced when switching jobs.
- Added an auto fix for the QB-shared vehicle misconfigured files.
- Fixed some locales on the UI.
v1.0.1
Released: 15/08/2022 Update All FilesChangelog:
Added
- Added configurable debug prints.
Updated
- Cleaned up some of the unused/unneeded code.
Fixed
- Fixed an issue with the standalone perms checks.