Vehicle Keys
Use JG Vehicle Keys with the HUD engine controls
Connect the HUD's engine controls to Vehicle Keys so starts follow your key and immobiliser rules.
Use a compatible HUD build with Config.VehicleKeys support. Its engine integration must pass a vehicle entity number to SetEngineState, not a table containing netId. Vehicle Keys must include SetEngineState and PutAwayKey. See the client API for these contracts.
Install both updates
Update jg-hud and jg-vehiclekeys together. Complete the Vehicle Keys installation.
Keep the compatible build's Framework.Client.ToggleEngine and Framework.Client.OnVehicleEnter functions in jg-hud/framework/cl-functions.lua.
The entry function puts away held keys and closes the fob before showing the speedometer. Ground inspection returns the key to the ground.
Configure the HUD
Open jg-hud/config/config.lua and set:
Config.VehicleKeys = "auto"
Config.EngineToggleKeybind = "G"
Config.VehicleControlKeybind = "F6"Config.VehicleKeys defaults to "auto". The HUD uses Vehicle Keys while jg-vehiclekeys is started. Otherwise, it uses its standard engine controls. Set "jg-vehiclekeys" to always use that integration, or "none" to use the standard controls.
Choose the Vehicle Keys engine inputs
In jg-vehiclekeys/config/config.lua, the engine command and keybind default to:
Config.Commands.engine = "engine"
Config.Keybinds.engine = "G"Set either option to false to disable that input independently.
When the running HUD has an engine shortcut on the same key, Vehicle Keys leaves that shortcut to the HUD. /engine remains available. Different keybindings can both remain active.
Check your start order
In server.cfg, start jg-vehiclekeys before jg-hud, after your framework, inventory, ox_lib and oxmysql:
ensure jg-vehiclekeys
ensure jg-hudIssue your test character a key through /vehiclekeysadmin. Physical modes require the inventory key; Virtual requires issued access.
Restart and test
Fully restart your server. Test G and the F6 engine button from the driver's seat with and without a valid key. Both should respect key access and any Ghost PIN requirement.
Check that entering a driver or passenger seat closes the fob and puts away the key. Repeat during ground inspection; the key should return to the ground.
Custom engine checks
Framework.Server.CanToggleEngine in jg-vehiclekeys/framework/sv-functions.lua can refuse manual engine changes, including HUD controls. It also gates automatic and hotwired starts. It doesn't replace the core access checks or control fob remote starts.
Last updated 5 November 2026