Common Issues

#Lift Props Do Not Appear

Props stream in within 90 metres of the lift. A lift placed with a bucket is only seen from that routing bucket. A lift placed with /vehiclelifts lasts until the server restarts; paste its printed line into shared/lifts.lua to keep it.

#Lifts From Another Resource Disappear After a Restart

Vehicle Lifts forgets other resources' lifts, rules, and trims when it restarts. Place them again on onResourceStart; see Create Lift.

#Arms Cannot Be Set

Lower the lift all the way first. The car must stand square between the posts, be empty and standing still, and be a regular automobile. Only one player can set a lift's arms at a time, and nobody can be working its power unit. Check the Can-Check Hooks and any busy checks from other resources.

#Lift Will Not Go Up

All four pads must be under the car, or every arm parked against its post for an empty lift. Nobody can be in the driver's seat as the car is taken up, and the car must not have moved since the arms were set. Another resource's rule can also refuse with its own message.

#Lift Will Not Come Down Further

Another resource's rule holds the car no lower than a given stop, such as while a wheel is off. Its message tells you what is needed.

#Car Stays Frozen After Lowering

Another resource's holdFrozen rule kept the car frozen as it was lowered. Vehicle Lifts does not unfreeze it later; the resource that holds it releases it.

#Interaction Markers or Target Options Do Not Appear

Check interaction. With "target", ox_target or qb-target must be running and configured in zyke_lib; otherwise, the console warns and interaction markers are used. With "point", look at a marker from within reach, on foot.