Midnight Vehicle Control Menu

Midnight Vehicle Control is a standalone script that provides a simple and intuitive interface to manage your vehicle controls in your FiveM server.

Buy Here

FiveM Forums Post

YouTube Walkthrough Video

---

SUPPORTED FRAMEWORKS

All frameworks are supported as this script is fully standalone

INSTALLATION GUIDE

1

Adding the Resource to Your Server

1. Download the resource from your FiveM Keymaster.

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

3. Ensure the script in your server.cfg file by writing ensure md_vehiclecontrol, (or make sure the script is placed in a folder that is already ensured)

4. Follow the next step to configure your fuel setup, and that is all!

2

Setting Up Fuel Scripts To Read Vehicle Fuel

The vehicle control UI displays the amount of fuel a vehicle has. By default, the script will be standalone, using the FiveM native to retrieve the fuel level for the vehicle.

If you wish to use a fuel script, you need to specify the script in the config file, by editing the following line.

If you do not wish to use any fuel script, simply set the config to 'none' or 'standalone'. You are now done setting up the script.

shared/config.lua

-- The fuel script you wish to use. 
-- The script comes with support for cdn-fuel, legacy-fuel and standalone functionality. Check documentation for more info
Config.FuelScript = 'none'    

We have configured this script to be compatible with cdn-fuel and legacy-fuel, straight out of the box.

• If you are using cdn-fuel, set this config to 'cdn-fuel'

• If you are legacy-fuel, set this config to 'legacy-fuel'

If you are using any other fuel script, you must set this config to 'other' and configure the GetFuelLevel(veh)function in[shared/functions.lua]

shared/functions.lua

function GetFuelLevel(veh)
    --standalone
    if Config.FuelScript == 'none' or Config.FuelScript == 'standalone' then 
        return GetVehicleFuelLevel(veh)

    --cdn fuel script
    elseif Config.FuelScript == 'cdn-fuel' then 
        return exports['cdn-fuel']:GetFuel(veh) 

    --legacy fuel script
    elseif Config.FuelScript == 'legacy-fuel' then
        return DecorGetFloat(veh, '_FUEL_LEVEL') 
    
    elseif Config.FuelScript == 'other' then
        -- If you are using any other fuel script, just add the code that gets the fuel amount right here
        -- Make sure the fuel amount is RETURNED as a number between 0 and 100 
    end
end

The comments are self explanatory. If you are using a fuel script other than cdn-fuel or legacy-fuel, you should place the code that returns the vehicles fuel amount in the last elseif statement If the fuel script you use is limited to a certain framework, this script will be too.

3

Setting Up Any Restrictions to Opening The Menu

