wasabi_carlock
Advanced Car Lock V3 is a vehicle key, locking, and security system for FiveM, with physical or virtual keys, vehicle controls, theft minigames, locksmith services, and police alerts. This documentation covers version
3.0.0.
danger
Keep the resource folder named wasabi_carlock. Inventory item exports and third-party integrations use this name.
Features
- Physical and virtual keys — Plate-specific inventory keys and electronic fobs, with virtual-key fallback when no inventory bridge is registered.
- Remote locking and ignition — Keybind, command, and inventory-key locking, configurable animations and sounds, and key-required engine access with ignition bypass rules.
- Vehicle control interface — Compact and full phone-style views with a 3D vehicle display, fuel and engine-health telemetry, doors, windows, seats, headlights, hazards, and neon controls.
- Security profiles — Standard and high-end profiles select key items, access tools, hotwire methods, and tracker eligibility by vehicle class or model override.
- Theft minigames — Multi-stage lockpicking with tension and strain, wire matching and ignition sparks, and a Flapper Device ECU sequence minigame for high-end vehicles.
- Locksmith services — Duplicate physical keys with materials or payment, or reprogram an existing key for a nearby vehicle. Services can be marked illegal and trigger police alerts.
- Key sharing — Transfer keys to nearby players; virtual-key mode includes give-key and management menus.
- Vehicle tracker — Locate eligible spawned vehicles in the same routing bucket, set a waypoint, and request a remote alarm. Locking still uses normal range limits.
- NPC interactions — Rob eligible drivers at gunpoint, recover keys from the original dead driver in the resistance flow, or request assistance with an authorized job.
- Vehicle searching — Search through the no-key driver flow for a chance at money, items, or a spare key.
- Police alerts — Wasabi MDT V2, ps-dispatch, cd_dispatch, or internal dispatch, plus native or custom alarms.
- Admin tools — Framework-permission-restricted command to grant a key for the occupied vehicle.
- Open integration files — Framework, inventory, interaction, listener, and minigame bridges, plus client/server exports.
- Localization — 15 shipped locale files with English fallback.
Supported frameworks
- ESX (
es_extended) - QBCore (
qb-core) - Qbox (
qbx_core) - Ox Core (
ox_core)
See Dependencies for inventory and interaction providers. Feature availability depends on the active bridge and configuration; for example, NPC job assistance uses ESX/QB/QBX job data.
Main configuration areas
| Area | File | Purpose |
|---|---|---|
| Shared | config/shared/config.lua | Keys, profiles, minigames, locksmith, search, NPC interactions, alerts |
| Client | config/client/config.lua | Interaction provider, appearance, engine behavior, vehicle controls, ignition bypass |
| Server | config/server/config.lua | Update checks, NPC locks, admin command, validation settings |
| Vehicle names | config/shared/vehicle_names.lua | Custom vehicle display names |
| Inventory setup | _invItems/data.lua, _invItems/images/ | Provider-specific item definitions and images |
| Bridges | bridge/** | Integration adapters and editable listeners |
| Locales | locales/*.json | Translated UI and notification strings |
Start with Installation, then review Configuration and Gameplay. Developers should use the current Exports rather than legacy key-system signatures.