Database

msk_garage stores vehicles in the standard ESX owned_vehicles table. It does not ship an .sql file — the additional columns it needs are created automatically on the first start.

Auto-migration

On onResourceStart the script runs an idempotent migration (ADD COLUMN IF NOT EXISTS), so it is safe to run repeatedly and never touches existing data:

ALTER TABLE owned_vehicles
    ADD COLUMN IF NOT EXISTS `garage`       varchar(60) NOT NULL DEFAULT 'A',
    ADD COLUMN IF NOT EXISTS `fuel`         TINYINT NULL DEFAULT 100,
    ADD COLUMN IF NOT EXISTS `name`         varchar(60) DEFAULT NULL,
    ADD COLUMN IF NOT EXISTS `isFav`        TINYINT NOT NULL DEFAULT 0,
    ADD COLUMN IF NOT EXISTS `deformations` longtext DEFAULT NULL;

The garage column default is set from Config.DefaultGarage (shown as 'A' above).

No manual import

You do not need to import any SQL by hand. Just make sure the base ESX owned_vehicles table exists (it ships with ESX Legacy).

Columns used by msk_garage

Column	Type	Set by	Purpose
owner	varchar	ESX	Player identifier (or society_<job> for shared job vehicles).
plate	varchar	ESX	License plate. Stored padded or trimmed — the script matches both.
vehicle	longtext	ESX / garage	Vehicle properties JSON (mods, colors and engine/body/tank health, dirt).
type	varchar	ESX / garage	Vehicle category (car, truck, boat, helicopter, aircraft, …).
job	varchar	ESX	Job that owns the vehicle (empty / civ for civilian cars).
stored	tinyint	garage	1 = safely parked (shown in garage), 0 = out in the world (shown in impound).
garage	varchar(60)	garage	Which garage the vehicle was parked in (used when Config.Parking = 'specific').
fuel	tinyint	garage	Fuel level at park-in.
name	varchar(60)	garage	Custom nickname set by the player.
isFav	tinyint	garage	1 if the player marked the vehicle as a favourite.
deformations	longtext	garage	Visual body deformation JSON (see VehicleDeformation).

Column name mapping

type, job, stored and the civilian marker (civ) are read through Config.MySQL, so you can adapt them if your owned_vehicles schema uses different column names:

Config.MySQL = {
    type   = 'type',
    job    = 'job',
    stored = 'stored',
    civ    = 'civ',
}

What "condition" is stored where

• Mechanical condition (engine / body / tank health, dirt level, mods, colors, plate) lives inside the vehicle properties JSON.
• Visual deformation (the actual dents) lives in the separate deformations column and is only filled when the VehicleDeformation resource is running.

Both are captured on park-in and restored on park-out for garages and impounds.