Troubleshooting
On this page
The key does nothing
Check each condition in turn:
- You are in the driver seat.
- You count as police: your job is in
Config.PoliceJobs(or its type inConfig.PoliceJobTypes), or you have thepursuit.useACE. - You are on duty, when
Config.RequireOnDutyis on. - The vehicle is Emergency class or its spawn code is in
Config.Vehicles.Models. - The key wasn't rebound. Check Settings > Key Bindings > FiveM, or use
/pursuit.
Unmarked cars can't switch modes
Most unmarked cars are not Emergency class. Add their spawn codes to Config.Vehicles.Models, or set
Config.Vehicles.EmergencyOnly = false.
It works for some officers and not others on ESX
ESX has no duty flag, so a listed job always counts as on duty. If your server uses offpolice style jobs,
make sure only the on-duty job names are in Config.PoliceJobs.
The mode turns itself off
That is auto off: in a pursuit mode, sitting under Config.AutoOff.BelowMph for Config.AutoOff.Seconds
drops the car back to OFF. Raise the seconds or set Config.AutoOff.Enabled = false.
The car still feels boosted after leaving
The changes are put back when the mode goes off, the officer gets out, or someone else takes the car. If another script changes handling on the same vehicle, it may write its own values after ours. Turn the mode off before that script runs, or leave its handling fields out of the modes.
The PIT assist never fires
Config.Pit.Assistis'off'. Set it to'light'or'full'.- The display didn't say PIT READY at contact. Speed, angle and position all have to be green.
- You were over
Config.Pit.MaxMphor underConfig.Pit.MinMph. - A cooldown was running:
Config.Pit.Cooldownper officer,Config.Pit.TargetCooldownper target. - The server saw the vehicles further apart than
Config.Pit.MaxDistance. Raise it a little on high-latency servers.
The display covers another HUD
Move it with Config.Hud.Position, OffsetX and OffsetY, or shrink it with Config.Hud.Scale. Set
Config.Hud.ShowWhenOff = false to hide it while the mode is off.