Changelog

1. Back up and prepare

These steps update sky_mechanicjob from 1.37.0 to 1.38.0. Complete earlier guides first if your installed version is older.

1. Download and extract the 1.38.0 package.
2. Back up your game database, server configuration and installed sky_mechanicjob folder.
3. Stop the server. Complete the Base 1.49.0 update and Jobs Base 1.52.0 update during the same maintenance window. Mechanic 1.38.0 loads its delivery modules from Jobs Base 1.52.0, so install them together.

2. Copy the package files

Inside your installed sky_mechanicjob folder:

1. Delete the old source/ folder and copy the complete new source/ folder from the 1.38.0 package.
2. Replace fxmanifest.lua with the matching downloaded file.
3. Replace config/locales/ with the complete downloaded folder. For custom translations, compare the backup with the new language file and copy only your edited wording into matching keys; retain the new keys.

Keep your existing config/config.lua, config/adv_config.lua, provider functions, item definitions, images and models.

3. Keep or configure settings

Keep your existing jobs, prices, procurement rules, parts catalogue, collection points and carry-item settings. No Mechanic configuration change or settings import is required.

If /jobconfig is enabled, its saved settings remain in use; do not import the shipped defaults over them. If Config.UseJobConfigurator = false, keep your existing Lua values unchanged. The updated shop does not require recreating your catalogue or delivery locations.

4. Database, items and assets

The Jobs Base 1.52.0 update adds the delivery-reservation field to the existing sky_mechanic_part_deliveries table. With Config.AutoExecuteQuery = true in Jobs Base, let its migration finish during startup. With that switch disabled, complete the manual database branch in the Jobs Base guide before startup: on MariaDB, run the new sky_jobs_base/import.sql; on an existing MySQL 1.51.0 database, open sky_mechanic_part_deliveries in your database editor, check for claim_reservations, and add it only when absent as a nullable LONGTEXT column with default NULL. Keep existing columns and rows. Do not run the MariaDB full import on MySQL.

There is no additional Mechanic SQL migration. Keep existing orders, deliveries and storage data. No new items, inventory images or models are required.

5. Start and check

1. Start the database connector, framework and selected inventory, banking, targeting and other providers in their normal dependency order. Then start sky_base 1.49.0, sky_jobs_base 1.52.0 and sky_mechanicjob 1.38.0.
2. Resolve the first startup or migration error before allowing players back. Reconnect to load the new interface.
3. With an on-duty mechanic, open the Parts Shop, review an existing order and place one small test order. Collect it at the configured workshop point and check the payment, received parts and order history.
4. Test your configured physical carry/pallet or direct inventory delivery mode, including depositing a part into authorised workshop storage. Check ready deliveries again after reconnecting.

1. Back up and stop the server

These steps update sky_mechanicjob from 1.36.0 to 1.37.0. If you are on an older version, complete its earlier update steps first.

1. Download 1.37.0 and extract the ZIP on your computer.
2. Make a full backup of your server files and game database. Also keep a separate copy of the installed sky_mechanicjob folder.
3. Stop the server before replacing files. Put away equipped custom weapons first. Keep the backup until the update has been checked.

Also complete the Base update and Jobs Base update for your installed jobs. They contain the library, database and inventory steps shared by these jobs.

2. Copy the new files

Use the files from the 1.37.0 download throughout these steps. All paths below are inside your installed sky_mechanicjob folder.

1. Delete the old source/ folder. Copy the complete new source/ folder into its place, including its interface files.
2. Replace fxmanifest.lua with the file from the same download.
3. Replace the complete config/locales/ folder with the new one. If you changed any wording, open the backed-up language file beside the new file and copy your edited text into the matching entries. Keep the new translation keys and folders.
4. Keep your existing config/config.lua; make only the settings changes described in step 3 below. Do not overwrite your configured jobs or locations with the download's defaults.

Copy the new import.sql to the same path. The required order-table update is installed through Jobs Base in step 4.

3. Check your settings

Your existing diagnostics stay enabled unless you choose to disable them. Keep your current jobs, parts, prices, delivery locations and permissions.

Using /jobconfig (the default): after starting the updated server, open /jobconfig → Mechanic → your job → Vehicle Diagnostics. Use Enable vehicle diagnostics only if you want to change that job's access, then save. No settings import is needed.

Only if Config.UseJobConfigurator = false and you want to disable diagnostics for a job: open sky_mechanicjob/config/config.lua, find that job inside Config.Jobs, and add this inside its existing job table:

diagnosticsSettings = {
    enabled = false
},

If the block already exists, change its existing value instead of adding another block. Use true to keep diagnostics enabled. This setting does not disable inspections, tuning or general vehicle wear.

The Parts Shop now uses Jobs Base's order system. Keep the existing parts catalogue and collection points. Review that job's online-shop switch and the global Parts Delivery switch if the shop should be available. Existing delivery time and payment settings continue to apply; company payment still needs permission 9 and the job's society account. You do not need to enter the same settings again.

4. Update database, items and models

Complete the database step in the Jobs Base 1.51.0 guide before testing Mechanic. It updates the existing order table without deleting orders. If Jobs Base has Config.AutoExecuteQuery = true, wait for its automatic update at startup. If false, execute the new sky_jobs_base/import.sql in your game database before startup.

Keep sky_mechanic_part_deliveries, existing orders, your inventory items and models. Do not run clear.sql. There are no further new Mechanic items or models to install.

5. Start the server and check

1. Finish the file copies, required Lua edits and database steps, then start the server. Start the framework, database connector and your selected inventory/weather/phone/banking/voice/key providers first. Start sky_base 1.48.0, then sky_jobs_base 1.51.0, then the installed jobs. Wait for database updates to complete. If used together, start DOJ 0.6.0 before Police 1.40.0, and Ambulance 2.47.0 before Crime 0.11.0.
2. Check the server console for startup or database errors. If an error appears, resolve the first error before testing further. Check that this resource reports version 1.37.0.
3. Reconnect so the new interface and models load. If step 3 listed in-game settings, open the named configurator, make those changes and save. Then check your saved jobs and the features you use before reopening the server to everyone.

What to check for this resource: Open an existing order, place one test order and collect it. Check its payment and parts. Test diagnostics for an enabled job and, if configured, a job where you disabled them. Open a saved inspection and the document gallery.

1. Prepare

These instructions cover sky_mechanicjob 1.35.0 → 1.36.0. Complete applicable earlier migrations first if you are upgrading from an older version. Back up the database, resources, custom configuration/translations and saved jobs, roles, locations and /jobconfig data. Test on staging and stop the server before replacing files. Start the framework, database connector and selected inventory, phone, banking and UI providers first, then sky_base 1.47.0 and sky_jobs_base 1.50.0, followed by the installed job resources. If you use DOJ with Police, start DOJ 0.5.0 before Police 1.39.0. If you use the Crime medical integration, start Ambulance 2.46.0 before Crime 0.10.0. Mechanic 1.36.0 and Fire 1.18.0 follow both libraries. Include only resources you have installed.

2. Replace files

Use the complete 1.36.0 customer package. Delete the entire sky_mechanicjob/source/ folder and insert the new one. Replace sky_mechanicjob/fxmanifest.lua from the same download; do not merge old generated interface or bootstrap files. Refresh the complete sky_mechanicjob/config/locales/ tree and merge custom translations without restoring an older dictionary. Preserve the selected locale value in sky_base/config/config.lua.

Merge sky_mechanicjob/config/adv_config.lua using the new blocks below, preserving your existing locations, access rules and custom functions. sky_mechanicjob/config/config.lua has no new option to merge in this release. Install the matching Jobs Base 1.50.0 locale packs as part of the Jobs Base update. The repair/wash illustrations are bundled inside the new interface in source/; no separate inventory image install is needed.

3. Merge settings

Instant repair and wash. In sky_mechanicjob/config/adv_config.lua, add these complete new child tables inside your existing Config.InstantTuning = { ... } block:

    repair = { enabled = true, price = 500 },
    wash = { enabled = true, price = 50 },

Previously all four values were absent. The new defaults are Config.InstantTuning.repair.enabled = true, Config.InstantTuning.repair.price = 500, Config.InstantTuning.wash.enabled = true and Config.InstantTuning.wash.price = 50. Preserve the other fields and configured locations. The unchanged shipped priceMultiplier = 1.25, mechanicOnly = false and allowedJobs = nil continue to control tuning/access; keep your intentional restrictions. No new location is created. Repair and wash are independent; repair-only preserves dirt. Their prices are fixed whole currency amounts and are excluded from the tuning multiplier and subscription discount.

With Config.UseJobConfigurator = true, make any desired changes after the updated server has started and before the gameplay checks. Edit Mechanic Jobs → Instant Tuning with instantTuningRepairEnabled, instantTuningRepairPrice, instantTuningWashEnabled and instantTuningWashPrice. The four new keys initialize from the shipped defaults until you save a different value. Preserve existing feature, location and access overrides, including instantTuningMechanicOnly and instantTuningAllowedJobs; copying this plaintext file does not replace them. With the configurator disabled, the entries above are the active values.

ECU engine software. Add this complete new block to sky_mechanicjob/config/adv_config.lua:

Config.ElectronicTuning = {
    engineTorqueMultipliers = {
        [1] = 1.10,
        [2] = 1.25,
        [3] = 1.35,
        [4] = 1.70
    }
}

The table was previously absent; these four defaults match the previous fixed boosts. Stock remains 1.00, and installed ECU stages 0–4 are retained. 1.00 adds no boost and 1.10 adds 10% torque. Do not rewrite saved vehicle stages as percentages.

With /jobconfig enabled, use Mechanic Jobs → ECU Engine Software: ecuEngineTorqueStage1 = 1.10, ecuEngineTorqueStage2 = 1.25, ecuEngineTorqueStage3 = 1.35 and ecuEngineTorqueStage4 = 1.70. New keys use shipped defaults until an override is saved. Change those four effective values to tune the boosts. With the configurator disabled, edit Config.ElectronicTuning.engineTorqueMultipliers[1] through [4] in the new block.

Keep all saved jobs, grades, permissions, locations and other overrides. No reset or routine import is needed. Use /jobconfigimport sky_mechanicjob only when you intentionally want to import your reviewed plaintext configuration after backing up its replacement scope. It does not install runtime files, SQL or images.

Optional profiling is disabled by default. If support requests a recording, put setr sky_profiler 1 in server.cfg before the Sky ensure lines and perform a full server restart. In the server console, run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-release-20261014.json; choose a new filename for each recording. Disable it with setr sky_profiler 0 and another full server restart. This is not a /jobconfig setting. No recording or upload starts automatically.

4. Database, items and assets

Database: No new Mechanic table, column or manual SQL migration is introduced from 1.35.0. Preserve invoices, payments, orders, refunds, ownership and saved vehicle stages. The ownership fixes use the selected framework's existing vehicle/character tables; do not create ESX tables on a QB/Qbox server or rewrite historical recipients.

Items and permissions: No new inventory item or permission ID is required. Existing repair-kit, ECU, invoice/duty and nearby-customer access rules remain. Present invoice again reuses the original outstanding invoice and its payment history; it does not create a replacement invoice or cancel it when the receipt closes.

Images and assets: Repair/wash pictures ship in the rebuilt interface under source/; no separate consumable registration is needed. There is no new streamed model or map. No non-source removals or renames are needed.

5. Restart and check

Perform a full server restart after all replacements and migrations so manifests and file lists reload, then reconnect clients. Start the framework, database connector and selected inventory, phone, banking and UI providers first, then sky_base 1.47.0 and sky_jobs_base 1.50.0, followed by the installed job resources. If you use DOJ with Police, start DOJ 0.5.0 before Police 1.39.0. If you use the Crime medical integration, start Ambulance 2.46.0 before Crime 0.10.0. Mechanic 1.36.0 and Fire 1.18.0 follow both libraries. Include only resources you have installed. Check the actual installed versions and the first startup/database error before testing.

At an existing instant-tuning location, select repair-only, wash-only and both; verify the fixed service prices in the basket and the result after cash/card payment. Confirm a subscription or tuning multiplier does not discount those service prices. Check the original customer can receive an outstanding invoice again and previous payments remain. Verify vehicle-owner billing and refunds on your actual framework and a character switch, without changing historical invoice recipients.

Inspect engine/body collision damage separately from maintenance wear. Test a Dyno placement on a level workshop floor and move an existing station, then run a stock vehicle test. Confirm the four effective ECU multipliers and check an installed stage while driving on staging. Confirm a failed vehicle-owner repair does not report a completed repair or consume the reserved kit. Open document actions, workshop invoice history, the paint palette and nearby-player invoice selection.

1. Prepare

These instructions cover sky_mechanicjob 1.34.1 → 1.35.0. Complete applicable earlier migrations when upgrading from an older version. Back up the database, resources, framework files, custom configuration/translations and saved /jobconfig/Creator data. Test on staging and stop the server for replacement. Install the coordinated versions for your installed resources. Start the framework, database connector and selected inventory, phone, banking and UI providers first, then Base 1.46.0 and Jobs Base 1.49.0. Start DOJ 0.4.0 before Police 1.38.0 for their shared catalogue and court workflows. Start Ambulance 2.45.0 before Crime 0.9.0 when using their medical integration. Mechanic 1.35.0 and Fire 1.17.0 follow both libraries. Include only installed resources.

2. Replace files

Use the complete 1.35.0 customer package. Delete the entire sky_mechanicjob/source/ folder and insert the new one, then replace sky_mechanicjob/fxmanifest.lua from the same package. Refresh the complete sky_mechanicjob/config/locales/ tree and merge custom translations. Preserve your selected language. Do not restore an older bootstrap or merge generated interface files.

Merge config/config.lua and the updated Config.Functions.GetVehiclePurchasePrice implementation in config/sv_functions.lua, retaining deliberate custom API hooks. Add compat/jg_hud_mileage.lua and update the supplied README.md. Keep the matching manifest and complete generated source together.

3. Merge settings

When Config.UseJobConfigurator = true, saved /jobconfig settings take precedence over the plaintext defaults. Change the effective values in /jobconfig; copying config files does not replace saved jobs, grades, locations or overrides. Keep the saved data and do not reset the configurator. Use /jobconfigimport sky_mechanicjob only if you intentionally want to import your edited plaintext configuration, after backing up and reviewing its replacement scope. With Config.UseJobConfigurator = false, merge the settings into the supplied config files instead.

New Config.VehiclePrices controls the global price source used by vehicle-value-based tuning. Defaults retain the existing mapping:

