#SetJob/Job not updating
1 messages · Page 1 of 1 (latest)
the lastes version i see on github
i even just removed it and update it again
when i do setjob 1 ppolice 4 or any job at that it doent update the hud
but when i do /job it shows that i have the job
so when i go to interact with the job it like it saying i dont have the job
might sound confusing
but when i go back to a older version it works fine
i think has to do with how the player data is now being update
Did you just update the core?
yes
Well there's the issue, you can't update qb-core the other scripts need updating aswell
i switch out most of the jobs
i use wasabi ambulance when i set the job in the update core, i cant 3rd the ped no more, it does nothing
revert back to the previous verson it work
i use codem hudv2 now when i set job it doent update
Well you just answered your own question, when you updated the core it messed it up as you didn't update the other resources, which is why it starts to work when you revert to a previous version
Again, you ant just update the core
i updated qb mananment , snall resource etc, all i removed was the job and replace the jobs
so i would assume once the main funtions are update it should still work
It should
right so thats updated but it just not working for me, i dont know why
i set my job to police and my mdt saying i dont have the auth to use this
i install this over 3 time since lastnight
Right your going into multiple issues here
So the hud and ambulance might not be updated to the latest qbcore functions.
Secondly, what MDT are you using?
what i notice if i set the job and restart the server it register the job and work
i just tried to set my job and qb manangment banned me
Right, locking this is you dont appear to want the help.
Im asking questions to determine whats happening and you keep posting comments irrelevant to what I ask.
You have failed to follow the structure of a support thread, found here.
All fields must be filled out, with effort, should you wish others to put effort into helping you.
This post has now been locked. Please reopen another, properly.