Vehicle Control

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.

Buy Here

FiveM Forums Post

YouTube Showcase Video

YouTube Walkthrough Video



Step 0 - First Steps

1. Download your resource from FiveM’s Keymaster.

2. Unzip the folder and place this folder in your server's resource folder.

3. Add the resource to your server start config (server.cfg): ensure cd_vehiclecontrol. 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_vehiclecontrol

Step 1 - Fxmanifest

Depending on your framework and dependencies, you may need to make some changes to the [cd_vehiclecontrol/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_vehiclecontrol/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 Framework and Important sections at the top of the config.lua. Everything else is optional.

NEW: Auto Framework Detect!

Introducing our new 'auto_detect' feature! It automatically identifies your Framework and applies the appropriate default settings.

Step 3 - Configure Key Binds

Before starting this resource on your main/live server, we highly advise you to configure 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_vehiclecontrol/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.

Step 4 - Vehicle Lock

What is the vehicle lock display?

This clickable button on the UI allows players to lock/unlock their vehicle from the UI itself.

Do you want to use the vehicle lock display?

NO = You can skip this step.

YES = A few small modifications are required; read below for more information.

  1. Enable Config.VehicleLock in the [configs/config.lua] file.

  2. This screenshot shows the 2 functions that must be modified in the [configs/client_customise_me.lua] file. Read the ”commented out help text” for further information.

Do you use cd_garage and its built-in keys feature?

Then you don't need to make any changes. We have already pre-configured this for you.


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.



Open the vehicle control's UI.

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.



Open the vehicle control's UI.


These events are completely optional; you can use them if needed.

Open the UI

Open the vehicle control's UI.

Close the UI

Close the vehicle control's UI.


Please check out our Troubleshooting Guide before contacting our support.

🔔 Folder Name Make sure the name of the folder is cd_vehiclecontrol.

🔔 Encrypted Files Do not edit the encrypted files in any way.

Some extras such as lightbars not working?

eg., the lightbar extra for example can be toggled off, but when toggled back on it's not visible.

✔️ Sometimes extras such as lightbars will only be visible if the car is fully repaired first.

To fix this you can set Config.Extras.extras_workaround_fix to true in the configs/config.lua.

There is a downside with this though; because to overcome this issue we fully repair the vehicle. After the extra has been enabled we re-aply most of the damage such as broken doors, broken windows and popped tyres. But we are unable to re-apply the minor visual body damage such as dints, bumps or scratches. So some players may abuse this to repair minor visual body damage on their vehicles.


If you see an error code not listed below, please open a script support ticket in the Codesign Discord.



Files Changed

Not 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 delete your old cd_vehiclecontrol folder, download and add in the latest version, reconfigure 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.lua file 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 Type

On 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.

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.


Files Changed:

Update Type:



  • Development Stage: COMPLETE

  • Alpha Test Stage: COMPLETE

  • Beta Test Stage: COMPLETE

Last updated