Common Errors

Common Errors — Lifeguard Job | Quasar Store | Quasar Store

"You are not allowed to do that" on /lifeguardadmin

The player lacks the ACE command.lifeguard. Grant it to their group and make sure they are in that group:

bash

add_ace group.admin command.lifeguard allow
add_principal identifier.fivem:1234567 group.admin

Also check that Config.AdminPanel.Enabled is not false, and that the ACE there was not renamed.

Checkpoints never raise a call-out

Some checkpoints are meant to be quiet — at level 1 only 40% raise anything. If none ever do:

On the water at low levels there is little to find: every simple call-out happens on the sand.
The shift must have been started from a station. A player who simply drives to the checkpoints is not on duty.
Arriving at the same stretch of beach again within a minute does not count — ride on to the next checkpoint.
After a call-out ran out of time or was abandoned, the next one can take up to a minute to turn up.
Solo call-outs pause while a cooperative rescue is running.

"Incident abandoned."

The call-out ran out of time. Each one has its own limit — the timeout field in config/incidents.lua, in seconds — which you can raise from the settings panel's Call-outs page.

A call-out was finished but nothing was paid

The server pays only when every one of these is true:

the player still holds the lifeguard job;
it was finished within its time limit;
the player is still on or around the beach;
it was a call-out the server issued to that player — one that was not abandoned or already paid.

If you moved stations or routes far from the beach, keep them together: pay is only given within a few hundred metres of the configured checkpoints and stations.

"Cannot change vehicle during an active incident."

Vehicles cannot be swapped or stored while a call-out is open. Finish it first, or use End Shift, which abandons it.

"You have not unlocked this vehicle yet."

The vehicle's minLevel is above the player's level. Jetskis start at level 2 by default, so a brand-new lifeguard has only the land patrol.

"You must be on a vehicle to rescue them."

The Exhausted Swimmer, and the surfers of the Missing Surfer rescue, climb on behind you — ride up on your jetski before using the option. The passengers of the Sinking Vessel are the opposite: you rescue them in the water, off the jetski.

The vehicle does not appear

Look in F8 for could not load vehicle model: the spawn name in Config.VehicleTypes is wrong, or an addon vehicle is not streamed. For a land vehicle, also check the station's land spawn point is clear ground a few metres from the captain.

The lifeguard gets no keys

The lock script was not detected: it starts after Lifeguard Job, or it is not one of the eleven supported. Move it up in server.cfg, or add a bridge as shown in Integrations.

I added a call-out to the config and it never happens

Each call-out id is played by a scene built into the job, so a new id has nothing to play. Tune, move or switch off the sixteen that ship instead — see Call-out IDs.

What you see	Why, and what to do
"You are not allowed to do that"	The player lacks the panel's ACE. It is checked on every button, not only when the panel opens.
A value will not save	It is not the same kind as the file's — text where a number belongs, or a list reshaped into something else — or it is not one of the answers the setting accepts. Match the kind of value the file has there.
Nothing will save at all	The database refused the write. The server console prints `could not save` with the reason.
The framework or lock script is not offered	Both are detected at every start and cannot be saved. Change the load order instead.
Start does nothing on Shared calls	Shared calls are switched off, fewer lifeguards are on shift than one needs (the counter on the page says how many), or one is already running.
Saved, but the game still runs the old value	Expected: saved settings wait for `restart qs-lifeguard`, and the panel shows a banner until then.
Console: saved setting(s) no longer fit this config	After an update, a setting saved earlier no longer matches the new config file and is ignored. It is kept in the database; revert it from the panel to clear it.

Common Errors

Installation and Access#

Patrols and Call-outs#

Cooperative Rescues#

Statistics and Levels#

When the Settings Panel Refuses a Change#