Troubleshooting
Frequent tc-mechanic errors: server not responding, billing blocked, vehicle not found…
Always start with /mecadiag (staff or console): it shows the detected framework, billing mode, account, points and tracked vehicles.
#“Server is not responding” when opening the tablet or configurator
- Check that the framework starts before
tc-mechanic(detection at load time) and thattc-uiandox_libare running. - Set
Config.Bridge.Debug = true, restart the script and read the console: the framework should be printed. - If detection is wrong, force it:
Config.Bridge.Framework = 'esx'(or'qbcore','qbox','vision').
#Billing is blocked
The message states the cause; /mecadiag details it.
| Cause | Fix |
|---|---|
| No usable society account | Set Config.Bridge.Society, or use the internal cash box (internal) |
No invoice system in invoice mode | Provide Config.Bridge.Standalone.createInvoice, or switch to builtin |
| Amount refused in cash | It exceeds Config.CashLimit: pay by bank |
#“Vehicle not found” / cannot order
- The vehicle must be owned: it must exist in the table defined in
Config.Vehicles. - Check the table and column names on your ESX / QBCore / Qbox database (
plate,owner/citizenid,vehicle/mods…). - The player must be the owner (or co-owner on Vision), depending on the vehicle ownership setting in the General tab.
#I am not recognised as a mechanic
- Your job must be listed in
Config.MechanicJobs, or have a type equal toConfig.JobType. - The mandatory duty setting (General tab) requires being on duty.
- Check the minimum grade of the action in the Permissions tab.
#/mecagestion refused
- Outside Vision: ACE
command, admin group orConfig.Bridge.Admins(see General installation). - Vision:
gestion_mecanopermission.
#No point appears / no prompt at the workshop
- Create the points in
/mecagestion→ Points and check they are enabled. - Without
ox_target/qb-target, the prompt is a marker + E key (Config.Bridge.InteractKey). - Check
Config.Distances.Point.
#Duplicates with another customisation system
Disable the old system's “Custom” points (Vision core, ESX/QB scripts) in the workshops, then keep only the tc-mechanic points.
#Wear has no effect
- It only applies to registered vehicles and the types in
Config.WearVehicleTypes. - Effects start below the threshold set in the Wear & effects tab.
#Points to validate after installation
- The billing mode actually detected (
/mecadiag) and the society account used. - Your vehicles' table / column names (
Config.Vehicles). - Your mechanic job names (
Config.MechanicJobs).