Most drift scripts are a menu. You open it, pick an option, and the car handles differently. This one makes your mechanics do the job.

The swap is the roleplay

Fitting drift tyres means jacking the car, taking the wheel off, and mounting the new one — a sequence of short minigames rather than a dropdown. Balancing runs on a purpose-built wheel balancer, and getting it wrong is a thing that can happen. Tyres and the jack are bought from an in-world shop, so a workshop has to stock itself before it can trade.

Handling that stays compatible

The drifting comes from in-game physics functions and maths, not from rewriting handling.meta. That distinction matters: the car does not get faster, and anything else you run that touches vehicle handling or performance keeps working. Pull up to an air compressor — most garages and filling stations already have one — and let air in or out to trim traction to the driver's taste.

The lift

A two-post lift that actually raises the car, with vehicles staying physical while they are on it. Add as many as your workshop needs, and on ESX or QBCore restrict individual lifts to specific jobs so the public cannot put a car in the air.

What it costs you to run

Idle it sits at 0.00–0.01ms, around 0.01–0.03ms while driving on drift tyres, and only climbs while a wheel is actually being changed. State bags carry the sync, so the server side stays light. Fitted tyres and pressures persist in the database.

Fitting it in

Runs standalone or on ESX, QBCore, Qbox and VRP. Target integration is optional, vehicle classes can be whitelisted or blacklisted so nobody puts drift tyres on an ambulance, and an exposed API fires on each event for hooking into your own systems.