Common Issues

#Another Key Resource Is Running

Vehicle Keys provides compatibility names for qb-vehiclekeys, qbx_vehiclekeys, qs-vehiclekeys, and wasabi_carlock. Do not start the original resource alongside Vehicle Keys under one of those names.

Running two key systems can cause duplicate grants, conflicting lock or engine state, and events being handled by the wrong resource.

#Garages Cannot Find the Key Provider

Start Vehicle Keys before Garages and select it in zyke_lib/dependency_override.lua:

lua
vehicleKeys = "zyke_vehiclekeys",

cfg
ensure zyke_lib
ensure zyke_vehiclekeys
ensure zyke_garages

#Stored Vehicles Are Missing From the Vehicle List

Standalone Vehicle Keys lists accessible vehicles that currently exist in the world. Stored or offline vehicles require a menu provider.

With Zyke Garages, set:

lua
Config.Settings.vehicleActions.menuProvider = "zyke_garages"

and start Garages after Vehicle Keys.

#A Physical Key Was Not Received

Confirm the inventory item name matches Config.Settings.keys.item, the item supports metadata, and the player has space.

When the full-inventory fallback is enabled, automatic grants can be retried with /getkeys until the configured expiry. A manual export still returns false, "noInventorySpace" so the calling resource can decide how to handle it.

#Engine Starts or Stops Unexpectedly

Fuel, HUD, vehicle management, handling, or other scripts may call SetVehicleEngineOn directly. A native call from another resource can override the state Vehicle Keys requested.

Search the server resources that manage engines, gears, fuel, or vehicle entry. Disable their engine-control behavior or integrate it with Vehicle Keys instead of running competing loops.

#Keys Fail After a Plate Change

Permanent plate changes must call:

lua
exports["zyke_vehiclekeys"]:RenamePlate(oldPlate, newPlate)

Changing only the visible native plate does not update the key identity. If another resource uses fake plates, keep the real canonical plate in Entity(vehicle).state.plate.