Common Issues

#Incorrect VIN Number

If you have another resource with a VIN number in your database, such as a vehicle registration script, you need to match the VIN number length in the config to the VIN number length in your vehicle registration script.

VIN numbers have to be longer than an entity handle. This is roughly 7-8 digits. A minimum of 10 for the length is required. We recommend not changing the default value assigned, which is 17.

#Vehicle Damage Not Saving

If the vehicle deformation is not saving and appears to be repaired every time you park and take it out, make sure that all dependencies are started. We utilize zyke_realisticvehicles to save and apply deformation. This deformation is primarily visible, and doesn't have any effect on engine health etc.

#Missing Default Impound

We require you to have an impound for your "default" impounder, which is simply the first job mentioned in the impound list in the config. When a vehicle doesn't exist by any means, but has been taken out, we store them at an impound for easy retrieval, which is the default one. By not having an impound for your default impounder job, we can't properly default it within our menus.

Simply create an impound for your default impounder to resolve this warning.

#Vehicle Key or Engine Issues

Starting with Garages 2.6.0, the selected vehicle-key provider owns runtime key checks and engine controls. Confirm the active provider in zyke_lib/dependency_override.lua:

lua
vehicleKeys = "zyke_vehiclekeys",

When using Vehicle Keys, follow its Common Issues page. For another provider, check that resource's documentation and support.

Fuel, HUD, gear, and vehicle-management resources can also call SetVehicleEngineOn directly and override the selected key system. Avoid running competing engine-control loops.