Separate the resource bundle from the workshop map
The publisher’s installation guide names jg-mechanic, jg-mechanic-props, jg-vehiclemileage and its default jg-textui resource. The text UI can be replaced through the documented configuration. It also directs you to inventory-specific item setup and the core config files.
A workshop MLO supplies the environment, while the mechanic resource supplies its documented gameplay. Keep map coordinates, job access, inventory, vehicle integration and resource versions in one staging record. This is an independent documentation guide, not a resource download or a performance benchmark.
When updating, the publisher warns against mixing old and new resource files. Begin with the complete new package and carefully reapply your configuration values. Keep backups and rehearse on staging before changing the live workshop.
Choose one employee-management system
The Job Setup page distinguishes Config.UseFrameworkJobs = false for built-in employee management from true for framework jobs. Only owned mechanic locations link to jobs. With framework jobs enabled, hiring and grades belong to the framework-compatible boss menu, and the tablet does not show its built-in employee controls.
The publisher also distinguishes active framework jobs from all memberships stored in a multijob resource. A player may need to switch to the configured mechanic job before logging into the tablet. Do not diagnose a missing Management app without first checking which job system was intentionally selected.
For framework jobs, the selected banking integration owns the society account. The documentation says JG Mechanic does not create third-party banking accounts. Set up and test the account for each unique mechanic job before accepting work orders.
Standard modifications, custom tuning and shop items use different price settings
The pricing documentation separates standard modifications and repairs in each location’s mods table, custom tuning in Config.Tuning, shop items in each shop’s items table, and employee commission in the owned location’s commission setting. Changing one value does not establish that every shop or tuning item now uses the intended price.
It describes fixed, percentage and combined base-pricing modes. Percentage pricing depends on the vehicle value used by the resource. Check that value for a custom model before concluding that an unexpectedly high upgrade price comes from the menu itself.
| Illustrative input | Calculation | Base result |
|---|---|---|
| Vehicle value 80,000; rate 1.5% | 80,000 × 0.015 | 1,200 |
| Fixed base 300 only | 300 | 300 |
| Combined example | 1,200 + 300 | 1,500 |
Trace a single work order from selection to saved vehicle state
Use one known vehicle and one modest change on staging. Record the displayed price before payment, the customer’s balance, the intended society destination and any employee commission. Complete the order, inspect the vehicle result, then compare the recorded balances and saved state.
Return the vehicle through your normal garage workflow and retrieve it again. Verify that the intended change remains. A visual change during the installation animation is narrower evidence than persistence after storage and reconnect. Keep the vehicle identifier and resource versions with the result.
Repeat with an ordinary employee, a manager and a player who should not have access. Validate sensitive requests on the server against the actual role and state. Client-side tablet visibility alone is not authorization for a transaction or vehicle modification.
Check mileage and integration changes together
The current installation guide says to update jg-mechanic and jg-vehiclemileage together and start the mileage resource first. It also discusses strict statebag mode and warns that other resources must support it. Treat this as a server-wide compatibility decision, not an isolated fix to paste into production.
Rehearse the exact configuration with your garage and vehicle resources. Check servicing, driving and mileage updates, then resource restarts and garage retrieval. Magnate has not performed these game-runtime tests; the sequence is a proposed acceptance plan for your setup.
Use the specific error to choose the next check
The publisher’s troubleshooting page separately covers an audio-bank timeout, respray particle loading and SQL startup failures. For the documented audio-bank issue it provides Config.DisableSound = true; that changes the feature behavior and is not a general cure for every startup error.
Keep database repair scoped to the shipped instructions and a backed-up staging copy. Do not remove SQL clauses or rerun a schema file solely because an unrelated guide suggests it. Capture the exact error, target database, resource release and current schema before planning a repair.
For missing management controls, return to the chosen job system. For wrong prices, identify the affected price category and vehicle value. For changes lost after storage, isolate the garage and persistence path. This makes the report reproducible without replacing several integrations at once.
Questions, answered.
Why is the JG Mechanic Management app missing?
The publisher says framework-job mode uses an external boss-menu workflow instead of the built-in employee controls. Check Config.UseFrameworkJobs and the intended job setup.
Does JG Mechanic create my framework society accounts?
The reviewed job documentation says third-party society accounts must be created separately for each unique mechanic job.
Does the example table calculate a complete upgrade invoice?
No. It illustrates base-price arithmetic only. Check the actual category, tuning options, modifiers and displayed work-order total in your installed release.
Sources & editorial notes
Source review: November 7, 2026. Platform announcements can change. This guide separates published facts from Magnate’s original analysis and preparation advice.
- JG Scripts — Mechanic installation Publisher bundle, update and mileage integration guidance.
- JG Scripts — Mechanic job setup Built-in/framework job choices and society banking responsibilities.
- JG Scripts — Mechanic pricing Separate pricing fields and base-pricing modes.
- JG Scripts — Mechanic troubleshooting Documented audio, particle and startup issue categories.
- Cfx — Secure your events Server-side validation of client-triggered actions.
Published by an independent editorial brand. Read our editorial standards.
