Vehicle wear

Per-plate tracking, server calculation, effects on driving and maintenance.

#Principle

Wear is tracked per plate for registered vehicles. Tracked components: oil, engine, tyres (per wheel), brakes, suspension, battery, spark plugs.

#How it is calculated

The calculation is done by the server, from:

the distance actually travelled (teleports are ignored);
the vehicle category;
the driving style: harsh braking, off-road, red zone, burnouts (bounded counters).

Server sampling every 5 s; grouped saves every 90 s.

#Effects on driving

Below the start threshold, effects are progressive:

power loss;
grip;
braking;
suspension;
responsiveness.

Random events can occur: stalling, puncture, starting failure, misfires.

#Where to see it

Wear is visible in the diagnostic and the history. Maintenance is done in steps (pick the part, fit it) like any other repair.

#Settings

In /mecagestion, Wear & effects tab: wear speeds, driving style, thresholds, effect intensity.

Tracked vehicle types are set in config.lua:

Lua

Config.WearVehicleTypes = { automobile = true, bike = true, quadbike = true, amphibious_automobile = true }

#Data

Table tc_mech_vehicles: mileage, wear, options outside props (finishes, special tyres). The tc_wear, tc_extras and tc_order statebags are written by the server only (read-only on the client).