Common Errors

Common Errors — Taxi Job | Quasar Store | Quasar Store

"Parking lot is full"

Every bay in Config.VehicleSpawnCoords has a vehicle within a couple of metres of it — usually cabs or cars left behind by other players. Clear them, or add more bays: one driver can start per free bay.

"Your level is too low to drive that cab"

The cab's levelRequired is above the driver's level. The panel shows locked cabs dimmed with the level they need; pick one that is unlocked.

No fare ever comes in

The radio waits between Config.CustomerCalls minTime and maxTime seconds (5 to 20) before each fare. If it never calls, check that Config.Rides.startLocation and finishLocation both hold at least one point — with either empty, shifts are refused.

There is no prompt at the pickup or the drop-off

The prompt only appears with the driver at the wheel of their own cab, the cab fully stopped, and within Config.InteractDistance (12 m) of the point. Pull up closer and come to a full stop. A cab taken from someone else does not count.

"There are no free seats available for the passenger"

Every passenger seat is taken — usually by friends riding along. The fare waits: free a seat and press E again.

"The fare could not be paid in" or "This item does not exist: black_money"

The money could not be credited. On ESX an illegal fare needs the black_money account; on QBCore and Qbox it needs a black_money item in your inventory's item list — stock QBCore only ships markedbills. A full inventory refuses the item too. The experience is still given; the leaderboard earnings are not.

The shift ended on its own

The driver lost the job, disconnected, or the resource was restarted — the server drops a shift it can no longer account for, and the client cleans up the cab, the blips and the meter. Another resource can also end a shift with the cancelShift export.

The cab has no keys, or no fuel

Keys are detected once, when the client loads, so the key script must start before qs-taxijob in server.cfg. Fuel is only filled with Config.Fuel on and Config.FuelExport pointing at a fuel resource that is running.

The police are never alerted on an illegal stop

Config.DispatchExport is empty by default. Fill it in with your dispatch resource's alert — see Integrations → Police Dispatch. It only runs when the stop is actually reported, which at level 1 is one stop in five.

Key	Means
`NOTIFY_NOT_TAXI`	The player has no job listed in Config.TaxiJob — or lost it mid-shift.
`NOTIFY_ALREADY_ON_SHIFT`	A shift is already running for this player.
`NOTIFY_VEHICLE_LOCKED`	The chosen cab needs a higher level.
`PARKING_FULL`	No free bay on the rank, or the cab could not be spawned.
`NOTIFY_NO_FREE_SEATS`	The cab has no free seat for the fare.
`NOTIFY_PAYMENT_FAILED`	The fare could not be credited — a missing account, or a full inventory.
`NOTIFY_ITEM_DOES_NOT_EXIST`	The inventory has no such item — almost always black_money on QBCore.
`NOTIFY_DRIVER_UNAVAILABLE`	The driver of a player fare left, clocked off or lost the job.
`NOTIFY_FARE_NOT_RIDDEN`	A player fare was paid but not driven, so it earned no experience.
`NOTIFY_SHIFT_ABANDONED`	The shift ended — clocked off, or no longer on file on the server after a restart.

Installation and Access#

Common Errors

Installation and Access#

Shifts and Fares#

Player Passengers#

Leaderboards and Rewards#

Messages and What They Mean#