Page cover

πŸ—ΊοΈJob Center Locations

Easily add more job center locations via Config.Locations


  • The key is the location name and must be unique

  • The zone coords must be a vector4 value as this is shared with the ped (if enabled)

  • The zone size must be a vector3 value

  • The jobs you list in the jobs table must exist in your jobs.lua file

  • The licenses you list in the licenses table must exist in your qb-core/config.lua file in the licenses metadata table


  • The key is the location name and must be unqiue

['My Custom Location'] = { -- the key is the location name
    ---
},

  • To enable visual debugging of the zone location set debug to true if the ped for this location is disabled

  • The coords must be vector4

  • The size must be vector3

  • The name is the zone name and must be unique, lowercase and no spaces or anything

  • The radius is the size of the target zone if a ped is disabled at this location


  • If required you can set a ped to spawn (if disabled then a target zone is created instead) by setting ped to true

  • The model is the ped model you want to use (ped models: https://docs.fivem.net/docs/game-references/ped-models/)

  • You can specify a scenario for the ped to use

  • The icon is the target icon

  • The label is the target label

  • The distance is the max target interaction distance


  • If required each location can have its own blip

  • The id is the blip id

  • The colour is the blip colour

  • The scale is the blip scale

  • The title is the blip name (advised to keep these the same name to group them up and prevent map issues)


  • When getting licenses or identity documents a small progress circle is played with an animation and a prop

  • The duration is the duration of the progress circle

  • The label is the label for the progress circle

  • Define animation data in the anim table

  • Define prop data in the prop table


  • You can add jobs where required to each location using the jobs table

  • Ensure the jobs you add are in your jobs.lua file

  • The key is the job name

  • The info is a small description of that job for the menu


  • You can add licenses where required to each location in the licenses table

  • Ensure the licenses you add are in your qb-core/config.lua file in the license metadata table

  • The key is the licenses name

  • The info is a small description of that license

  • The cost is the cost to purchase that license

  • The item is the item name given when purchasing that license ensure this exists in your items.lua and also ensure you have added the relevant data you wish to be added in the following callback lusty94_jobcenter:server:giveLicense

  • Ensure you also add the relevant data you wish to be displayed in the following event lusty94_jobcenter:server:useItem

  • Ensure you also add the respective item name to the useableItems table in server/funcs.lua if adding custom licenses to ensure it is useable


  • You can add identity documents where required for each location in the identity table

  • The key is the item name and must be in your items.lua as it gets the label of it for the menu

  • The info is a small description of that identity document

  • The cost is the cost to purchase that item and can be set to 0 if required

  • The item is the item name received and must be in your items.lua

  • The requiredJob is the job required to purchase that document

  • The rank is the required rank of that job to purchase that document

Last updated