> For the complete documentation index, see [llms.txt](https://pixelcraft-development.gitbook.io/pixelcraft-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pixelcraft-development.gitbook.io/pixelcraft-docs/assets-and-guides/pc-mechanic.md).

# PC-Mechanic

{% hint style="info" %}
Full-stack mechanic resource for FiveM. Vehicle servicing, damage-driven part wear, inspection minigames, tuning with custom handling data, dyno testing, mod menu, nitrous, role-based shop management, and a tablet workflow for on-duty mechanics.
{% endhint %}

## Description

PC-Mechanic is a complete vehicle workshop system for QBCore, Qbox, and ESX servers. It pairs a player-facing customization UI (mods, paint, wheels, stance) with a deep maintenance layer where parts wear over time and damage, vehicles fail when neglected, and mechanics fix them through inspection and replacement workflows.

The resource ships with self-service shops (Benny's-style walk-up tuning), owned shops (mechanic-managed with employee tablets, repair zones, parts shops, and dyno stations), a mileage HUD, an oil-leak system with engine-seizure consequences, electric-vehicle support, and 13 locales.

## Features

* **Customization** — body kits, wheels, livery, paint (Metallic, Matte, Util, Worn, Misc, Chameleon), neon lights, headlights, tyre smoke, bulletproof tyres, plate index, window tint, horn, extras
* **Stance** — adjustable suspension height, camber, and track width within configurable clamps
* **Tuning** — engines, drivetrains (AWD/RWD/FWD), tyres (slick/semi-slick/offroad), brakes, drift kits, anti-roll bars, launch control, with custom handling data per option
* **Mileage HUD** — km or miles, configurable display position and scale, accumulation multiplier, auto-purge for non-owned cars
* **Servicing** — suspension, tyres, brake pads, engine oil, clutch, air filter, spark plugs, EV motor, EV battery, EV coolant, each with its own item, durability, and degradation
* **Damage-driven wear** — parts degrade from body damage, engine damage, tyre bursts, and rollovers, scaled by hit severity
* **Engine consequences** — oil leaks on damage, low-oil engine shutdowns, complete engine seizure at 0% oil
* **Inspection minigames** — OBD diagnostics, tread test, pressure test, multimeter, dyno inspection, with item-gated tools and per-tool variants and difficulty
* **Electric vehicles** — auto-detected on game build 3258+, manual list for older builds, EV-only parts and tuning
* **Dyno** — alignment overlay, DUI screen, per-plate test history
* **Nitrous** — bottle inventory, partial refills, purging drain, configurable boost duration and cooldown
* **Mod menu** — performance, cosmetics, stance, respray, wheels, neon, headlights, tyre smoke, bulletproof tyres, extras
* **Shops** — self-service or owned, with per-shop mod/tuning toggles, repair zones, walk-up parts shops, stashes, dyno stations
* **Roles** — owner / manager / mechanic / novice with granular permissions, framework-grade mapping, server admin override
* **Repair zones** — polygon enforcement with auto-snap, ceiling detection, in-MLO support, and visual flash on violation
* **Tablet** — on-duty workflow for orders, invoices, analytics, and management
* **Pricing engine** — vehicle-value scaled, profit-margin or buffer modes, lowest/highest shop price selection
* **Discord webhooks** — work orders, servicing, billing, staff management
* **13 locales** — en, ar, cn, de, es, fr, hu, it, ja, pt, sv, zh-tw

## Guides

* [Installation](/pixelcraft-docs/assets-and-guides/pc-mechanic/installation.md)
* [Mechanic Guide](/pixelcraft-docs/assets-and-guides/pc-mechanic/guide.md)
* [Configuration](/pixelcraft-docs/assets-and-guides/pc-mechanic/configuration.md)
* [Events](/pixelcraft-docs/assets-and-guides/pc-mechanic/events.md)
* [Exports](/pixelcraft-docs/assets-and-guides/pc-mechanic/exports.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://pixelcraft-development.gitbook.io/pixelcraft-docs/assets-and-guides/pc-mechanic.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.