Config.VehiclePrices = {
    source = "auto",
    tableName = "vehicles",
    modelColumn = "model",
    priceColumn = "price",
    hashColumn = ""
}

In /jobconfig → Mechanic Jobs → General → Database, use vehiclePriceSource, vehiclePriceTable, vehiclePriceModelColumn, vehiclePricePriceColumn and vehiclePriceHashColumn. auto uses ESX's SQL mapping or QBCore/Qbox's vehicle catalogue. database uses the configured SQL mapping on any framework. For JG Dealerships choose database, dealership_vehicles, spawn_code, price, hashkey. The model column must contain spawn names, not display names; price values must be positive numbers. The optional hash column accepts numeric signed/unsigned hashes; leave it empty to resolve from spawn names. SQL identifiers allow up to 64 letters, digits or underscores. Missing prices retain the configured fallback vehicle value. The catalogue is read-only; the existing custom purchase-price hook remains available.

New Config.ToggleFeatures.tuningFreeCamera = true allows Space to hide the tuning cursor for camera movement; it is independent of existing automatic tuningCamera. New Config.ToggleFeatures.jgHud = false enables optional JG HUD display. Existing jgMileage = false and mileageHud = true remain. Select these feature switches in /jobconfig when enabled. For Sky mileage shown only in JG HUD, enable JG HUD and disable JG Mileage and Mileage HUD. JG Mileage uses jg-vehiclemileage v2.1.1+ while started, otherwise Sky mileage continues; switching does not migrate old odometer data.

For JG HUD integration, add this after the existing client_scripts block in jg-hud/fxmanifest.lua, so it loads after framework/cl-functions.lua:

client_script "@sky_mechanicjob/compat/jg_hud_mileage.lua"

Reload manifests with refresh, then restart Mechanic and jg-hud, or use the full server restart in the verification step. This retains JG HUD's original getter when Sky has no active display value. No additional JG resource is required if the new switch stays off. Plate-style audit integration is opt-in through the supplied server exports; installing this release alone does not enable attribution for an external script. Keep existing actor/permission policies. Install Base 1.46.0 with Mechanic 1.35.0 for the Qbox initial-save correction.

Optional profiling remains off by default. If support requests it, put setr sky_profiler 1 before the Sky ensure lines in server.cfg, perform a full server restart, run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-release-20261008.json with a new filename for each capture. Disable it with setr sky_profiler 0 and another full server restart. This is not a /jobconfig setting; no recording or upload starts automatically.

4. Database, items and assets

SQL: No new Mechanic table, column or manual migration. Vehicle-price configuration reads your existing catalogue; do not alter dealership tables merely to apply the update. Existing registration history and vehicle properties remain. Items: No new definitions. Assets: Add the supplied JG compatibility Lua file if integrating the HUD; no new map, stream model or item image. No Sky-to-JG mileage data migration is performed.

5. Restart and check

Perform a full server restart to reload changed manifests and file lists, then reconnect clients. Start the framework, database connector and selected inventory, phone, banking and UI providers first, then Base 1.46.0 and Jobs Base 1.49.0. Start DOJ 0.4.0 before Police 1.38.0 for their shared catalogue and court workflows. Start Ambulance 2.45.0 before Crime 0.9.0 when using their medical integration. Mechanic 1.35.0 and Fire 1.17.0 follow both libraries. Include only installed resources. Check actual installed versions and the first startup/database error before testing.

Confirm saved tuning settings and calculate a price for a known model, including your fallback for a missing price. Test automatic tuning camera and Space free camera independently. If JG HUD is enabled, check its mileage with your selected source, provider stop/restart and vehicle exit. On Qbox, save tuning and retrieve an already-owned vehicle with naturally empty saved properties, preserving plate, fuel and damage. Check temporary-registration remaining online time and history, Dyno PS/HP output, File Explorer and targeted invoices. If integrating plate-style audit exports, confirm only successful attributed changes are recorded.

1. Prepare

These instructions cover sky_mechanicjob 1.34.0 → the refreshed 1.34.1 package. If you already installed the earlier 1.34.1 startup hotfix, download the latest 1.34.1 package again for these additions. The manifest version stays 1.34.1, so the version alone cannot distinguish the earlier package. Check that the new download includes Config.VehiclePrices and Config.ToggleFeatures.tuningFreeCamera in sky_mechanicjob/config/config.lua, then check the settings after installation.

Back up resources, the database, custom configuration, translations and saved configurator data. Validate the update on staging and stop the server for replacement. Install the latest refreshed Base 1.45.1, then Jobs Base 1.48.1, then Mechanic 1.34.1 and the matching updates for your installed consumers. Base supplies the Qbox first-save storage contract and Jobs Base supplies startup readiness plus the matching configurator fields and labels. An older package with the same .1 version may lack the new additions. Complete earlier release migrations first if upgrading from before 1.34.0.

2. Replace files

Use the complete refreshed 1.34.1 customer package. Delete the entire sky_mechanicjob/source/ folder and insert the new folder, then replace sky_mechanicjob/fxmanifest.lua from that same package. This replaces the runtime code and generated interface together; do not merge old generated interface files.

Merge the new sky_mechanicjob/config/config.lua entries and the updated purchase-price hook in sky_mechanicjob/config/sv_functions.lua as described below, preserving intentional custom values and hooks. Replace sky_mechanicjob/README.md and refresh the complete sky_mechanicjob/config/locales/ tree, merging custom translations. Keep your selected Base language.

The supplied dependency bootstrap remains editable for support and must match the new source and manifest. Keep the new source/dependencies.lua; do not restore an older custom bootstrap. There are no outside-source removals or renames in this Mechanic update.

3. Merge settings

Keep your existing jobs, grades, workshop locations and saved overrides. Merge the changed values into sky_mechanicjob/config/config.lua; do not replace your custom configuration with all shipped defaults. Config.UseJobConfigurator remains true by default. When it is true, managed features and settings use the packaged defaults plus saved database overrides, so edit them in /jobconfig. Plaintext edits to those managed values do not change the effective saved configuration. When it is false, the Lua values below are authoritative. Startup settings such as Config.UseJobConfigurator and Config.AutoExecuteQuery remain plaintext settings. No configuration reset or re-import is required.

Vehicle purchase prices — old: no Config.VehiclePrices block; the supplied hook used ESX vehicles.model / vehicles.price or the QBCore/Qbox catalogue. New: add this complete block, with the default auto preserving those sources:

Config.VehiclePrices = {
    source = "auto",
    tableName = "vehicles",
    modelColumn = "model",
    priceColumn = "price",
    hashColumn = "" -- Optional numeric model-hash column; leave empty to hash the spawn names.
}

In /jobconfig, open Mechanic Jobs → General → Database and set Vehicle price source, Vehicle price table, Spawn name column, Price column, and Model hash column (optional). This is one global catalogue for the resource's vehicle-value-based tuning calculations, not a separate mapping for each workshop. The saved setting keys and new defaults are vehiclePriceSource = "auto", vehiclePriceTable = "vehicles", vehiclePriceModelColumn = "model", vehiclePricePriceColumn = "price", and vehiclePriceHashColumn = "". Missing new keys inherit those defaults; saved non-default mappings remain authoritative. Save the intended values there and reopen the section after a restart to check them.

Choose auto / Automatic (framework) for the existing behaviour: ESX reads the configured SQL mapping, while QBCore and Qbox use their framework vehicle catalogue. Choose database / Database to read a custom SQL catalogue on any of those frameworks. Use the exact names of an existing table and columns. The model column must contain spawn names, the price column numeric purchase prices, and SQL table/column names must contain 1–64 letters, digits or underscores. Do not enter schema prefixes, spaces or SQL expressions. Leave the optional hash column empty to match model hashes from spawn names; an existing numeric hash column may contain signed or unsigned values, including numeric strings.

For an existing JG Dealerships catalogue that uses these exact column names, the complete example is:

Config.VehiclePrices = {
    source = "database",
    tableName = "dealership_vehicles",
    modelColumn = "spawn_code",
    priceColumn = "price",
    hashColumn = "hashkey"
}

With /jobconfig enabled, enter the same five values in General → Database instead of relying on the Lua example. JG's model column is a display name; use spawn_code for the spawn name. The mapping only reads prices and does not create or change dealership tables. Missing or nonpositive prices use your existing Config.TuningCostProfile.fallbackVehicleValue or the applicable workshop/instant-tuning price profile's fallback. The shipped global fallback remains 50000; preserve intentional pricing overrides.

Merge sky_mechanicjob/config/sv_functions.lua from the same package. The supplied Config.Functions.GetVehiclePurchasePrice(model, modelHash, source) now reads Config.VehiclePrices; restoring an older supplied hook would bypass the mapping. If you deliberately use a custom resource API or complex query, preserve that custom hook and check its returned prices; the new SQL settings do not override custom hook code. Keep the supplied startup readiness line at the top of this file. For the standard mapping, this is the complete new hook:

Config.Functions.GetVehiclePurchasePrice = function(model, modelHash, source)
    local modelName = tostring(model or "")
    modelName = modelName:match("^%s*(.-)%s*$")
    local normalizedHash = tonumber(modelHash)
    if normalizedHash then
        normalizedHash = normalizedHash % 4294967296
    end

    local function getSharedVehiclePrice(vehicles)
        if modelName ~= "" then
            local directVehicle = vehicles[modelName] or vehicles[modelName:lower()] or vehicles[modelName:upper()]
            local directPrice = tonumber(directVehicle and directVehicle.price) or 0
            if directPrice > 0 then
                return math.floor(directPrice)
            end
        end

        if not normalizedHash then
            return nil
        end

        for catalogModel, vehicle in pairs(vehicles) do
            local price = tonumber(vehicle.price) or 0
            if price > 0 then
                local vehicleModel = tostring(vehicle.model or vehicle.hash or catalogModel or "")
                if vehicleModel ~= "" and (joaat(vehicleModel) % 4294967296 == normalizedHash
                    or (tonumber(vehicleModel) and tonumber(vehicleModel) % 4294967296 == normalizedHash)) then
                    return math.floor(price)
                end
            end
        end

        return nil
    end

    local price_source = Config.VehiclePrices or ConfigDefaults.VehiclePrices
    if price_source.source ~= "auto" and price_source.source ~= "database" then
        error("[sky_mechanicjob] Config.VehiclePrices.source must be auto or database")
    end

    if price_source.source == "database" or Sky.Config.framework == "esx" then
        local identifiers = {}
        for _, key in ipairs({ "tableName", "modelColumn", "priceColumn", "hashColumn" }) do
            local identifier = tostring(price_source[key] or ""):match("^%s*(.-)%s*$")
            if key ~= "hashColumn" or identifier ~= "" then
                if #identifier == 0 or #identifier > 64 or not identifier:match("^[%w_]+$") then
                    error(("[sky_mechanicjob] Invalid Config.VehiclePrices.%s: use a SQL identifier of 1-64 letters, digits or underscores"):format(key))
                end
                identifiers[key] = "`" .. identifier .. "`"
            end
        end

        if modelName ~= "" then
            local rows = Sky.Query(("SELECT %s AS price FROM %s WHERE %s = ? LIMIT 1")
                :format(identifiers.priceColumn, identifiers.tableName, identifiers.modelColumn), { modelName })
            local price = tonumber(rows[1] and rows[1].price) or 0
            if price > 0 then
                return math.floor(price)
            end
        end

        if not normalizedHash then
            return nil
        end

        if identifiers.hashColumn then
            local signed_hash = normalizedHash >= 2147483648 and normalizedHash - 4294967296 or normalizedHash
            local rows = Sky.Query(("SELECT %s AS price FROM %s WHERE %s IN (?, ?) LIMIT 1")
                :format(identifiers.priceColumn, identifiers.tableName, identifiers.hashColumn),
                { ("%.0f"):format(signed_hash), ("%.0f"):format(normalizedHash) })
            local price = tonumber(rows[1] and rows[1].price) or 0
            return price > 0 and math.floor(price) or nil
        end

        local rows = Sky.Query(("SELECT %s AS model, %s AS price FROM %s")
            :format(identifiers.modelColumn, identifiers.priceColumn, identifiers.tableName), {})
        for _, row in ipairs(rows) do
            local rowModel = tostring(row.model or "")
            local price = tonumber(row.price) or 0
            if rowModel ~= "" and price > 0 and joaat(rowModel) % 4294967296 == normalizedHash then
                return math.floor(price)
            end
        end

        return nil
    end

    if Sky.Config.framework == "qbox" then
        return getSharedVehiclePrice(exports.qbx_core:GetVehiclesByName())
    end

    local qb = exports["qb-core"]:GetCoreObject()
    return getSharedVehiclePrice(qb.Shared.Vehicles)
end

Free camera — old: Config.ToggleFeatures.tuningFreeCamera was absent and free-camera entry was not separately configurable. New: add tuningFreeCamera = true alongside the existing tuningCamera = true. tuningCamera still controls automatic focusing of the selected tuning part; its shipped default is unchanged. tuningFreeCamera controls hiding the cursor for manual camera movement, independently of the automatic camera. This complete shipped block is a reference: add the new entry and preserve your existing choices for all other entries:

Config.ToggleFeatures = {
    kuv = false,
    vehicleRegistration = false,
    stance = true,
    tuningCamera = true, -- Automatically focus the selected tuning part. Also managed in /jobconfig.
    tuningFreeCamera = true, -- Allow Space to hide the tuning cursor for free camera movement. Also managed in /jobconfig.
    instantTuning = false,
    partsDelivery = true,
    carryItems = false,
    nitro = true,
    antiLag = true,
    twoStep = true,
    electronicTuning = true,
    wheelDamage = true,
    customHandling = true,
    handlingEditor = true, -- Admin editor and its automatic plate/model overrides.
    mileageHud = true,
    -- Requires jg-vehiclemileage v2.1.1+ to be started first. Existing Sky mileage is not migrated to JG.
    jgMileage = false,
    workshopLift = true,
    mobileDyno = true,
    brakeOverheating = true,
    selfServiceOrderNotifications = true,
    vehicleMaintenanceNotifications = true,
    subscriptions = true
}

In /jobconfig, open Mechanic Jobs → Features → Free camera in tuning menu. Its saved feature key is tuningFreeCamera, with default true; a saved false remains disabled after restart. Keep or adjust Automatic tuning camera separately (tuningCamera, unchanged default true). With free camera enabled, Space releases the tuning cursor and pressing it again restores the cursor; Escape still closes the menu. With it disabled, Space does not enter free camera. Disabling it through /jobconfig during an unfocused tuning session restores the cursor. The existing focus-key default remains Config.Keybinds.tuningFocusKey = "SPACE"; retain player key bindings and existing hotkey overrides.

