The resource folder is not called qs-lifeguard. The freeze is deliberate. Stop the server, give the folder its name back, update server.cfg to ensure qs-lifeguard and start again.

The stations only appear for players who may work them. In order of likelihood:

• The player's job is not in Config.LifeguardJob while Config.RequireJob is on.

• The framework starts after Lifeguard Job, so none was detected. Move it above ensure qs-lifeguard.

• Config.Target = true without ox_target running: the captains are there but have no option. Start ox_target first, or turn the setting off.

• The player has just switched character — the stations are rebuilt about two seconds later.

The job the player holds is not listed in Config.LifeguardJob. On QBCore and Qbox, also check the job exists in shared/jobs.lua with exactly that name. The same message appears when a call-out is finished by somebody who has changed job since it started — they are not paid for it.

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

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.

The job is written to the database on the first start, but ESX reads its jobs when it starts — restart the server once afterwards. If the console printed Could not register the ESX job rows, your database has no jobs table the job could write to: import qs-Lifeguard.sql by hand.

Two possible reasons. Either the resource has not been restarted since — config files are read at start — or that setting was saved from the settings panel, which wins over the file. Open /lifeguardadmin, find the setting (it is marked as changed from the panel), press the arrow to give it back to the file and restart.

The uniform needs Config.Clothing = true and, on ESX, esx_skin and skinchanger; on QBCore, qb-clothing. With another clothing resource, point ApplyJobClothes and RemoveJobClothes in config/clothing.lua at it, or turn the uniform off. The pieces themselves are the numbers in that same file.

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.

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.

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.

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

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.

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.

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 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.

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.

It needs Config.CoopIncidents.enabled, at least two lifeguards who started their shift at a station, and then a 30% roll on someone's checkpoint arrival — with a 10-minute rest after each one (5 after a failure). The Shared calls page of the settings panel shows how many are on shift, and can start one on the spot to test.

A cooperative rescue pays for the work each lifeguard did: somebody who found no board, delivered no surfer, rescued no passenger or never drove off a shark has nothing to be paid for. A lifeguard who changed job during it is not paid, and a Shark Alert that loses every swimmer pays nobody.

It fills in as solo call-outs are paid — cooperative rescues are not counted on it. It is saved to data/stats.json, so the server needs write access to the resource folder; on hosts that mount resources read-only it cannot be kept.

Levels are kept per character — the ESX identifier, or the citizen id on QBCore and Qbox — so a different character starts from 1. Their row is in qs_lifeguard.

It follows Config.PlayerNameSource — the character's name, the FiveM name, or both. A name is stored when a call-out is paid, so a change shows after that player's next one.

The resource folder is not called qs-lifeguard. The freeze is deliberate. Stop the server, give the folder its name back, update server.cfg to ensure qs-lifeguard and start again.

The stations only appear for players who may work them. In order of likelihood:

• The player's job is not in Config.LifeguardJob while Config.RequireJob is on.

• The framework starts after Lifeguard Job, so none was detected. Move it above ensure qs-lifeguard.

• Config.Target = true without ox_target running: the captains are there but have no option. Start ox_target first, or turn the setting off.

• The player has just switched character — the stations are rebuilt about two seconds later.

The job the player holds is not listed in Config.LifeguardJob. On QBCore and Qbox, also check the job exists in shared/jobs.lua with exactly that name. The same message appears when a call-out is finished by somebody who has changed job since it started — they are not paid for it.

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

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.

The job is written to the database on the first start, but ESX reads its jobs when it starts — restart the server once afterwards. If the console printed Could not register the ESX job rows, your database has no jobs table the job could write to: import qs-Lifeguard.sql by hand.

Two possible reasons. Either the resource has not been restarted since — config files are read at start — or that setting was saved from the settings panel, which wins over the file. Open /lifeguardadmin, find the setting (it is marked as changed from the panel), press the arrow to give it back to the file and restart.

The uniform needs Config.Clothing = true and, on ESX, esx_skin and skinchanger; on QBCore, qb-clothing. With another clothing resource, point ApplyJobClothes and RemoveJobClothes in config/clothing.lua at it, or turn the uniform off. The pieces themselves are the numbers in that same file.

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.

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.

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.

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

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.

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.

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 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.

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.

It needs Config.CoopIncidents.enabled, at least two lifeguards who started their shift at a station, and then a 30% roll on someone's checkpoint arrival — with a 10-minute rest after each one (5 after a failure). The Shared calls page of the settings panel shows how many are on shift, and can start one on the spot to test.

A cooperative rescue pays for the work each lifeguard did: somebody who found no board, delivered no surfer, rescued no passenger or never drove off a shark has nothing to be paid for. A lifeguard who changed job during it is not paid, and a Shark Alert that loses every swimmer pays nobody.

It fills in as solo call-outs are paid — cooperative rescues are not counted on it. It is saved to data/stats.json, so the server needs write access to the resource folder; on hosts that mount resources read-only it cannot be kept.

Levels are kept per character — the ESX identifier, or the citizen id on QBCore and Qbox — so a different character starts from 1. Their row is in qs_lifeguard.

It follows Config.PlayerNameSource — the character's name, the FiveM name, or both. A name is stored when a call-out is paid, so a change shows after that player's next one.