Browse docs
Configuration
Configuration sources
Sky Mechanic Job uses two configuration layers:
| Layer | Purpose |
|---|---|
/jobconfig | Job-specific and frequently changed settings stored through Sky Jobs Base |
Open files in sky_mechanicjob/config | Defaults, fallback job data, advanced systems, hooks, locales, and inventory assets |
When Config.UseJobConfigurator is enabled, saved Job Configurator values take priority over matching fallback values in config.lua. Editing a fallback value alone may therefore have no visible effect on an already configured server.
Recommended workflow
- Enable or disable the main systems in
/jobconfig. - Configure mechanic jobs, vehicle-class access, shops, delivery catalogs, interactions, prices, wear, vehicle care, fluid leaks, and carry items.
- Save the configuration and test it without restarting the resource.
- Use the open configuration files only for settings that are not exposed in the configurator.
- Keep a backup of customized configuration files before every resource update.
The Tuning Prices editor supports complete option switches, individual stage switches, and allowed or blocked value lists. Paint presets can configure Standard and Chameleon ranges without manually editing JSON.
Main feature toggles
Config.ToggleFeatures controls the major systems. Available toggles include:
- Tuning and instant tuning
- Parts delivery and physical carry items
- Nitro, anti-lag, and two-step
- Realistic wheel damage
- Custom handling
- Mileage HUD
- Workshop lifts
- Vehicle fluid leaks and frontal-impact detection
Disabling a feature does not remove its old database data. This allows a feature to be enabled again without losing saved vehicle records.
Job definitions
Each mechanic job can define its color, optional off-duty job, mechanic shop catalog, parts delivery catalog, tuning profile, allowed vehicle classes, and job-specific behavior. Ensure every configured job name exists in your framework and uses the intended grades.
allowedVehicleClasses restricts tuning, removal, diagnostic repairs, and order installation to the selected GTA classes. An empty selection allows every class. The server validates the class from the actual networked vehicle rather than trusting a client-supplied value.
The Order item source setting controls where tuning-order install parts are taken from:
| Source | Behavior |
|---|---|
Player inventory | Keeps the classic flow. The installing mechanic must carry the required item. |
Storage | Counts matching items across the workshop's job storage and removes them from storage when the install succeeds. |
Use Storage only for jobs whose workshop storage is configured and stocked with the same item names used by tuning options, diagnostics, vehicle care, and engine-sound installs.
Billing settings
Mechanic billing prices are managed in the Billing section of /jobconfig and in the Bossmenu billing price management flow. Default mechanic billing rows are protected so they cannot be accidentally removed, while custom rows can be created for server-specific invoice positions.
Custom billing positions created by bosses appear in the mechanic tablet Billing app. If custom prices are enabled, authorized users can adjust the price before adding the position to an invoice. Saved labels require the matching sky_jobs_base billing-spec migration.
Open configuration files
| File | Use |
|---|---|
config/config.lua | Feature toggles, fallback jobs, interactions, theft, delivery, vehicle care, wear, fluid leaks, wheel damage, and pricing |
config/adv_config.lua | Database automation, command permissions, instant tuning, performance systems, vehicle pushing, lift behavior, persistence, and custom handling |
config/engine_sounds_config.lua | Built-in and custom Engine Sound tuning entries |
config/sv_functions.lua | Supported server-side integration hooks such as vehicle price lookup and theft dispatch |
config/locales/*.lua | Translations and interface text |
config/inventory | Included mechanic item images |
Settings that need extra care
Vehicle persistence
The ownership requirement prevents saved tuning and stance data from being applied to unrelated world, job, NPC, or administrator-spawned vehicles that reuse an existing plate. Disable it only when you intentionally want tuning persistence on vehicles outside the framework ownership table.
Vehicle pricing
Percentage-based tuning prices depend on a valid vehicle purchase price. Review the supported price lookup hook when your vehicle catalog is stored in a custom resource or database table.
Custom handling
Only enable handling overwrite behavior when another resource resets vehicle handling on entry. Enabling it unnecessarily can repeatedly multiply handling changes.
Electric vehicles
Servers below game build 3258 should maintain the electric vehicle fallback model list so EV-specific diagnostics and wear behave correctly.
Job Configurator mechanic jobs
Mechanic jobs created only through /jobconfig are included when Mechanic tablet apps are registered. They receive the same Vehicles, Orders, Parts Shop, Diagnostics, and Dyno apps as mechanic jobs defined in config.lua.
After adding or changing a mechanic job, save the Job Configurator entry and ensure the player has the correct job and duty state before checking the tablet.
Custom Engine Sounds
Custom Engine Sound entries are configured in config/engine_sounds_config.lua, while their audio files must be loaded by Mechanic Job or a separate ensured sound resource. See Custom Engine Sounds for the complete setup.
External Nitro HUD
Set Config.Nitro.hud.enabled = false in config/adv_config.lua to hide only the built-in Nitro display. External resources can continue reading Nitro state and consumption through the supported client exports and live event.
Config.Nitro.externalUpdateIntervalMs controls how often the external HUD state event is emitted while Nitro data is active. Keep the value responsive enough for your HUD without making it faster than your NUI needs. See External Nitro HUD for the complete setup.
Vehicle Fluid Leaks
The global Vehicle Fluid Leaks Job Configurator section controls wear thresholds, probabilities, trail spacing, and frontal-impact detection. The provider connection remains in the open Config.OilLeaks.integration table so another spill system can be connected without changing Mechanic Job source files.
See Vehicle Fluid Leaks for every setting and the provider payload.