With a key that has jobs.read, Blixye is the source of truth for jobs. The framework applies what Blixye says, and whatever in the game wants to change a job (the boss menu, /setjob, the panel or an ESX or QBCore script's setJob) does not apply it: it asks Blixye, which decides with the same permissions as the MDT. That way, a badly protected setJob in a third-party script cannot make anyone a police officer.
With a key that has jobs.read, Blixye is the source of truth for jobs. The framework applies what Blixye says, and whatever in the game wants to change a job (the boss menu, /setjob, the panel or an ESX or QBCore script's setJob) does not apply it: it asks Blixye, which decides with the same permissions as the MDT. That way, a badly protected setJob in a third-party script cannot make anyone a police officer.
NOTE
With a key that has jobs.read, Blixye is the source of truth for jobs. The framework applies what Blixye says, and whatever in the game wants to change a job (the boss menu, /setjob, the panel or an ESX or QBCore script's setJob) does not apply it: it asks Blixye, which decides with the same permissions as the MDT. That way, a badly protected setJob in a third-party script cannot make anyone a police officer.
Linking corporations and jobs
Linking corporations and jobs
NOTE
Linking corporations and jobs
NOTE
It is done on the same card as the key: Admin panel → Integraciones → «Servidor de juego (FiveM)».
Each corporation is linked to a job name exactly as it appears in blixye_config/trabajos.lua (police, ambulance…). A job can only belong to one corporation, and the admin corporation cannot be a job.
Each rank is linked to a grade (0 to 9999), which is the rank's level in the framework. Within a corporation, each grade belongs to a single rank.
A corporation can be managed (a boss signs hires) or open. In an open one, ranks marked as assignable without a boss accept unsigned hires, if the key has jobs.free.
How it stays in sync
How it stays in sync
NOTE
How it stays in sync
NOTE
On start, the resource asks Blixye what its key can do; with jobs.read it registers with the core as the job authority.
Every 5 seconds it asks for the changes since the last one it saw and rereads the connected players they affect.
Every 15 minutes it rereads everyone connected, in case someone wrote to Blixye's database outside the log (that leaves no event).
If Blixye signals that everything must be reread (a server backup was restored, or which corporation is which job changed), it rereads everything.
Each request waits 10 seconds at most: if Blixye does not answer, the game carries on and tries again on the next round.
Which job gets applied
Which job gets applied
NOTE
Which job gets applied
Out of the character's active jobs in Blixye whose job and grade exist in the framework, the most recently changed one (on a tie, the higher rank). If there is none, they end up as unemployed, grade 0.
Out of the character's active jobs in Blixye whose job and grade exist in the framework, the most recently changed one (on a tie, the higher rank). If there is none, they end up as unemployed, grade 0.
NOTE
Out of the character's active jobs in Blixye whose job and grade exist in the framework, the most recently changed one (on a tie, the higher rank). If there is none, they end up as unemployed, grade 0.
Changing a job from the game
Changing a job from the game
NOTE
Changing a job from the game
NOTE
Both the person asking and the person whose job changes must have picked their Blixye character in the phone: the change is signed by the requester's character.
Blixye applies the MDT's permissions: the requester must be an active member of that corporation with permission to manage personnel, act below their own rank and within their subdivision. Whoever manages MDT personnel on the server can do everything.
The answer shows up as an in-game notification: «Hecho: Blixye lo ha aprobado» or the reason why not.
Changes made in the MDT reach the game on their own. The detail of each call is in Game API (FiveM).
Changes made in the MDT reach the game on their own. The detail of each call is in Game API (FiveM).
NOTE
Changes made in the MDT reach the game on their own. The detail of each call is in Game API (FiveM).