By default, anybody in the vehicle can open the menu (with passengers having limited access compared to the driver). However, in certain situations, such as when a passenger may be in handcuffs, you may not want them to be control the vehicle. To account for any restrictions similar to these, you can edit the openCCAfterCheck(veh)function in[shared/functions.lua

shared/functions.lua

-- If you want to add any restrictions/conditions for opening the vehicle menu, you can add them here
function openCCAfterCheck()
    openCC() -- This will actually open the menu, so add your conditions before this
end

4

All Done!

---

INFORMATION AND CONFIG OPTIONS

Default Key Binds

A default keybind can be assigned to all players to open and close the script. This is configurable in the config file

shared/config.lua

-- The default keybind used to open/close the vehicle control menu
-- Set this to nil  if you dont want a keybind to be used
Config.DefaultKeybind = 'lshift'

As mentioned in the comments above, setting the default keybind to nil (not 'nil') will completely remove the key mapping. This is ideal if your server is already overloaded with keybinds from various scripts. This will mean that players will either have to use commands, or you must provide alternative methods using exports/events (mentioned later in this documentation)

IMPORTANT NOTE

Our script uses keymapping as an optimized alternative to continuously listening for keypresses every tick. This method allows players to map a keybind to a command, which they can configure individually under Settings > Key Bindings > FiveM, just like any other game keybind.

When the resource is first started on your server, the default keybind from the config file will be applied to all players. However, if a player customizes their keybind through the settings, their chosen keybind will remain unchanged even if the default keybind in the config is later updated. The updated default keybind will only apply to players who have not yet played on the server. Codesign has good documentation on this topic. https://docs.codesign.pro/coding-information/register-key-mapping

Chat Commands

Players can use commands in the chat to open, close and toggle the vehicle control UI. The default commands are listed below.

Command	Description
/openCC	Open Vehicle Control Menu
/closeCC	Close Vehicle Control Menu
/toggleCC	Toggle Vehicle Control Menu

You may change these commands in the config file

shared/config.lua

-- Commands used to open, close and toggle vheicle control UI
Config.OpenCommand = "openCC"
Config.CloseCommand = "closeCC"
Config.ToggleCommand = "toggleCC"

Events

The events used to open and close the vehicle control UI. These can be called from any script, such as a radial menu.

TriggerEvent("md_vehiclecontrol:open") -- open vehicle control
TriggerEvent("md_vehiclecontrol:close") -- close vehicle control

Exports

If you would like to use exports rather than events

exports['md_vehiclecontrol']:open() -- open vehicle control
exports['md_vehiclecontrol']:close() -- close vehicle control

Other Config Options

Refresh Time

This config determines how frequently the vehicle control UI will be updated, defining the delay time in miliseconds between each update tick. For example, if a door is torn off a vehicle, a lower refresh time will cause the UI to disable the corresponding door button more quickly. However, it's important to note that while a shorter refresh time improves responsiveness, it will also consume more server resources. The default value of 500ms will result in a good balance between responsiveness, while consuming 0.02 to 0.04 resmon (while the UI is open)

shared/config.lua

-- Time in ms between each UI update. Lowering this will result in a more responsive UI, but will consume more resources
Config.RefreshTime = 500      

Utilizing a Separate Neon/Headlight Controller Script

There are many advanced neon and headlight controller scripts developed by FiveM scripters (including our very own advanced controller script, coming soon!). The vehicle control menu includes a basic neon and headlight controller with simple toggle functionality and the ability to change colors.

If you have a more advanced script for handling neons installed on your server, you can set the Config.HideNeonControl configuration option to true. Doing so will hide the built-in controller from this script, helping to avoid feature duplication and reduce repetitiveness in the user interface. Same can be done for headlights

shared/config.lua

-- If your server has a seperate controller/tuner script to handle neons, you can disable them in this script
Config.HideNeonControl = false

-- If your server has a seperate controller/tuner script to handle headlights, you can disable them in this script
Config.HideHeadlightControl = false

Allowed Controls

Controls that will be registered while the NUI is active (so that you can actually still utilize the vehicle while the control UI is open)

shared/config.lua

-- Keyboard controls that are enabled while the vehicle control UI is open. 
-- See https://docs.fivem.net/docs/game-references/controls/ for all keys
Config.AllowedControls = {
    75,  -- exit vehicle
    71,  -- accelerate vehicle
    72,  -- deccelerate vehicle
    59,  -- turn vehicle left/right
    86,  -- honk
    74,  -- toggle headlight
    101, -- open vehicle roof
    76,  -- handbrake
    245, -- open chat
    85,  -- use radio
}

Passenger Vehicle/Window Control

For most vehicles, passengers can typically control their own windows and doors. However, for larger vehicles like buses, prison buses, tour buses, and other similar types of buses, it would be more realistic for passengers to have no control over the windows or doors. This configuration allows you to specify which vehicles this rule should apply to. To add a vehicle, add the MODEL NAME of the vehicle from the FiveM Vehicle Reference (in capital letters)

shared/config.lua

-- See https://docs.fivem.net/docs/game-references/vehicle-models/ for names of vehicle models 
-- Vehicles that pasengers should have no control of any windows, whatsoever
Config.NoPassengerWindowControl = {  
    "BUS", "AIRBUS", "COACH", "PBUS", "PBUS2", "TOURBUS", "RENTALBUS", 
}

-- Vehicles that pasengers should have no control of any doors, whatsoever
Config.NoPassengerDoorControl = { 
    "BUS", "AIRBUS", "COACH", "PBUS", "PBUS2", "TOURBUS", "RENTALBUS", 
}

---

Support

Join our Discord for support. You can create a ticket for assistance or general inquiries.