Update the matching Jobs Base 1.48.1 package and its complete sky_jobs_base/config/locales/jobconfigurator/sky_mechanicjob/ tree for the new price fields, General → Hotkeys/Database labels and free-camera feature label. Refresh Mechanic's own complete locale tree and merge custom translations. Keep the selected language in sky_base/config/config.lua. The configurator labels are owned by Jobs Base.

The existing Parts Delivery Shop → Delivery handling selector is restored by Jobs Base 1.48.1. Its setting remains partsDeliveryMode; without /jobconfig, retain Config.PartsDelivery.deliveryMode in sky_mechanicjob/config/config.lua ("standard" or "player_inventory"). The shipped default remains "standard". Keep saved overrides.

Optional diagnostics remain disabled by default. If support requests a recording, put setr sky_profiler 1 before the Sky ensure lines in server.cfg, restart the server, run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-startup-hotfix.json. Disable with setr sky_profiler 0 and another full server restart. This is a plaintext server convar, not a /jobconfig setting; no recording or upload starts automatically.

4. Database, items and assets

SQL: No new table, column or SQL import is introduced by this Mechanic update. Keep your existing Config.AutoExecuteQuery policy. Repair the original database error if an earlier migration failed; continuing startup does not create missing schema. Do not replay a full import, clear tuning tables, force success markers or reset saved jobs/configurator data.

The vehicle-price mapping reads an existing catalogue; it does not create a dealership table, alter its schema or change prices. Check the table and columns before choosing Database. JG Dealerships is optional and is only needed if you choose its existing catalogue or custom hook.

Qbox: Update the refreshed Base 1.45.1 together with Mechanic 1.34.1, keeping your existing Qbox qbx_core and qbx_vehicles setup. An already-owned vehicle with missing or empty properties can receive its first complete tuning snapshot through qbx_vehicles; later saves continue preserving stored fuel, damage and other fields. This does not create an ownership record, repair malformed nonempty property data, or require a framework patch or manual SQL repair. Do not empty an existing vehicle's saved properties to trigger initialization. If you customized sky_base/config/vehicle_storage.lua, merge its Qbox initialization-marker update while preserving your garage schema mapping.

Items: No new item definitions, inventory registrations or item migration are introduced. Assets: No new item images, models, audio or stream assets are introduced. Keep the existing inventory and asset setup. The new frontend files are supplied inside the replaced source/ folder.

Progress providers: Keep your selected provider configuration. If you use ZSX_UIV2, install the matching Base 1.45.1 provider files and follow Base's provider setup; ensure the provider starts before Base. ZSX supports player cancellation; no programmatic stop export is assumed.

5. Restart and check

Perform a full server restart after replacement so changed manifests and file lists reload. Start the framework, database connector and selected providers first, then Base 1.45.1, Jobs Base 1.48.1, Mechanic 1.34.1 and other installed consumers. Reconnect clients. The new changes keep the existing startup hotfix: Mechanic waits for Jobs Base initialization instead of aborting after 60 seconds. SQL migration warnings remain actionable and failure to read saved settings remains a visible initialization error.

Open the Mechanic tablet at your existing workshop. With /jobconfig, confirm the General → Database values, the Free camera in tuning menu feature, and Parts Delivery Shop → Delivery handling. Save a deliberate non-default price mapping or free-camera choice, reopen the section and restart once to verify that choice persists; do not reset unrelated overrides.

For vehicle-value-based pricing, use a vehicle with a known positive purchase price in your selected catalogue and check its tuning quote. With an optional hash column, test a vehicle whose catalogue stores its hash in the format you use. Also check a missing-price vehicle against the intended fallback. Fixed-price or otherwise overridden tuning options may not change when the purchase catalogue changes.

In the tuning menu, test Space to hide and restore the cursor and Escape to close, with Automatic tuning camera both enabled and disabled. Then disable Free camera in tuning menu and confirm that entry is blocked; if you disable it during an unfocused session, confirm that the cursor returns. Test your existing rebound focus key too.

On Qbox, use an already-owned staging vehicle with naturally missing or empty saved properties. Complete one permitted tuning install, store and retrieve it through your configured garage, and check the installed tuning, plate/model, fuel and damage. Repeat a save with an existing complete record and check that stored fuel, damage and other vehicle data remain intact. Source/contract tests do not establish the customer's paid install or garage round trip.

With two clients or a staging streaming-range test, check a spawned tuned vehicle, Dyno updates, remote AntiLag/TwoStep effects, catalytic smoke, wheel repair and engine-sound previews both nearby and outside streaming range. Check that no new network-object warnings occur and that nearby effects and restoration still work. Test lift attachment while in range, moving out of range during loading, and detachment; this change does not create a missing garage/lift vehicle association.

Complete and cancel one non-minigame install/repair using your selected progress provider; include ZSX_UIV2 if configured. Do not assume a provider has a programmatic stop export when it does not document one. If a feature remains unavailable, collect the first initialization/SQL error, preceding lines and actual package versions. Customer/client/provider acceptance remains a check to perform on your server.

1. Prepare

These instructions cover sky_mechanicjob 1.33.1 → 1.34.0. Before replacing files, confirm that your customer download platform provides the versions below and check each downloaded resource's fxmanifest.lua; published documentation or a source tag alone does not establish that its customer download has been uploaded. Complete earlier migrations first if upgrading from an older version. Back up the database, resources, custom config, translations and saved Job Configurator/Creator data. Validate the update on staging before applying it to your production server. Stop the server during replacement. Install Sky Base 1.45.0, then Sky Jobs Base 1.48.0, then the matching releases for your installed jobs and Crime. Keep provider dependencies and optional integrations compatible; preserve saved overrides and existing records.

2. Replace files

Use the complete 1.34.0 release package. Delete the entire sky_mechanicjob/source/ folder and insert its new version; do not merge old generated interface files. Replace sky_mechanicjob/fxmanifest.lua from the same package. Refresh the complete sky_mechanicjob/config/locales/ tree and merge your custom translations into the new files. Keep your selected shared language in sky_base/config/config.lua. Install the following shipped paths from that package, merging custom configuration into the updated public files rather than restoring old complete files:

