JG Docs
Handling

Installation

HandlingJG HandlingPurchase on the JG store

Download & unzip

Unzip the jg-handling-bundle and open it.

Add the resource to your server

Drag the script folder (jg-handling) into a new folder called [jg] within your server's resources folder.

Install dependencies

Make sure you have the latest versions of ox_lib & oxmysql installed on your server.

Update your server.cfg

Inside of your server.cfg, add a new line after all your other resources have started:

ensure [jg]

Configure the script

Inside the config folder, config.lua is the core configuration - most integrations are detected automatically, including framework (optional) and notifications. You'll mainly be adjusting the script's functionality, such as the job lock and timing tool features.

Exporting your changes

Use Preview while adjusting a vehicle. Preview applies the changes for testing, but does not save them to the vehicle resource or database.

When the handling is ready for your production server, select Export, choose handling.meta (XML) and copy the exported XML. Open the existing handling.meta inside the vehicle resource and make a backup before editing it.

If the file contains more than one vehicle, find the existing <Item type="CHandlingData"> block with the same <handlingName> as the exported data. Replace that block only, then save the file and restart the vehicle resource.

Do not use Apply Handling as the main setup for a fleet. It can save an override for one plate or every vehicle of the same model in the database, but this does not update the vehicle resource. Plate overrides must be managed per vehicle, while model overrides are stored separately from the resource. Replacing the matching data in handling.meta keeps the base handling with the vehicle and applies it to every vehicle that uses that handlingName.

See Exporting Your Changes for the full export steps and JG Mechanic tuning config options.

Troubleshooting

Last updated 20 August 2026

On this page