Resource Description
How the lifts, arms, and power unit work.
#Two-Post Lift
Each lift has two posts with a carriage on each, four arms with screw pads, a power unit on the right post, and a lock release. The carriages travel by the server's clock, so every player sees the carriages and the car at the same height. The motor runs and the locks click as the carriages pass them.
Props stream in within 90 metres. Nothing runs every frame while a lift stands still.
#Setting the Arms
With the lift all the way down, players drive a car between the posts and open the arm view from either carriage. They drag each pad under the marked jacking point at its corner, where it snaps into place. A pad pulled well away comes off again.
The car must stand square between the posts, be empty and standing still, and be a regular automobile.
#Raising & Lowering
The carriages stop at three heights on the way up, each on the nearest lock of the posts:
| Stop | Height |
|---|---|
| Low | The car's sills at low, for work on a creeper. |
| Waist | The car's wheel hubs at waist, for wheels and corners. |
| High | The car's sills at high, to walk under. |
Players can also send the carriages straight to the top or the bottom. Carriages let go of between two stops come down onto the lock below.
A lift only goes up with all four pads under the car, or empty with every arm parked against its post. An empty lift travels between the bottom and the top of the posts.
#Placing Lifts
Lifts that always stand go in shared/lifts.lua. Admins can place a lift where they stand until the next restart, and the command prints its line for shared/lifts.lua. Other resources place their own lifts with CreateLift, optionally inside a routing bucket so each instanced interior can have its own.
A lift goes when the resource that made it stops. A car up on it stays up for 15 seconds, so a resource that restarts and places the lift again keeps the car where it was. Otherwise, the car is set down on its wheels.
#Interactions
The power unit and the arms are used through zyke_lib interaction markers by default. Target-based interactions through ox_target or qb-target are optional.
#Integrations
Every action is server-authoritative. Other resources can refuse work on a lift, hold a car no lower than a given stop, keep a car frozen once it is lowered, tilt the car on the pads, and keep the player off the lifts while they are busy. Server events report lifts moving and cars lifted or lowered. See Exports & Events.