• sky_mechanicjob/config/adv_config.lua
• sky_mechanicjob/config/config.lua
• sky_mechanicjob/config/engine_sounds_config.lua
• sky_mechanicjob/config/init.lua
• sky_mechanicjob/config/locales/*
• sky_mechanicjob/config/sv_functions.lua
• sky_mechanicjob/fxmanifest.lua
• sky_mechanicjob/source/* — delete and reinsert

3. Merge configuration

Merge the two new feature defaults into sky_mechanicjob/config/config.lua:

Config.ToggleFeatures.tuningCamera = true
Config.ToggleFeatures.jgMileage = false

Set /jobconfig → Mechanicjob → Features keys tuningCamera and jgMileage when the configurator is enabled. Saved overrides remain effective. The camera feature permits automatic focus; each player can disable the automatic camera in the tuning menu and use the existing manual/free camera control with Space. Disabling the feature releases its own camera immediately.

Leave jgMileage = false unless using jg-vehiclemileage v2.1.1 or newer, started before Mechanicjob. With the feature enabled, JG's valid odometer value is authoritative, including zero and corrected lower values. Existing Sky mileage is not migrated into JG. Back up and review both systems' odometer data before switching; do not enable this to copy Sky mileage.

Add both new profiles inside your existing Config.Interactions table, keeping all existing workshop profiles:

mobile_dyno_station = {
    public = false,
    interaction = true,
    duty = true,
    interactionDistance = 3.5,
    unique = true,
    requiresHeading = true,
    placementGizmo = true,
    marker = { enabled = false, type = 1, offset = vector3(0.0, 0.0, 0.0) },
    npc = { enabled = false },
    blip = { enabled = false, sprite = 446, color = 5 }
},
mobile_dyno_monitor = {
    public = false,
    interaction = false,
    duty = true,
    unique = true,
    requiresHeading = true,
    placementGizmo = true,
    marker = { enabled = false, type = 1, offset = vector3(0.0, 0.0, 0.0) },
    npc = { enabled = false },
    blip = { enabled = false, sprite = 446, color = 5 }
},

With /jobconfig, edit the station and monitor interaction/placement profiles for Mechanicjob and keep saved custom rules. They are interaction profiles, not new global boolean settings. Menu and inventory placement use the configured placement gizmo and limits. Review existing installations and their blips after a live update.

The default global Config.Billing.maximumInvoiceAmount changes 250000 → 999999999. The shipped per-job Config.Jobs[*].billing.maximumInvoiceAmount also changes 250000 → 999999999; the shipped grade rows 0/1/2/3 change 15000/50000/125000/250000 → 999999999. Keep deliberate server-specific limits, discounts, taxes, permissions and other grade flags. Review the selected job's Billing settings in /jobconfig; do not reset saved custom limits to receive the new default.

In config/engine_sounds_config.lua, the default Config.EngineSounds.cameraPart changes "rear" → "engine". Preserve custom sound entries and their chosen focus. This sound option catalogue stays in the plaintext file; tuningCamera controls whether automatic focus is available.

Activity allow-lists in config/adv_config.lua now accept exact job/group names and "gang:<internal_name>". Gang membership is checked independently; a job duty requirement applies to job grants. Preserve existing jobs and enter only the intended gang selector in a supported activity list.

Mechanic's native service invoice and advanced billing configuration remain separate from central Sky Billing. Configure Base Config.billing = "sky" and Jobs Base billing to use the shared central panel; do not assume this migrates existing mechanic or external invoices. Unpaid public tuning orders can be invoiced from the Tuning Orders view by an authorized mechanic, using the original order/customer rather than a nearby replacement.

Merge readiness lines in config/init.lua and config/sv_functions.lua while retaining your custom function bodies. These bootstrap extension files are not /jobconfig settings.

The new readiness line in the supplied public bootstrap/hooks is:

if not Citizen.Await(SkyJobsReady) then return end

Retain it in the same position as the supplied file, before code using the job dependency. Merge your custom function bodies into the updated files; do not add this line inside every custom function. This is a bootstrap change, not a new editable setting.

Optional diagnostics are disabled by default. If support requests a recording, put setr sky_profiler 1 before the Sky ensure lines in server.cfg, then restart the server. Run profiler record 1000, wait for profiler status to show that recording has completed, then run profiler saveJSON sky-release-profile.json. Disable diagnostics with setr sky_profiler 0 and another server restart. This is not a /jobconfig setting; no recording or upload starts automatically.

For an older explicit profiler package, replace any previously modified public config/provider/compatibility files with the supplied versions and merge your intentional customizations. In this release package, profiler preparation preserves all files outside source/ byte for byte except fxmanifest.lua; the functional config changes listed in this guide still require their own merge.

4. Data, items and dependencies

SQL: No new Mechanic table or column is introduced by this release. Keep existing orders, invoice links and vehicle mileage. Do not replay the full Mechanic import on an established database. Complete matching Base and Jobs Base migrations for the central Billing panel; existing mechanic invoices keep their own workflow.

Items/assets: No new item definition or streamed model is required by these changes. Existing mobile dyno, monitor, engine sound and carry-item names must still match your configured inventory. Replace the shipped UI, style and image files named in Changed Files. Keep your selected external vehicle properties and mileage provider configuration.

Providers: JG mileage is optional and requires jg-vehiclemileage v2.1.1+ started first. The ESX compatibility diagnostic reports unsupported upstream vehicle property support; it does not patch ESX or guarantee successful persistence. Follow the reported upstream compatibility requirement when this warning appears.

Dependencies: Install matching Sky Base 1.45.0 and Jobs Base 1.48.0 releases before Mechanicjob 1.34.0. Start framework/database/providers, Base, Jobs Base and then Mechanicjob; include the compatible JG resource before Mechanicjob only when that integration is enabled. Restart and reconnect clients.

5. Restart and check

Start your framework, database connector and configured providers first, then Base, Jobs Base and the updated job resources in dependency order. Reconnect clients. Open a workshop and test automatic focus on the selected part, the player camera toggle, Space/manual control and live disabling. If JG is enabled, verify a loaded, zero and corrected odometer value and preserve the unconverted Sky history. Place a dyno/monitor through the configured routes and check saved interaction, slope/placement and blip settings. Invoice an unpaid public order and confirm the original customer, quote and permission checks; retry without creating a duplicate. Test the native mechanic invoice flow separately from the shared Sky Billing panel, print a record, reopen the tablet at its current view and check tuning prices/materials for two workshop jobs.

If a check fails, keep the update on staging and collect the installed resource versions, selected provider, effective saved setting and the first relevant startup or action error. A successful source test, build or copy does not establish live FiveM, provider or customer acceptance.

1. Prepare

These instructions cover sky_mechanicjob 1.33.0 → 1.33.1. Complete earlier migrations first if upgrading from an older version. Back up the database, resources, custom configuration and saved job/Creator data. Stop the server for the coordinated update. Install Base 1.44.1, then Jobs Base 1.47.1, then the matching hotfixes for your installed Sky jobs and Crime.

2. Replace files

Use the 1.33.1 download. Delete the entire sky_mechanicjob/source/ folder and insert the new folder. Replace sky_mechanicjob/fxmanifest.lua from that same package. Refresh the complete sky_mechanicjob/config/locales/ tree and reapply custom translations. Keep the new source and manifest together; do not merge old generated interface files into them.

Remove these obsolete locale fragments after merging any custom translations into the matching language file: sky_mechanicjob/config/locales/partials/handling_editor.lua, sky_mechanicjob/config/locales/partials/mobile_dyno.lua.

3. Keep settings

No configuration values or Job Configurator setting keys are added, removed or reset by this hotfix. Keep your current settings and saved overrides. Hungarian uses the existing Config.locale = "hu" setting in sky_base/config/config.lua; leave your selected language unchanged if you do not want to switch. Update the matching Base, Jobs Base and installed resource locale folders together.

Optional diagnostics stay disabled by default. If support requests a recording, put setr sky_profiler 1 before the Sky ensure lines in server.cfg, restart, run profiler record 1000, wait for profiler status to show completion, then run profiler saveJSON sky-hotfix-profile.json. Disable with setr sky_profiler 0 and another restart. This is not a /jobconfig option; nothing is recorded or uploaded automatically.

4. Data and assets

No new SQL import, item definition, inventory image or stream asset is required for this hotfix. Keep saved job/Creator data; do not reset or reimport it. Required earlier migrations still apply when upgrading from an older release.

5. Restart and check

Start your framework, database connector and configured providers first, then Base 1.44.1, Jobs Base 1.47.1 and the updated jobs/Crime. Reconnect clients. Open /jobconfig and check that the tuning menu loads and saves vehicle properties. If startup still fails, collect the first error and its preceding log lines together with the installed versions.

1. Prepare the update

These instructions cover sky_mechanicjob 1.32.0 → 1.33.0. Complete earlier required migrations first if upgrading from an older version. Stop the server for the coordinated update and back up the database, resource files, customized configuration and saved job/Creator data. Install Base 1.44.0 first, then Jobs Base 1.47.0, then sky_mechanicjob 1.33.0 and the matching updates for your other installed Sky jobs. The updated manifest requires the matching Base and Jobs Base imports; do not combine it with older dependency folders.

2. Replace the package files

Use the matching 1.33.0 package. Delete the complete old sky_mechanicjob/source/ folder and insert the new folder. Replace sky_mechanicjob/fxmanifest.lua from the same download. Refresh the entire sky_mechanicjob/config/locales/ tree and merge your custom translations back. Do not merge old generated interface files into the new source/ folder.

Merge the comment update in sky_mechanicjob/config/config.lua while preserving your workshop settings. Copy sky_mechanicjob/compat/sky_mechanicjob_repair_hotfix.lua to its packaged compat/ location. It is an optional compatibility file for older 1.32.0 installations; do not additionally install it into config/locales/partials/ for this full update, which already includes the repair fix. If you already used that drop-in on 1.32.0, it automatically skips its repair callback when the integrated fix is present. Delete the old sky_mechanicjob/config/locales/partials/handling_editor.lua and sky_mechanicjob/config/locales/partials/mobile_dyno.lua files. Their supplied translations are now included in the normal language files. Use the matching fxmanifest.lua, which no longer loads the old partials directory. Merge any custom text from those fragments into the corresponding normal locale table instead of restoring the old files or their manifest globs. If you maintain other custom files in that directory, move their translations into the corresponding normal locale files too. No file rename is required.

3. Merge configuration and saved overrides

Hungarian language

Refresh the complete resource locale folder from this download, including hu.lua, and carry over your custom translations. To use Hungarian, set the existing Config.locale value to "hu" in sky_base/config/config.lua; its supplied default remains "en". Keep your current value if you are not changing language. This is the shared Sky language setting, so update the matching Base, Jobs Base and installed job locale folders together. Jobs Base supplies the Hungarian /jobconfig translations too. No new /jobconfig language setting, saved-job reset or database migration is required for this language addition. Apply the normal restart and reconnect steps at the end of this update.

In sky_mechanicjob/config/config.lua, the only file change is the guidance comment inside Config.Subscriptions.npc. No shipped value changes, new config tables, adv_config.lua edits or interaction capability flags are required. The existing defaults remain:

Config.Subscriptions.npc = {
    pedModel = "s_m_m_autoshop_01",
    scenario = "WORLD_HUMAN_CLIPBOARD",
    emote = { dict = "", clip = "" }
}

Keep your customized values rather than replacing them with this example. Previously these subscription-specific values could overwrite the terminal's edited NPC. They are now legacy plaintext/import defaults; customized interaction values in Config.Interactions.subscription_terminal.npc take priority. Set model through pedHash, scenario through scenario, and animation through animation.dict / animation.name. Leave the scenario empty to use an animation. For a server without /jobconfig, retain legacy values or move intentional customizations to those interaction fields; no bulk reset is needed.

With /jobconfig: After starting the updated resources, open Mechanic → Interactions → Subscription Terminal → NPC. The four old standalone settings are retired and automatically move to the interaction only where no explicit interaction override exists:

Explicit interaction values, including empty scenario/animation strings, are preserved. The load migration is repeatable; the next normal save persists the new interaction overrides and removes the retired standalone keys. Review and save the effective NPC once. Do not edit the database, reset the job or reimport the whole configuration.

Workshop tuning restrictions: Existing per-job Config.Jobs[*].tuningCostProfile, managed as the job-owned tuningCostProfile extension, now determines the visited workshop's choices for staff and public customers. Its optionCostByOptionId settings remain unchanged. Existing disabled objects (enabled = false) and legacy literal false entries remain disabled. Existing global Config.ToggleFeatures.electronicTuning, .antiLag and .twoStep also apply when open menus refresh. Saved overrides remain authoritative. Recheck a normal and a restricted workshop separately; enabling an option in one workshop must not enable it in another. Instant Tuning keeps its separate profile. Already installed tuning is preserved when a newly forbidden pending selection is removed.

Dyno installation coordinates, headings and all Dyno/lift settings retain their current values. Saved Dyno positions are restored directly; correct an intentionally misplaced installation using its existing editor instead of deleting the stored installations.

Optional performance diagnostics

Extra profiler information remains disabled by default. If support requests a recording, add setr sky_profiler 1 to server.cfg before the Sky ensure lines and restart the server. In the server console, run profiler record 1000, wait until profiler status reports completion, then run profiler saveJSON sky-release-profile.json. Share the file only when requested. To disable the extra information, change the line to setr sky_profiler 0 and restart again. This is not a /jobconfig setting; enabling it does not record or upload anything automatically.

Keep source/ and fxmanifest.lua from the same download even when diagnostics are disabled. Profiler processing changes only source Lua and the manifest. If an older profiler package changed public files outside source/, restore those files once from the clean current download and reapply your own customizations.

4. Apply SQL, inventory and asset updates

No Mechanic SQL migration, table/column type/default change, new inventory item, image or streamed asset is required. Existing subscriptions, invoices, orders, vehicle tuning and role grants are retained. The subscription NPC change migrates existing configurator values through the normal load/save path; it is not an SQL schema migration.

5. Restart and verify

Start providers/framework, Base 1.44.0, Jobs Base 1.47.0 and Mechanic 1.33.0, then reconnect. Check subscription terminal model/scenario/animation after saving, reopening and restarting; test two Instant Tuning NPC locations with different headings. Check that an interaction save updates active workshop points.

At two workshops with different ECU permissions, test both staff and public customers. Change an option while the tuning menu is open: only a now-forbidden pending choice should be removed, installed tuning and other permitted selections should remain, and a rejected basket should not charge money. Compare Dyno runs on the same vehicle before/after engine or turbo upgrades and after removing them, including a second run without reconnecting. The Dyno remains a simulated estimate; this update does not calibrate it to real-world power figures. Restart/reopen a saved Dyno installation and check its exact position and heading. Damage and repair a vehicle using your actual repair provider, then verify normal throttle response and its selected engine sound. Check workshop lifts after streaming away/back and 24-hour vehicle-document times.

1. Prepare the update

If Fire Job is installed, take all breathing bottles out of vehicle bottle storage before stopping the old server. The Fire update cannot migrate its old live vehicle-state contents. Complete this pre-shutdown step before updating Base or Jobs Base.

These instructions cover sky_mechanicjob 1.31.0 → 1.32.0. Complete earlier required migrations first if upgrading from an older release. Stop the server for the coordinated update and back up the resource, database, customized configuration and saved job/creator settings. Install Base 1.43.0 first, then Jobs Base 1.46.0, then the matching installed job releases.

2. Replace the package files

Use the matching 1.32.0 package. Delete the old sky_mechanicjob/source/ directory completely and insert the new directory. Replace sky_mechanicjob/fxmanifest.lua from the same package. Refresh the entire sky_mechanicjob/config/locales/ tree and merge your custom translations back. Merge sky_mechanicjob/config/config.lua as described in this view, preserving unrelated workshops, prices and custom values.

Do not merge old generated interface files into the new source/ directory.

3. Merge configuration and saved overrides

Prepare file changes while the server is stopped. Perform the /jobconfig, Creator and other in-game actions described in this section after starting the updated resources in step 5, during maintenance and before admitting players.

Changed file: sky_mechanicjob/config/config.lua, Config.Interactions.vehicle_registry. The generated defaults mirror it. No adv_config.lua, SQL, item, stream asset or permission-ID migration exists.

Old block:

vehicle_registry = {
    public = false,
    interaction = false,
    unique = false,
    marker = { enabled = false },
    npc = { enabled = false },
    blip = { enabled = false }
},

New block:

vehicle_registry = {
    public = false,
    interaction = true,
    duty = true,
    interactionDistance = 2.5,
    unique = false,
    marker = { enabled = true, type = 1, offset = vector3(0.0, 0.0, 0.0) },
    npc = { enabled = false },
    blip = { enabled = true, sprite = 446, color = 5 }
},

• Exact changed fields: interaction false -> true; duty absent -> true; interactionDistance absent -> 2.5; marker.enabled false -> true with new type = 1, offset = vector3(0.0, 0.0, 0.0); blip.enabled false -> true with new sprite = 446, color = 5. public = false, unique = false, npc.enabled = false remain unchanged.
• /jobconfig resource: sky_mechanicjob. This is an interaction definition at interactions.vehicle_registry, not a new individual feature switch. There is no vehicleRegistryInteraction setting. Definitions/capability flags and actual saved Workshop locations are different objects.
• Existing feature keys are kuv and vehicleRegistration (Config.ToggleFeatures.kuv / .vehicleRegistration), both default false and unchanged. At least one must be enabled for the service point. The service-point interaction follows those feature switches; disabling both removes it.
• Review saved interaction/location display overrides in the Mechanic Interaction System and Workshops area. Existing saved disabled marker/blip choices remain intentional overrides; defaults alone do not force them visible. Place/retain the actual vehicle_registry point in the desired workshop, review marker/blip visibility and workshop sharing for the intended job. No reset or destructive reimport is required.
• New self-invoices use existing job billingSettings / fallback Config.Billing settings: enabled, allowTuningInvoices and allowImmediatePayment, plus duty, own workshop and the role's existing Create invoices permission. No new config setting is added. Exact configured job names beginning with society_ must be retained; do not rename jobs/accounts for this fix.
• Unpaid-order deletion requires existing Cancel invoices permission and effective rank allowCancellation. It is not unrestricted deletion and does not refund paid/open orders through this path. Closing a receipt still leaves the order pending.
• Progress provider selection remains in sky_base/config/config.lua (Config.progressbar), not a new Mechanic option or /jobconfig key. Update Base with the job; verify the configured provider during the installation check.
• Dependencies: Base 1.43.0, Jobs Base 1.46.0, then Mechanic 1.32.0.

Optional performance diagnostics

Extra profiler information is disabled by default. If support requests a recording, add setr sky_profiler 1 to server.cfg before the Sky ensure lines and restart. In the server console, run profiler record 1000, wait until profiler status reports completion, then run profiler saveJSON sky-release-profile.json. To disable the extra information, use setr sky_profiler 0 and restart. This is not a /jobconfig setting. Enabling it does not start recording or upload anything automatically.

Keep source/ and fxmanifest.lua from the same download even when diagnostics are disabled. Profiler processing changes only source Lua and the manifest; public configuration and provider files remain unchanged by that processing. If an older profiler package altered files outside source/, restore those once from the current download and reapply your own customizations.

4. Apply SQL, inventory and asset updates

No Mechanic SQL, inventory item, image or stream migration is required. Keep existing data and role grants. The new source provides the runtime changes; /jobconfig does not install source files or manifests.

5. Restart and verify

Start framework/providers, Base 1.43.0, Jobs Base 1.46.0 and Mechanic 1.32.0, then reconnect. Test the placed inspection/registration point and a deliberately shared workshop. Check an authorized customer invoice, self-invoice and unpaid-order deletion, plus a role without invoice permission. Closing a receipt must leave its order pending. Test cancellation with the configured progress provider and confirm cancelled work does not install parts or complete a repair.

If a separate invoice-creation window remains invisible, provide the first F8 NUI error and the installed versions. The empty-item receipt correction does not establish the cause of every window-opening problem.

1. Prepare

These instructions cover 1.30.0 → 1.31.0. Complete older required migrations first if upgrading from an earlier version. Stop the server and back up the database, resource, customized files and saved job/creator data. Install Base 1.42.0 first, then Jobs Base 1.45.0 with its own SQL, inventory and printer requirements, then sky_mechanicjob 1.31.0.

2. Replace files

Install the matching 1.31.0 package and replace these delivered paths:

• sky_mechanicjob/source/* — delete and reinsert
• sky_mechanicjob/config/locales/*
• sky_mechanicjob/compat/fakeplates.lua
• sky_mechanicjob/compat/fakeplates_realplate_native.lua
• sky_mechanicjob/fxmanifest.lua
• sky_mechanicjob/import.sql

Delete the old sky_mechanicjob/source/ directory and insert the complete new one, including its UI. Replace the complete locale directory. Preserve unrelated writable data and customized public configuration. There are no additional deleted or renamed package paths outside source/ in this release.

Always replace source/* and fxmanifest.lua from the same download, even with diagnostics off. The profiler may instrument only source Lua and the generated manifest; public configuration and compatibility files must match the uninstrumented release source. If an older profiler package modified public files, restore those once from the clean new package and reapply your custom edits.

3. Configuration and access

No options are added, removed or given new defaults in sky_mechanicjob/config/config.lua or config/adv_config.lua for this update. Preserve your job and workshop configuration. File Explorer and the saved-record Print/Share actions become available with Jobs Base 1.45.0; no separate activation flag or record import is required. Vehicle records, orders, invoices and subscriptions retain their app restrictions and role permissions. Own-record actions require an on-duty authorized worker. A recipient sees an explicitly shared record read-only. Other jobs use Shared Documents under the issuing workshop; existing explicit vehicle recipients are retained, while the old Jobs Base Share-tab record/link rules no longer grant document access. DOJ is optional and is needed only for DOJ-origin documents.

Shared-storage permissions: Keep the existing warehouse and full-access role settings. This correction requires no new configuration key, SQL step, permission ID or role reassignment. Update Jobs Base 1.45.0 and any installed Mechanic Job 1.31.0 together so shared storage and workshop deposits use the matching checks. Personal lockers, trunks and custom storage are outside this shared-storage refresh change.

Billing: The existing per-job Config.Jobs[*].billingSettings / /jobconfig Billing extension remains authoritative. Keep enabled, radialEnabled, allowTuningInvoices and allowImmediatePayment enabled for the corresponding workflows; retain your existing customer range and amount limits. Config.Billing remains the plaintext fallback for jobs without those values. There is no new company-payment switch or permission ID. Pay with Company is shown only to the actual invoice recipient whose current registered, active job grants Manage money and differs from the issuing workshop. It uses that company's balance and does not fall back to personal cash or bank funds. Ordinary invoices retain their configured instalment policy; tuning invoices require full payment before installation. Refunds of company-funded tuning go back to the original paying company, even if the customer changes jobs or is offline.

Tuning materials: Explicit quantities in the existing /jobconfig per-job tuningCostProfile extension, including quantity one, are now preserved. If an earlier version overwrote a custom quantity, enter the intended values again and save after this update; the old intended amounts cannot be recovered automatically. Old bare item-name defaults still migrate. No new setting or SQL migration is needed for this correction.

Workshop and vehicle state: An unsubmitted staff basket survives closing and reopening the same live vehicle at the same workshop during the current client session. It does not survive character logout, reconnect, resource restart or vehicle removal, and it does not save unpaid changes to the vehicle. Separately, already accepted runtime tuning can survive a Mechanic resource stop/start while the same vehicle exists; that is not persistence across a full server restart. The Stance Kit saves authorized changes when closed. Existing self-service interaction capability flags and saved per-location vehicle class restrictions are unchanged; do not add new capability flags as ordinary saved settings.

Document printing: Complete the Jobs Base 1.45.0 SQL and printer setup before using Print. The active inventory must support item metadata. Merge the supplied job_document entry from sky_jobs_base/config/inventory/items_ox.lua into your active inventory; for Ox Inventory, put it inside the existing ox_inventory/data/items.lua table and copy sky_jobs_base/config/inventory/job_document.png to ox_inventory/web/images/job_document.png:

["job_document"] = {
    label = "Document",
    weight = 10,
    stack = false,
    close = true,
    consume = 0,
    description = "Printed copy of a job record.",
    client = { image = "job_document.png" },
},

In sky_jobs_base/config/printers.lua, keep Config.Printers.enabled = true and enable this resource in Config.Printers.resources. Configure a printer in /jobconfig → the job → Locations, then review the existing job printerSettings. paperEnabled and inkEnabled remain off by default; register and supply printer_paper or printer_ink only when the corresponding consumption setting is enabled. Saved records can be printed only when access and printer checks pass. The requester collects the finished item at the printer. A collected paper copy remains readable after the corresponding digital share is revoked. Printing is optional; it is not needed to browse or share records. Editing Ambulance or Mechanic configuration does not install these shared items or tables. For Mechanic, Config.Printers.resources.sky_mechanicjob = true is newly supplied by Jobs Base 1.45.0; add that entry to a customized existing resources table.

Optional performance diagnostics: Extra profiler information remains off by default. To make a support recording, put setr sky_profiler 1 in server.cfg before the Sky ensure lines and restart the server. Run profiler record 1000 in the server console, wait for profiler status to report completion, then run profiler saveJSON sky-release-profile.json. Share the file only when requested. To disable the extra information, use setr sky_profiler 0 and restart again. This is not a /jobconfig setting; enabling it does not record or upload anything automatically.

4. SQL, assets and inventory

SQL: Back up the database. With the existing plaintext Config.AutoExecuteQuery = true, startup adds the two columns. If it is false, apply these matching statements from sky_mechanicjob/import.sql before using the new release:

ALTER TABLE `sky_mechanic_invoice_payments`
    ADD COLUMN IF NOT EXISTS `payer_job` VARCHAR(64) NULL;
ALTER TABLE `sky_mechanic_vehicle_profiles`
    ADD COLUMN IF NOT EXISTS `sharing_revision` BIGINT UNSIGNED NOT NULL DEFAULT 0;

payer_job records the company for each invoice payment; existing rows remain valid with NULL. sharing_revision protects vehicle recipient changes from stale edits, starting at zero for existing profiles. Existing profiles, recipients, invoices and tuning orders are retained. Jobs Base 1.45.0 also needs its own shared-record and printed-document tables; apply that dependency's migration first. Do not reset or delete business records. /jobconfig does not install SQL.

Inventory and assets: No Mechanic item, image outside the UI bundle, stream model or tuning-material definition is added or renamed. Replace the full UI through source/* and all locales. Optional record printing uses the Jobs Base job_document item/image and the job's configured printer supplies.

Fake-plate compatibility: Replace sky_mechanicjob/compat/fakeplates.lua and sky_mechanicjob/compat/fakeplates_realplate_native.lua. Restart the garage/key resources that load these compatibility files after Mechanic starts. Real plates such as ABC 123 must retain their internal space through keys, fake-plate application/removal and garage storage. Fake-plate input validation is unchanged. Previously compacted stored real plates cannot be reconstructed reliably by inserting guessed spaces; compare an affected entry with its original owned-vehicle record.

5. Restart and verify

Restart the database/framework and any changed inventory first, then Base 1.42.0, Jobs Base 1.45.0 and Mechanic 1.31.0, followed by garage/key resources loading the updated fake-plate compatibility files. Confirm versions and resolve migration errors before admitting players. With two workers, test vehicle-share grant/revoke conflicts and verify an ordinary profile save cannot restore revoked recipients. Open File Explorer and verify vehicle, order, invoice and subscription access plus a receiving job's read-only view. If printing is configured, print, collect and open a document. Issue a radial invoice with multiple reasons; test cash, card, authorized company payment, insufficient company funds and a tuning refund back to the original company. Verify the workshop receives the payment through the configured banking adapter. At a real workshop point, select tuning, close/reopen, invoice the nearby customer, pay in full and install. Reopen the Stance Kit after closing and restart only Mechanic with the same tuned vehicle present. Check a mixed-space real plate through keys, fake-plate removal and garage storage, plus anti-lag on stock and modified exhausts. Run a dyno session with an observer. Save/reopen custom quantity-one stages in /jobconfig.

Shared-storage role check: Use a regular employee role with warehouse access, not the highest rank or a full-access role, since those retain their existing bypass. Confirm that permitted stock can be transferred. Remove warehouse access through role management while storage is open: it must close, and reopening or transferring stock must be denied. Restore access and reopen without reconnecting. Restrict an item and a weapon for that role, then verify that withdrawals are blocked, including a weapon whose stored name uses different capitalization and any supported carried-item withdrawal. The restriction list blocks withdrawal; it does not reserve stock for that role. Deposits still require warehouse access. With access retained, change a restriction and confirm that the open view updates without losing the current selection or entered quantities.

Carried-parts deposit check: With an on-duty employee carrying a part, revoke warehouse access and attempt to deposit it into shared storage. Repeat with a parts-delivery box. Each denied deposit must leave the carried stock and delivery state unchanged. Restore warehouse access and confirm that both deposits succeed without reconnecting.

1. Prepare the update

Update Base to 1.41.0 and Jobs Base to 1.44.0 before installing sky_mechanicjob 1.30.0. These instructions cover 1.29.1 → 1.30.0; complete earlier migrations first when upgrading from an older version. Stop the server and back up the resource, database, customized files and saved configurator/creator data.

2. Replace the package files

Install the matching 1.30.0 download. Update every path in Changed Files, delete and reinsert sky_mechanicjob/source/*, and replace sky_mechanicjob/config/locales/* completely. Remove the exact paths under Removed Files and apply any listed renames. Preserve unrelated files, writable data and custom assets; merge the configuration changes in this tab into your customized public files.

Replace source/* and fxmanifest.lua from the same download even when optional diagnostics remain off. Profiler instrumentation is confined to Lua in source/ and the generated manifest. Public configuration, integration and compatibility files match the uninstrumented source; their functional changes are listed separately for this release. If an older profiler package modified public files, restore those once from the clean new package and reapply your own edits.

3. Merge configuration

In sky_mechanicjob/config/config.lua, add the following three fields to each relevant Config.Jobs[*].billingSettings table and to the existing Config.Billing fallback table. All three fields were absent in 1.29.1:

radialEnabled = true,
allowTuningInvoices = true,
customerRange = 8.0,

With /jobconfig, edit Mechanic → job → Billing: Invoice radial action (billingSettings.radialEnabled), Invoice tuning customers (billingSettings.allowTuningInvoices) and Customer distance (billingSettings.customerRange, 1–20 m). Keep existing explicit job settings. Config.Billing is the file-based compatibility fallback for missing per-job billing fields; it is not a second global configurator section.

Billing and immediate payments must be enabled. The mechanic must be on duty and have the existing CREATE_BILLING permission. A normal tuning invoice is sent to the nearest other eligible player within range; check the recipient before issuing it. The linked order remains unavailable until full payment, even if ordinary invoices allow partial payment. Cancelling the unpaid invoice closes its blocked order. Public self-service, instant tuning and administrator tuning retain their own checkout flows.

In sky_mechanicjob/config/adv_config.lua, remove Config.VehiclePush.steeringDegreesPerSecond (previous default 34.0). Steering now uses limited wheel movement; there is no replacement setting and no saved configurator key to migrate. Keep the other VehiclePush values.

Nearby owner selection associates a workshop record with a character. It does not transfer legal framework vehicle ownership. No other configuration values change.

Optional performance diagnostics

Extra profiler information remains disabled by default. For a support recording, add setr sky_profiler 1 to server.cfg before the Sky ensure lines and restart the server. In the server console, run profiler record 1000, wait for profiler status to report completion, then run profiler saveJSON sky-release-profile.json. Share that file when requested by support. Set setr sky_profiler 0 and restart again to disable the extra information. This is not a /jobconfig setting; enabling it does not start a recording or upload data automatically.

4. Apply data and inventory updates

No database migration or new item type is required. Existing invoice and order storage supports the new payment state. Copy the new images from sky_mechanicjob/config/inventory/ to the matching image directory of your inventory if you use drift_tyres, blank_plate, fake_plate_kit, plate_printer or plate_scanner. Preserve existing item definitions, workshop orders, invoices and vehicle records.

5. Restart and verify

Restart the database, framework and any edited inventory first, then Base, Jobs Base and the installed job resources. Confirm 1.30.0 and resolve startup errors before admitting players. With two players, send a tuning invoice, pay it in full and install the order. Verify that an unpaid or cancelled invoice cannot release installation. Check the selected recipient, range, cash/card payment and workshop income. Capture a nearby vehicle and owner without changing legal ownership, try a repair at the configured distance, push a vehicle gently in both directions and inspect stock quantities in an order.

1. Prepare the update

These instructions cover 1.29.0 to 1.29.1. Complete earlier updates first when upgrading from an older version. Stop the server and back up the resource, database, customized files and saved workshop settings. Install Base 1.40.1 and Jobs Base 1.43.1 before Mechanic 1.29.1.

2. Replace the runtime files

Delete the old sky_mechanicjob/source folder and insert the complete replacement from the 1.29.1 package. Replace sky_mechanicjob/fxmanifest.lua from the same package. Preserve existing configuration, locales, compatibility files and persistent data outside source.

3. Keep the existing workshops

No manual configuration values or saved /jobconfig settings change. Existing workshop shops and engine hoist locations do not need to be recreated. No SQL, item or locale migration is required, and the database must not be reset or reimported for this hotfix.

4. Restart and verify

Start Base, Jobs Base and Mechanic in that order and confirm Mechanic 1.29.1. Test a workshop without an engine hoist, then place, move and remove a hoist through /jobconfig. Verify that the changes appear for connected players and that taking an existing hoist works. Check server and client logs for recurring timeout errors.

1. Prepare the update

Update Base to 1.40.0 and Jobs Base to 1.43.0 before installing sky_mechanicjob 1.29.0. Vehicle documents also require Mechanic 1.29.0 and Police 1.32.0 together. These instructions cover 1.28.0 → 1.29.0; complete earlier migrations first when upgrading from an older version. Stop the server and back up the resource, database, customized files and saved configurator/creator data.

2. Replace the package files

Install the matching 1.29.0 package. Update every path in Changed Files, delete and reinsert sky_mechanicjob/source/*, and replace sky_mechanicjob/config/locales/* completely. Remove every exact path listed under Removed Files and apply any listed renames. Preserve unrelated files, writable data and your own custom assets; merge the configuration changes in this tab into customized public files.

Replace source/* and fxmanifest.lua from the same download even when optional diagnostics remain off. The profiler only instruments Lua inside source/ and adds its manifest entries; public configuration, integration and compatibility files must match the uninstrumented package. Apply the separate functional public-file changes listed for this release. If an older profiler package modified public files, restore those once from the clean new package and reapply your edits.

3. Merge configuration

Merge these additions into sky_mechanicjob/config/config.lua. Paste assignments after their corresponding existing parent table declarations. Both new features are disabled by default. Every path in this table was absent in 1.28.0:

Config.ToggleFeatures.kuv = false
Config.ToggleFeatures.vehicleRegistration = false

Config.KUV = {
    validityDays = 30, -- Real-time days; configurable in /jobconfig.
    warningDays = 2,
    fee = 500,
    reinspectionFee = 200,
    maxDistance = 6.0,
    sessionSeconds = 600,
    vehicleTypes = { "automobile", "bike" },
    carChecks = { "identity", "engine", "body", "tyres", "lights", "brakes", "modifications" },
    bikeChecks = { "identity", "engine", "tyres", "lights", "brakes", "modifications" }
}

Config.VehicleRegistration = {
    requireKuv = true,
    fee = 250,
    transferFee = 150
}

Also add the complete new interaction definition. All six leaf values are new and false: Config.Interactions.vehicle_registry.public, .interaction, .unique, .marker.enabled, .npc.enabled, and .blip.enabled. This is the service-point capability definition; changing it does not create a workshop location:

Config.Interactions.vehicle_registry = {
        public = false,
        interaction = false,
        unique = false,
        marker = { enabled = false },
        npc = { enabled = false },
        blip = { enabled = false }
    }

For managed settings, open /jobconfig > sky_mechanicjob > Settings and search for the inspection/registration fields using the exact keys above. Saved overrides take precedence; missing values use the new defaults. With Config.UseJobConfigurator = false, maintain the Lua values directly. Enable only the services you want to offer.

Create a Vehicle inspection / registration point (vehicle_registry) in the workshop's Locations editor and assign it to the intended job. The vehicle must be at that point within the configured distance. Grant the relevant role permissions: 1401 reads records, 1402 performs inspections, 1403 handles registration/deregistration, and 1404 revokes documents issued by that job. Staff must be on duty. The actual owner must be nearby and confirm with a drawn signature; selecting a nearby customer does not replace owner consent.

The defaults give inspections 30 real days of validity, a two-day warning and a ten-minute session. Registration requires a valid inspection by default. Changing validity affects new documents; it does not renew an old certificate. Ownership transfers require the registration workflow. Fees use normal Mechanic invoices, including applicable billing settings; an issued document is not proof that its invoice was paid. No additional direct payment is required by this update.

Saved instantTuningProfile.optionCostByOptionId profiles now regain missing electronic-option entries from shipped defaults during loading/import. Existing prices remain unchanged. Review the completed price list in /jobconfig after updating; no manual profile reset is required. Dyno ground settings already shipped in 1.28.0 do not require another migration.

Removed diagnostic setting: Config.HandlingEditor.debugEnabled changes from false to removed. Delete that property from a customized sky_mechanicjob/config/config.lua. Its /jobconfig key handlingEditorDebugEnabled is also retired; existing saved overrides are ignored, so no SQL deletion or settings reset is required. Detailed Handling Editor traces now follow Sky Base's central debug level. For support diagnostics, enable Config.debugLevels.debug in sky_base/config/config.lua, then restart Base and dependent resources. Restore it to its unchanged default false afterward. Keep Config.debug and Config.debugLevels.all at their unchanged default false when selecting individual levels. These Base settings are maintained in files, outside /jobconfig.

The existing Handling Editor performance controls remain unchanged: Config.HandlingEditor.performanceChecksEnabled = true, Config.HandlingEditor.performanceWarningMs = 25, Config.HandlingEditor.payloadWarningBytes = 262144, and Config.HandlingEditor.performanceSummaryIntervalMs = 60000. Threshold warnings now respect Base's central warning level; enabling debug is not required for those warnings.

Optional performance diagnostics

Extra profiler information remains disabled by default. Normal use needs no diagnostic setting. For a support recording, add setr sky_profiler 1 to server.cfg before the Sky ensure lines and restart the server. In the server console, run profiler record 1000, wait for profiler status to report completion, then run profiler saveJSON sky-release-profile.json. Share that file only when requested by support. Set setr sky_profiler 0 and restart again to disable the extra information. This is not a /jobconfig option; enabling it does not start a recording or upload data automatically.

4. Apply data and inventory updates

Back up the vehicle, registry and invoice tables. The normal Mechanic startup migration adds sky_mechanic_invoices.registry_operation_id CHAR(36) NULL and unique index uniq_mechanic_registry_operation when Config.AutoExecuteQuery = true.

With automatic SQL disabled, run the shipped sky_mechanicjob/vehicle_registry.sql against the existing game database. Merely rerunning the invoice CREATE TABLE IF NOT EXISTS in import.sql does not add this column to an existing table. For new installations, the updated import.sql includes it.

Complete the Base owned-vehicle identifier upgrade and import sky_jobs_base/vehicle_registry.sql when Jobs Base automatic SQL is disabled. The shared finance update also needs sky_jobs_logs.payment_reference and its unique index; follow Jobs Base 1.43.0 before starting Mechanic. Keep existing ownership, tuning, invoice and document data. No new items are required. Never clear the registry, regenerate vehicle IDs or issue old certificates automatically to resolve a migration error.

5. Restart and verify

Confirm version 1.29.0 and all schema migrations. Leave both new switches off until a test workshop, permissions and service point are ready. With the owner nearby, issue an inspection, sign it, register the vehicle and inspect the history from Mechanic and Police. Check expiry, owner rejection, off-duty rejection and one invoice per operation. Verify the actual society credit separately from document issuance. Then test an existing instant-tuning profile, a garage vehicle with extras, propulsion changes and the eight-gear confirmation. With two clients, test engine-sound preview, cancellation and saved restoration after a garage spawn, streaming away/back and a change of vehicle controller. Check that a nearby dynamometer observer sees the current engine revs. With central debug disabled, verify that ordinary Handling Editor use and player disconnect do not force debug traces; enable the debug level for a support trace and restore it afterward.

1. Prepare the update.

Update sky_base to 1.39.0 and sky_jobs_base to 1.42.0 before installing sky_mechanicjob 1.28.0. These steps cover 1.27.1 → 1.28.0. Follow earlier update instructions first when upgrading from an older version. Stop the server and back up the resource, database, custom settings, and saved configurator data.

2. Replace the package files.

Install the matching 1.28.0 package. Update every path listed in Changed Files, delete and reinsert sky_mechanicjob/source/*, and replace sky_mechanicjob/config/locales/* completely. Merge the configuration changes in this tab into your customized files. Preserve writable data and generated user content.

Required profiler files

For the profiler update, replace the complete sky_mechanicjob/source/* tree and sky_mechanicjob/fxmanifest.lua from the same download, even if diagnostics stay disabled. Delete the old source/ folder before copying the new one.

The profiler builder leaves configuration, integration and compatibility files unchanged. Apply any separate configuration or integration changes listed for this release as usual.

If you previously installed an older profiler package that also modified files outside source/, restore those affected files once from the unmodified versions in the new download and reapply your custom edits. Later profiler-only updates do not require this step.

3. Merge and review configuration.

In sky_mechanicjob/config/config.lua, add the previously absent feature switch:

Config.ToggleFeatures.handlingEditor = true

The new default true keeps the handling editor and its automatic plate/model rules enabled. Set it to false to disable both. This is separate from the existing Config.ToggleFeatures.customHandling, which remains unchanged. With Config.UseJobConfigurator = true, use Mechanic → Features → Handling editor, feature key handlingEditor; saved feature overrides take precedence. With the configurator disabled, use the file value. Respawn vehicles after disabling previously applied handling changes; switching the feature off does not reset vehicles already in the world.

In sky_mechanicjob/config/adv_config.lua, delete Config.MobileDyno.placement.acceptedMaterials. The old list was { "tarmac", "concrete_pavement", "paving_slab", "road", "concrete", "concrete_solid" }; it is no longer read. There is no replacement material list. maxSlopeDegrees = 1.0, maxHeightSpread = 0.04, rayStartHeight = 2.0, rayDepth = 5.0, and the footprint probes stay unchanged. Placement still needs valid, sufficiently flat ground. The removed material list and the model-specific probes are file settings; existing /jobconfig slope and height settings continue to apply.

Before using the new tuning save path, follow Garage Integration and the matching ESX, QBCore, or Ox instructions. Some framework versions need the documented vehicle-property additions to preserve paint types and separate livery values. Check your actual installed files and keep custom changes. In particular, QBCore with MSK Garage 5.6 needs a review of the different vehicle-property formats; installing field additions alone does not establish compatibility.

Optional performance diagnostics

Sky's extra profiler information is disabled by default. This update does not start recordings or send data automatically. No configuration change is required for normal use. If support needs a performance recording, add the following line to server.cfg before the Sky ensure lines, then restart the server:

setr sky_profiler 1

This global setting is configured in server.cfg; it is not managed by /jobconfig. The previous state with no setting remains disabled. Set the value to 1 only when you want the additional diagnostics.

Run profiler record 1000 in the server console for a server delay, or in the player's F8 console for a client problem. Reproduce the issue during the recording. Wait until profiler status reports that recording has stopped, then run profiler saveJSON sky-profile.json in the same console to save the capture. These are the standard FiveM profiler commands.

After diagnostics, change the line to setr sky_profiler 0 and restart again. Keep the new package files installed; disabling diagnostics does not require editing Lua or removing manifest entries.

4. Apply database and item changes.

Back up sky_mechanic_vehicle_tuning and your framework's owned-vehicle table before the first start. The automatic migration, controlled by Config.AutoExecuteQuery, adds nullable legacy_properties LONGTEXT DEFAULT NULL to sky_mechanic_vehicle_tuning and ensures a non-unique plate index on owned_vehicles (ESX) or player_vehicles (QBCore/Qbox) when needed. Existing suitable indexes and vehicle rows are retained.

If Config.AutoExecuteQuery = false, run the VEHICLE OWNERSHIP INDEX block from sky_mechanicjob/import.sql against your active database. It starts with SET @sky_mechanic_ownership_table = 'owned_vehicles';; change that value to 'player_vehicles' for QBCore/Qbox. Then run:

ALTER TABLE `sky_mechanic_vehicle_tuning`
    ADD COLUMN IF NOT EXISTS `legacy_properties` LONGTEXT NULL;

Confirmed tuning now updates owned_vehicles.vehicle on ESX, the existing QBCore/Qbox vehicle properties, or the Sky job-garage vehicle record. On conversion, the previous full Mechanic snapshot is saved once in legacy_properties; Mechanic-specific extras remain in its active record. Existing vehicles are not converted in bulk. Keep those backup values and verify an existing vehicle after a confirmed save. The older /migrate command is not a bulk conversion tool for this change.

Replace all Mechanic locales. No new inventory item, image, streamed model, or provider secret is introduced by this release.

5. Start and verify the update.

Confirm a tuning purchase, check the existing garage record, and retrieve the vehicle twice. Verify paint, RGB-to-palette changes, liveries, extras, engine sound, and handling before entering the vehicle and from a second player's view. Cancel a paint preview and confirm unrelated tuning stays intact. Test drivetrain conversion, the handling-editor switch, and a mobile dyno on valid flat ground. Check persistence again after a server restart.

1. Update sky_jobs_base to 1.41.1 and use sky_base 1.38.0 before updating sky_mechanicjob. These steps cover 1.27.0 → 1.27.1; complete earlier release instructions first if you are upgrading from an older version. Stop the server and back up the resource, database, saved Job Configurator settings and custom configuration. Preserve generated reports and other writable data.
2. Install 1.27.1 as a matching package. Update every path in Changed Files, delete and reinsert sky_mechanicjob/source/*, and replace sky_mechanicjob/config/locales/* completely. Merge the configuration instructions in this tab into customized files; retain intentional settings and persistent data.
3. Review the configuration steps.

No config/config.lua, config/adv_config.lua or /jobconfig value changes are required for this patch. Keep existing Anti-Lag, vehicle persistence, payment and Mobile Dyno settings. The Anti-Lag correction supports the existing temporary tuning path for spawned vehicles; it does not make those vehicles persistent across deletion or server restarts.

Sharing is available from a completed measurement owned by the operator. Open the sharing controls, select a nearby player and send the result. Existing duty, distance and session checks still apply. No additional monitor is required for direct player sharing.

4. Apply the data, inventory and asset steps.

Replace sky_mechanicjob/stream/sky_mobile_dyno.ydr and sky_mechanicjob/stream/sky_mechanic_props.ytyp together with the matching source package. The corrected placement uses updated collision bounds; no manual station Z offset is required for the shipped model. Replace all sky_mechanicjob/config/locales/* for the sharing controls.

No new SQL migration, inventory item, image or provider secret is introduced. Preserve stored tuning, Dyno measurements, orders and balances. Follow any unfinished 1.27.0 installation steps when upgrading from an older version.

5. Start providers, Base, Jobs Base and Mechanic in that order. Check a tuning purchase with insufficient and sufficient funds, Anti-Lag on a spawned vehicle, mobile Dyno placement, leaving its tablet view and sharing a completed measurement with a second nearby player.

1. Update sky_base to 1.38.0 and sky_jobs_base to 1.41.0 before updating sky_mechanicjob. Stop the server and back up the complete sky_mechanicjob resource, its database and inventory data, saved Job Configurator settings where applicable, and intentional public configuration edits. Preserve writable reports and other generated data outside the replaceable source files.
2. Install 1.27.0 as a consistent package. Replace every file listed in Changed Files, delete and reinsert sky_mechanicjob/source/*, and replace sky_mechanicjob/config/locales/* completely. Merge the public configuration changes listed in this tab into your customized files; do not copy old configuration files over the new package wholesale. Keep the manifest, built UI, runtime and dependencies from the matching release set.
3. Apply the following configuration changes before starting the resource.

In sky_mechanicjob/config/config.lua, add the complete Config.Keybinds block. This table and its paths were absent in 1.26.0; 1.27.0 uses the following string defaults instead of scattered settings or fixed controls. Preserve your chosen keys when transferring old settings.

Config.Keybinds = {
    mechanicDynoControl38 = "E",
    mechanicDynoControl47 = "G",
    mechanicDynoControl174 = "LEFT",
    mechanicDynoControl175 = "RIGHT",
    mechanicDynoControl172 = "UP",
    mechanicDynoControl173 = "DOWN",
    mechanicDynoControl45 = "R",
    mechanicDynoControl177 = "BACK",
    mechanicSprayPaintControl202 = "ESCAPE",
    mechanicSprayPaintControl200 = "ESCAPE",
    mechanicVehicleCareControl202 = "ESCAPE",
    mechanicVehicleCareControl200 = "ESCAPE",
    mechanicWheelChangeControl22 = "SPACE",
    mechanicWheelChangeControl200 = "ESCAPE",
    mechanicWheelChangeControl202 = "ESCAPE",
    mechanicCatalyticConverterCATALYTICACTIONCONTROL = "E",
    mechanicCatalyticConverterCATALYTICCANCELCONTROL = "X",
    mechanicWheelTheftWHEELTHEFTACTIONCONTROL = "E",
    mechanicWheelTheftWHEELTHEFTCANCELCONTROL = "X",
    mechanicVehiclePushINPUTMOVEUP = "W",
    mechanicVehiclePushINPUTMOVEDOWN = "S",
    mechanicVehiclePushINPUTMOVELEFT = "A",
    mechanicVehiclePushINPUTMOVERIGHT = "D",
    mechanicVehiclePushINPUTSPRINT = "LSHIFT",
    mechanicVehiclePushINPUTCONTEXT = "E",
    nitroActivationKey = "LSHIFT",
    tuningFocusKey = "SPACE",
    handlingEditorFocusKey = "F7",
}

With Config.UseJobConfigurator = true, open /jobconfig → this resource → General → Keybinds. Every key inside the block is also its exact saved setting ID; for example Config.Keybinds.mechanicDynoControl38 is saved under the same final name. Saved overrides take precedence over the generated defaults. Numeric overrides migrate to their corresponding QWERTY key, and -1 migrates to an empty string. An empty string means no initial binding. Players retain their own assignments in Settings → Key Bindings → FiveM; changing a server default does not overwrite those assignments.

With Config.UseJobConfigurator = false, edit these paths in the file and restart the resource. Keep mouse/controller prefixes exactly as shown. Command permissions and Config.AutoExecuteQuery remain file settings; their reordering does not change their values.

Remove the following old paths after transferring your overrides. The new paths all live in config/config.lua; the saved setting ID is the final segment of each new path.

Move Config.AutoExecuteQuery and the complete Config.CommandPermissions table from sky_mechanicjob/config/adv_config.lua to sky_mechanicjob/config/config.lua, preserving your existing values and groups. Remove the old definitions from adv_config.lua so they cannot overwrite the new table. Add the previously absent permission and feature flag:

Config.CommandPermissions.handlingeditor = { "god", "superadmin", "admin" }
Config.ToggleFeatures.mobileDyno = true

The permission remains plaintext/global. mobileDyno is a saved /jobconfig feature toggle. Add the complete new handling editor block to config/config.lua; all these paths were absent in 1.26.0:

Config.HandlingEditor = {
    defaultTab = "advanced", -- simple, advanced, flags, inspector, telemetry, profiles, fleet, export
    -- Suggested percentage window above/below the captured vehicle basis.
    -- A non-default field maximum below takes precedence over the upper endpoint.
    -- The vehicle basis remains stable after Apply, so reopening cannot compound this range.
    sliderMaximumDeviationPercent = 30,
    -- Optional hard maximums for every numeric handling field. Fields not listed here use the
    -- default maximum from data/handling_editor_schema.json (fallback: 1,000,000,000).
    -- Overrides may raise or lower that default, up to the editor's numeric ceiling of
    -- 1,000,000,000 (2,147,483,647 for integers). The same limits are editable in /jobconfig; they do not
    -- change a vehicle value by themselves. A non-default maximum is also the slider endpoint;
    -- fields using their default maximum retain the suggested vehicle-basis slider window.
    -- Example: ["CHandlingData.fInitialDriveMaxFlatVel"] = 250.0,
    fieldMaximums = {},
    layerInspectorEnabled = true,
    fieldDocumentationEnabled = true,
    validatorEnabled = true,
    blockCriticalValidation = true,
    telemetryCoachEnabled = true,
    profileVersioningEnabled = true,
    fleetManagerEnabled = true,
    flagSearchEnabled = true,
    workspacesEnabled = true,
    maxProfileRevisions = 30,
    maxFleetResults = 200,
    maxWorkspacesPerAdmin = 12,
    coachMinimumSamples = 20,
    coachWheelSlipWarningKmh = 12.0,
    coachMinimumBrakeDeceleration = 6.0,
    -- Detailed traces are opt-in; threshold warnings use the queued Sky.Debug logger.
    debugEnabled = false,
    performanceChecksEnabled = true,
    performanceWarningMs = 25,
    payloadWarningBytes = 262144,
    performanceSummaryIntervalMs = 60000
}

With /jobconfig, the saved keys are handlingEditorDefaultTab, handlingEditorSliderMaximumDeviationPercent, handlingEditorLayerInspectorEnabled, handlingEditorFieldDocumentationEnabled, handlingEditorValidatorEnabled, handlingEditorBlockCriticalValidation, handlingEditorTelemetryCoachEnabled, handlingEditorProfileVersioningEnabled, handlingEditorFleetManagerEnabled, handlingEditorFlagSearchEnabled, handlingEditorWorkspacesEnabled, handlingEditorMaxProfileRevisions, handlingEditorMaxFleetResults, handlingEditorMaxWorkspacesPerAdmin, handlingEditorCoachMinimumSamples, handlingEditorCoachWheelSlipWarningKmh, handlingEditorCoachMinimumBrakeDeceleration, handlingEditorDebugEnabled, handlingEditorPerformanceChecksEnabled, handlingEditorPerformanceWarningMs, handlingEditorPayloadWarningBytes, and handlingEditorPerformanceSummaryIntervalMs. They map to the same suffixes in Config.HandlingEditor. Each Config.HandlingEditor.fieldMaximums[field_id] override uses the exact saved key handlingEditorMaximum__<field_id> and must be checked under the matching handling field. Saved overrides win; changing a maximum does not itself change a vehicle. With the configurator disabled, the file is authoritative.

Add the complete new Config.MobileDyno block to sky_mechanicjob/config/adv_config.lua. Every path in this block was absent in 1.26.0; retain the model-specific coordinates for the supplied models only:

Config.MobileDyno = {
    itemPlacement = {
        enabled = true,
        stationItem = "mobile_dyno",
        monitorItem = "mobile_dyno_monitor",
        consumeItem = true,
        returnItemOnRemove = true,
        persistPlacedProps = false,
        removeDistance = 3.5,
    },
    model = "sky_mobile_dyno",
    requireOnDuty = true,
    interactionDistance = 3.5,
    serverInteractionDistance = 20.0,
    maxVehicleDistance = 7.0,
    maxActiveSessionsPerJob = 3,
    duiDistance = 65.0,
    historyLimit = 20,
    countdownMs = 3000,
    cooldownMs = 2400,
    fullLoadDurationMs = 15000,
    telemetryIntervalMs = 100,
    -- Converts normalized engine RPM into the visual wheel-rotation native's
    -- units. This is vehicle/native presentation tuning and remains Lua-only.
    wheelSpeedMultiplier = 72.0,
    -- The panel quad is calibrated against the actual front glass vertices of
    -- sky_mobile_dyno. Rendering the DUI directly avoids the model's rotated
    -- and cropped texture mapping. This geometry intentionally remains Lua-only.
    screen = {
        width = 1024,
        height = 610,
        topLeft = { x = 1.36335, y = -2.14804, z = 1.61428 },
        topRight = { x = 1.87627, y = -2.14808, z = 1.61442 },
        bottomLeft = { x = 1.36149, y = -2.17236, z = 1.30767 },
        bottomRight = { x = 1.87844, y = -2.17224, z = 1.30729 }
    },
    rollers = {
        centerX = -1.35,
        leftTrackY = 0.78,
        rightTrackY = -0.78,
        longitudinalTolerance = 0.75,
        lateralTolerance = 0.55,
        chassisLongitudinalTolerance = 1.90,
        chassisLateralTolerance = 1.10,
        headingTolerance = 12.0,
        maximumSpeed = 0.25
    },
    fanController = {
        offset = { x = 3.28, y = 0.0, z = 0.82 },
        interactionDistance = 1.35
    },
    -- Thermal rates and thresholds form one coherent simulation/safety contract.
    -- They intentionally remain Lua-only instead of exposing independently
    -- adjustable values that could invalidate the model through /jobconfig.
    thermal = {
        ambientC = 24.0,
        initial = { engine = 86.0, oil = 78.0, coolant = 84.0 },
        heatPerSecond = { engine = 1.10, oil = 1.24, coolant = 0.92 },
        passiveCoolingPerSecond = { engine = 0.045, oil = 0.035, coolant = 0.050 },
        fanCoolingPerSecond = { engine = 0.34, oil = 0.20, coolant = 0.46 },
        warning = { engine = 112.0, oil = 128.0, coolant = 106.0 },
        critical = { engine = 124.0, oil = 145.0, coolant = 118.0 },
        powerLossStart = { engine = 100.0, oil = 112.0, coolant = 98.0 },
        maximumPowerLoss = 0.10,
        minimumEngineHealth = 350.0,
        cacheLifetimeMs = 1800000
    },
    -- Surface material identifiers and footprint probes form a model-specific
    -- world-placement contract and intentionally remain Lua-only.
    placement = {
        maxSlopeDegrees = 1.0,
        maxHeightSpread = 0.04,
        rayStartHeight = 2.0,
        rayDepth = 5.0,
        acceptedMaterials = {
            "tarmac",
            "concrete_pavement",
            "paving_slab",
            "road",
            "concrete",
            "concrete_solid"
        },
        probes = {
            { x = -4.55, y = -1.65 },
            { x = -4.55, y = 0.0 },
            { x = -4.55, y = 1.65 },
            { x = -1.00, y = -1.65 },
            { x = -1.00, y = 0.0 },
            { x = -1.00, y = 1.65 },
            { x = 2.80, y = -1.65 },
            { x = 2.80, y = 0.0 },
            { x = 2.80, y = 1.65 }
        }
    },
    -- The calibrated result-monitor screen quad is coupled to
    -- prop_tv_stand_01 and intentionally remains Lua-only.
    resultMonitor = {
        model = "prop_tv_stand_01",
        renderDistance = 55.0,
        width = 1280,
        height = 720,
        screen = {
            topLeft = { x = -0.659, y = -0.148, z = 1.876 },
            topRight = { x = 0.655, y = -0.148, z = 1.876 },
            bottomLeft = { x = -0.659, y = -0.148, z = 1.138 },
            bottomRight = { x = 0.655, y = -0.148, z = 1.138 }
        }
    },
    animation = {
        full = { dictionary = "sky_mobile_dyno", clip = "dyno_spin" },
        rollers = { dictionary = "sky_mobile_dyno_rollers", clip = "rollers_spin" },
        fans = { dictionary = "sky_mobile_dyno_fans", clip = "fans_spin" }
    },
    -- Stage shapes are a trusted test-program contract. The operator-facing
    -- full-load duration is managed separately through /jobconfig.
    profileOrder = { "sweep", "full_load", "hold", "coastdown" },
    profiles = {
        sweep = {
            label = "Advanced Power Sweep",
            stages = {
                { key = "warmup", durationMs = 3000, startRpm = 0.20, endRpm = 0.32, throttle = 0.30, load = 0.20 },
                { key = "ramp", durationMs = 9000, startRpm = 0.32, endRpm = 0.96, throttle = 1.00, load = 0.92 },
                { key = "full_load", durationMs = 15000, fullLoad = true, startRpm = 0.96, endRpm = 0.96, throttle = 1.00, load = 1.00 },
                { key = "coastdown", durationMs = 6000, startRpm = 0.96, endRpm = 0.18, throttle = 0.00, load = 0.12 }
            }
        },
        full_load = {
            label = "15s Full Load",
            stages = {
                { key = "warmup", durationMs = 4000, startRpm = 0.20, endRpm = 0.36, throttle = 0.35, load = 0.25 },
                { key = "ramp", durationMs = 6000, startRpm = 0.36, endRpm = 0.94, throttle = 1.00, load = 0.90 },
                { key = "full_load", durationMs = 15000, fullLoad = true, startRpm = 0.94, endRpm = 0.98, throttle = 1.00, load = 1.00 },
                { key = "recovery", durationMs = 5000, startRpm = 0.98, endRpm = 0.24, throttle = 0.00, load = 0.10 }
            }
        },
        hold = {
            label = "Steady-State Hold",
            stages = {
                { key = "warmup", durationMs = 3500, startRpm = 0.20, endRpm = 0.34, throttle = 0.30, load = 0.20 },
                { key = "ramp", durationMs = 5000, startRpm = 0.34, endRpm = 0.72, throttle = 0.78, load = 0.68 },
                { key = "steady_hold", durationMs = 15000, startRpm = 0.72, endRpm = 0.72, throttle = 0.78, load = 0.75 },
                { key = "recovery", durationMs = 4500, startRpm = 0.72, endRpm = 0.22, throttle = 0.00, load = 0.10 }
            }
        },
        coastdown = {
            label = "Extended Coastdown",
            stages = {
                { key = "warmup", durationMs = 3000, startRpm = 0.20, endRpm = 0.34, throttle = 0.30, load = 0.20 },
                { key = "ramp", durationMs = 8000, startRpm = 0.34, endRpm = 0.96, throttle = 1.00, load = 0.88 },
                { key = "coastdown", durationMs = 12000, startRpm = 0.96, endRpm = 0.16, throttle = 0.00, load = 0.08 },
                { key = "recovery", durationMs = 3000, startRpm = 0.16, endRpm = 0.20, throttle = 0.00, load = 0.08 }
            }
        }
    }
}

The managed Dyno settings and exact file paths are:

Review these values in Mobile Dyno and saved installations. The default tablet operating distance is 20.0 metres, pickup distance is 3.5, and requireOnDuty stays enabled in the new block. Item placements are not persistent by default. Model identifiers, screen geometry, roller geometry, animation definitions, thermal simulation and test-profile shapes remain plaintext Lua settings; they are not ordinary saved location fields. Place the supplied Dyno on a valid flat surface and use the editor for each installation rather than copying one model's coordinates to another model. Existing explicit overrides remain effective.

Remove Config.Jobs[*].tuningCostProfile.optionCostByOptionId.electronic_exhaust_smoke_color, including its enabled and complete cost table. This option was enabled in the old shipped workshop, with prices from 0.0 to 4.65 and ecu_tuning_kit requirements; it has no replacement. The updated runtime retires old job and instant-tuning overrides and ignores old vehicle smoke-color values. Keep paid historical orders and existing ECU kits for their remaining supported uses and refund handling. No Two-Step default value changes in this release; retain your current Two-Step settings.

4. Complete the following database, inventory, and asset steps.

With Config.AutoExecuteQuery = true, let startup create the seven new handling tables. Otherwise apply the matching new sky_mechanicjob/import.sql statements before starting the resource. Existing vehicle tuning, Dyno result history, orders and balances must be retained. Exact new schema:

CREATE TABLE IF NOT EXISTS `sky_mechanic_handling_profiles` (
    `id` INT NOT NULL AUTO_INCREMENT,
    `name` VARCHAR(64) NOT NULL,
    `vehicle_label` VARCHAR(120) NULL,
    `vehicle_model` VARCHAR(64) NULL,
    `vehicle_model_hash` BIGINT UNSIGNED NULL,
    `handling_name` VARCHAR(64) NULL,
    `snapshot` LONGTEXT NOT NULL,
    `created_by_identifier` VARCHAR(120) NULL,
    `created_by_name` VARCHAR(120) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    INDEX `idx_mechanic_handling_profiles_name` (`name`),
    INDEX `idx_mechanic_handling_profiles_model` (`vehicle_model_hash`)
);

CREATE TABLE IF NOT EXISTS `sky_mechanic_handling_overrides` (
    `id` INT NOT NULL AUTO_INCREMENT,
    `scope` VARCHAR(16) NOT NULL,
    `target_key` VARCHAR(80) NOT NULL,
    `target_label` VARCHAR(120) NOT NULL,
    `vehicle_model_hash` BIGINT UNSIGNED NULL,
    `profile_name` VARCHAR(64) NULL,
    `snapshot` LONGTEXT NOT NULL,
    `created_by_identifier` VARCHAR(120) NULL,
    `created_by_name` VARCHAR(120) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uniq_mechanic_handling_override` (`scope`, `target_key`),
    INDEX `idx_mechanic_handling_overrides_scope` (`scope`),
    INDEX `idx_mechanic_handling_overrides_model` (`vehicle_model_hash`)
);

CREATE TABLE IF NOT EXISTS `sky_mechanic_handling_runs` (
    `id` INT NOT NULL AUTO_INCREMENT,
    `vehicle_label` VARCHAR(120) NULL,
    `vehicle_model_hash` BIGINT UNSIGNED NOT NULL,
    `plate` VARCHAR(24) NULL,
    `mode` VARCHAR(16) NOT NULL,
    `top_speed` DECIMAL(8,2) NOT NULL DEFAULT 0,
    `distance` DECIMAL(10,2) NOT NULL DEFAULT 0,
    `elapsed` DECIMAL(10,3) NOT NULL DEFAULT 0,
    `max_acceleration` DECIMAL(8,3) NOT NULL DEFAULT 0,
    `max_deceleration` DECIMAL(8,3) NOT NULL DEFAULT 0,
    `max_wheel_slip` DECIMAL(8,3) NOT NULL DEFAULT 0,
    `zero_to_sixty` DECIMAL(10,3) NULL,
    `zero_to_hundred` DECIMAL(10,3) NULL,
    `zero_to_two_hundred` DECIMAL(10,3) NULL,
    `hundred_to_zero` DECIMAL(10,3) NULL,
    `quarter_mile` DECIMAL(10,3) NULL,
    `kilometer` DECIMAL(10,3) NULL,
    `samples` LONGTEXT NOT NULL,
    `created_by_identifier` VARCHAR(120) NULL,
    `created_by_name` VARCHAR(120) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    INDEX `idx_mechanic_handling_runs_model` (`vehicle_model_hash`, `created_at`),
    INDEX `idx_mechanic_handling_runs_plate` (`plate`, `created_at`)
);

CREATE TABLE IF NOT EXISTS `sky_mechanic_handling_profile_revisions` (
    `id` INT NOT NULL AUTO_INCREMENT,
    `profile_id` INT NOT NULL,
    `revision` INT NOT NULL,
    `note` VARCHAR(500) NULL,
    `release_status` VARCHAR(16) NOT NULL DEFAULT 'draft',
    `telemetry_run_id` INT NULL,
    `snapshot` LONGTEXT NOT NULL,
    `created_by_identifier` VARCHAR(120) NULL,
    `created_by_name` VARCHAR(120) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uniq_mechanic_handling_profile_revision` (`profile_id`, `revision`),
    INDEX `idx_mechanic_handling_revisions_profile` (`profile_id`, `created_at`)
);

CREATE TABLE IF NOT EXISTS `sky_mechanic_handling_preferences` (
    `identifier` VARCHAR(120) NOT NULL,
    `preferences` LONGTEXT NOT NULL,
    `favorites` LONGTEXT NOT NULL,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    PRIMARY KEY (`identifier`)
);

CREATE TABLE IF NOT EXISTS `sky_mechanic_handling_workspaces` (
    `id` INT NOT NULL AUTO_INCREMENT,
    `owner_identifier` VARCHAR(120) NOT NULL,
    `owner_name` VARCHAR(120) NULL,
    `name` VARCHAR(64) NOT NULL,
    `vehicle_label` VARCHAR(120) NULL,
    `vehicle_model_hash` BIGINT UNSIGNED NULL,
    `snapshot` LONGTEXT NOT NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    `updated_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    UNIQUE KEY `uniq_mechanic_handling_workspace_owner_name` (`owner_identifier`, `name`),
    INDEX `idx_mechanic_handling_workspaces_owner` (`owner_identifier`, `updated_at`)
);

CREATE TABLE IF NOT EXISTS `sky_mechanic_handling_fleet_history` (
    `id` INT NOT NULL AUTO_INCREMENT,
    `scope` VARCHAR(16) NOT NULL,
    `target_key` VARCHAR(80) NOT NULL,
    `target_label` VARCHAR(120) NOT NULL,
    `vehicle_model_hash` BIGINT UNSIGNED NULL,
    `action` VARCHAR(24) NOT NULL,
    `snapshot` LONGTEXT NULL,
    `created_by_identifier` VARCHAR(120) NULL,
    `created_by_name` VARCHAR(120) NULL,
    `created_at` DATETIME NOT NULL DEFAULT CURRENT_TIMESTAMP,
    PRIMARY KEY (`id`),
    INDEX `idx_mechanic_handling_fleet_target` (`scope`, `target_key`, `created_at`),
    INDEX `idx_mechanic_handling_fleet_created` (`created_at`)
);

Register mobile_dyno (weight 25000) and mobile_dyno_monitor (weight 5000) in the active inventory. The ESX-style items inserts in import.sql are idempotent; QBCore, Qbox and ox_inventory normally need their own shared item definitions. The runtime registers usable actions through the shared prop service. Copy the new config/inventory/mobile_dyno.png and config/inventory/mobile_dyno_monitor.png into the inventory's image directory.

Install every listed Dyno stream file, the updated stream/sky_mechanic_props.ytyp, both new audio configuration files, data/handling_editor_schema.json, the matching manifest, complete locales and complete built source folder. The manifest now points to the archetype inside stream/ and loads the Dyno audio mix. Do not carry an older manifest forward. No new provider secret is required.

5. Start the matching dependencies and Mechanic, then verify all seven handling tables and both usable items. Place/cancel/pick up a Dyno and monitor, check duty and range rejection, prepare cooling fans, run seated and external tests, and check start/stop cleanup, temperatures, graphs, fan dragging, saved history and monitor sharing. Open /handlingeditor with an authorized administrator, apply two successive edits, reopen, test profile revisions, XML clipboard export/import, field limits, fleet rules and driving telemetry. Verify unsupported/failed live changes report an error, Escape closes only the open dropdown, and drivers can toggle installed Anti-Lag. Confirm smoke-color ordering is unavailable while historical refunds remain intact.

1. Install sky_base 1.37.0 and sky_jobs_base 1.40.0, stop the server, and back up the complete Mechanic resource, Job Configurator data, tuning data, and intentional configuration edits.
2. Delete the old folder and install the complete 1.26.0 package. Do not mix 1.25.0 manifest, advanced config, standard config, locales, UI, or source files with this release.
3. Let the first start migrate saved /jobconfig profiles, then confirm electronic_exhaust_smoke_color under each intended job's tuningCostProfile.optionCostByOptionId. Level 0 is free with no item; levels 1 through 10 use a cost value of 4.65 and require ecu_tuning_kit. Do not create a parallel tuningCostProfile.options table.
4. Add Config.TwoStep.defaultEnabled = false and Config.TwoStep.inactiveCheckIntervalMs = 125 to config/adv_config.lua. /jobconfig manages only the coarse Config.ToggleFeatures.twoStep switch; these low-level values remain plaintext deployment settings.
5. Add custom tuning artwork below config/img only when needed. No SQL migration or new inventory item is required; the new tuning option reuses ecu_tuning_kit.
6. Restart Base, Jobs Base, and Mechanic in order. Verify exhaust-smoke colors and persistence, anti-lag previews, ECU diagnostics, Two-Step defaults/input/torque, runtime plate styles, creator refresh, queued deliveries, and engine-hoist handling.

1. Install sky_base 1.36.0 and sky_jobs_base 1.39.0, stop the server, and back up the complete Mechanic resource, inventory definitions/data, Job Configurator tables, mechanic tables, and intentional config/provider edits.
2. Delete the old folder and install the complete 1.25.0 package. Do not mix the old manifest, built UI, locales, source, config defaults, or fake-plate compatibility files with this release.
3. Add Config.ToggleFeatures.electronicTuning = true and Config.ToggleFeatures.brakeOverheating = true; both paths were absent in 1.24.1. With /jobconfig, the saved feature keys electronicTuning and brakeOverheating override these file defaults.
4. Add this complete new plaintext/default brake block exactly as shipped:
   config/config.lua

   Config.BrakeOverheating = {
       simulationIntervalMs = 100,
       visualDistance = 55.0,
       maximumVisibleVehicles = 16,
       minimumSpeedKmh = 25.0,
       referenceSpeedKmh = 120.0,
       heatGainPerSecond = 8.0,
       coolingPerSecond = 0.34,
       coolingDelayMs = 5000,
       heatUp = {
           classes = {
               [0] = 0.9, [1] = 1.0, [2] = 1.1, [3] = 1.0, [4] = 1.0, [5] = 0.9,
               [6] = 0.85, [7] = 0.8, [8] = 0.5, [9] = 0.9, [10] = 0.7, [11] = 0.7,
               [12] = 1.0, [17] = 1.0, [18] = 0.7, [19] = 0.7, [20] = 1.0, [22] = 0.8
           },
           brakeUpgrade = { [-1] = 1.0, [0] = 0.8, [1] = 0.65, [2] = 0.6 }
       },
       cooldown = {
           classes = {
               [0] = 1.0, [1] = 1.0, [2] = 1.0, [3] = 1.0, [4] = 1.1, [5] = 1.1,
               [6] = 1.15, [7] = 1.25, [8] = 1.5, [9] = 1.0, [10] = 1.0, [11] = 1.0,
               [12] = 1.0, [17] = 1.0, [18] = 1.15, [19] = 1.15, [20] = 1.0, [22] = 1.25
           },
           brakeUpgrade = { [-1] = 1.0, [0] = 1.1, [1] = 1.25, [2] = 1.5 }
       },
       stages = { warm = 35.0, hot = 60.0, critical = 85.0 },
       glow = {
           [1] = { radius = 0.16, red = 255, green = 105, blue = 20, intensity = 0.45 },
           [2] = { radius = 0.19, red = 255, green = 65, blue = 8, intensity = 0.7 },
           [3] = { radius = 0.22, red = 255, green = 32, blue = 3, intensity = 1.0 }
       },
       sparks = {
           asset = "des_scaffolding",
           effect = "ent_ray_scaf_spark_bursts",
           scale = 0.5,
           minimumIntervalMs = 180,
           maximumIntervalMs = 420
       },
       brakeFade = {
           chancePerSecond = 0.45,
           minimumDurationMs = 300,
           maximumDurationMs = 700,
           cooldownMs = 1800
       },
       wheelBones = {
           "wheel_lf", "wheel_rf", "wheel_lr", "wheel_rr",
           "wheel_lm1", "wheel_rm1", "wheel_lm2", "wheel_rm2"
       },
       excludedVehicleClasses = { [13] = true, [14] = true, [15] = true, [16] = true, [21] = true }
   }
   

   
   /jobconfig stores the two feature flags plus these exact settings: brakeOverheatingMinimumSpeedKmh, brakeOverheatingReferenceSpeedKmh, brakeOverheatingHeatGainPerSecond, brakeOverheatingCoolingPerSecond, brakeOverheatingCoolingDelayMs, brakeOverheatingHeatClassMultipliers, brakeOverheatingHeatBrakeUpgradeMultipliers, brakeOverheatingCooldownClassMultipliers, brakeOverheatingCooldownBrakeUpgradeMultipliers, brakeOverheatingWarmThreshold, brakeOverheatingHotThreshold, brakeOverheatingCriticalThreshold, brakeOverheatingVisualDistance, brakeOverheatingSparkMinimumIntervalMs, brakeOverheatingSparkMaximumIntervalMs, brakeOverheatingFadeChancePerSecond, brakeOverheatingFadeMinimumDurationMs, brakeOverheatingFadeMaximumDurationMs, and brakeOverheatingFadeCooldownMs. The simulation interval, visible-vehicle limit, glow colors, particle asset/scale, wheel bones, and excluded classes remain plaintext-only.
5. Add Config.PartsDelivery.deliveryMode = "standard" after deliveryTimeSeconds = 60. This path was absent in 1.24.1; "standard" keeps the physical flow and "player_inventory" grants the complete collected delivery directly. With /jobconfig, the saved key is partsDeliveryMode and overrides the file.
6. Replace antilag_kit with ecu_tuning_kit in every Config.Jobs[*].shop, partsDeliveryShop, and tuning required-item row. Change the default pricing category key from antilag to ecu_electronics while keeping 70% supplier share, 25% margin, 1400 labor, complex, minimum 400, and maximum 90000. Saved /jobconfig jobs are migrated on start, but inspect every configured job afterward.
7. Replace the tuning-option defaults with these exact levels, percent costs, and required items; none means no required item:

   Option ID	1.25.0 level configuration
   antilag_enabled	0=0/none, 1=18.6/ecu_tuning_kit, 2=20.93/ecu_tuning_kit, 3=23.26/ecu_tuning_kit, 4=27.91/ecu_tuning_kit
   twostep_enabled	enabled, 16.28/ecu_tuning_kit
   electronic_throttle_response	0=0/none, 1=4.65/ecu_tuning_kit
   electronic_wheelie_tune	0=0/none, 1=9.3/ecu_tuning_kit, 2=13.95/ecu_tuning_kit
   electronic_engine_tune	0=0/none, 1=18.6, 2=34.88, 3=65.12, 4=93.02, each paid level requiring ecu_tuning_kit
   electronic_idle_rpm	0=0/none, 1=4.65, 2=5.58, 3=6.98, 4=8.37, each paid level requiring ecu_tuning_kit
   electronic_interior_light	0=0/none, 1=1.12/ecu_tuning_kit
   electronic_headlight_brightness	0=1.12, 1=1.12, 2=1.12, 3=0/none, 4=1.86, 5=2.79; every non-default paid level requires ecu_tuning_kit
   electronic_radio_power	0=1.12/ecu_tuning_kit, 1=0/none
   electronic_brake_lights	0=0/none, 1=2.79/ecu_tuning_kit, 2=2.79/ecu_tuning_kit
   electronic_highbeams_on_horn	0=0/none, 1=2.33/ecu_tuning_kit
   electronic_automatic_hazards	0=0/none, 1=3.72/ecu_tuning_kit
   electronic_mood_color	0=0/none; levels 1..16=4.65/ecu_tuning_kit
   electronic_mood_intensity	0=0/ecu_tuning_kit, 1=0/none, 2=1.12/ecu_tuning_kit

   
   In config/adv_config.lua, remove the obsolete Config.AntiLag.activationRpm = 0.7 and Config.AntiLag.minGear = 2 paths; anti-lag behavior now comes from the installed level rather than those global gates.
8. Register ecu_tuning_kit in the active inventory with label ECU Tuning Kit, weight 2000, and the supplied PNG. Migrate stored antilag_kit items according to the active provider. For ESX item tables, replace the old insert row with ('ecu_tuning_kit', 'ECU Tuning Kit', 2000, 0, 1); INSERT IGNORE does not rename existing rows automatically.
9. No mechanic table schema changes in this release. Restart Base, Jobs Base, and Mechanic in order, then verify the ECU menu, all option levels, saved tuning, brake heat, both delivery modes, item consumption, invoice completion, Quasar/self-service repair persistence, stance/windows/xenon sync, fake-plate falloff, and post-repair limp-mode recovery.