01 / OVERVIEWWhat it does
- Type
- Vehicle-control menu that works without a framework
- Main controls
- In-vehicle touchscreen and nearby key fob
- Defaults
- /vehcontrol on U · /keyfob on K
Players open one small touchscreen inside a vehicle. The buttons and artwork change for cars, boats, helicopters, planes, commercial vehicles, motorcycles, and other supported vehicle types, while normal driving or flight controls stay available.
Outside the vehicle, a matching key fob controls the last nearby vehicle the player drove when the configured key system allows it. The script works by itself, with optional connections for notifications, vehicle keys, Qbox audio, San Andreas Radio, and shared vehicle state.
What you can change
These are the main parts you can adjust for your server. The setup guide lists every option and example.
- Commands, keybinds, locale, and interface frame
- Passenger permissions and control availability
- Cruise, collision cancellation, and adaptive following
- Plane autopilot, helicopter waypoint travel, and hover
- Key script, fob range, animation, and sound
- Notification script and Qbox audio
- Blocked vehicle types and per-model control changes
- Which vehicle settings are shared and how the server checks updates
- Keeping San Andreas Radio power in sync
See every setup option →What it works with
- Server framework
- No framework requiredQboxQBCore
- Base
- FiveM; no mandatory framework dependency
- Resource name
- Must remain drs_vehcontrol
- Shared state
- OneSync and networked vehicles
- Optional
- Qbox, QBCore, ox_lib, vehicle keys, San Andreas Radio
- Also works with
- Vehicle key providersQbox audio
See all requirements and setup options →Technical details3 details+
- Runtime
- FiveM Lua with optional OneSync state bags
- Interface
- HTML, CSS, JavaScript NUI, and local player settings
- API
- Client/server exports plus integration events
