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, shops, delivery catalogs, interactions, prices, wear, vehicle care, 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.
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
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, and job-specific behavior. Ensure every configured job name exists in your framework and uses the intended grades.
Open configuration files
| File | Use |
|---|---|
config/config.lua | Feature toggles, fallback jobs, interactions, theft, delivery, vehicle care, wear, wheel damage, and pricing |
config/adv_config.lua | Database automation, command permissions, instant tuning, performance systems, lift behavior, persistence, and custom handling |
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.