* Update README.md
* Update README.md
* feat (locale/tr): Added turkish locale.
Türkçe Karakter Yer Almakta
* feat (locale/es): Added spanish.
* updated spanish
Sounded weird
* Update es.lua
* feat (locale/lv): Added latvian.
I'm personally a native speaker and I can approve this is correct.
* feat(qb-core/player): Added server-side event onJobUpdate (#516)
Added server-side event onJobUpdate so scripts can listen on server if any player changed their job. It's safer than redirecting client event to server again.
* feat (server/player): Added Job update on duty update (#519)
* Trigger Job Update on Duty Update
* Add server event
Co-authored-by: Kakarot <57848836+GhzGarage@users.noreply.github.com>
Co-authored-by: Muhammed Developer <56224780+muhammed10100@users.noreply.github.com>
Co-authored-by: MonkeyWhisper <82112471+MonkeyWhisper@users.noreply.github.com>
Co-authored-by: Casper <71441748+JajarGaming@users.noreply.github.com>
Co-authored-by: Chaini <28576404+chainiDV@users.noreply.github.com>
Co-authored-by: Brady F <bmf1418@gmail.com>
This issues fixes the possible exploit when removing an item when sending the item slot parameter before you were able to send any amount of an item and it would return as if the remove item worked just fine returning true
When you add a new job, existing players cannot get jobrep for it because the original jobrep metadata is always loaded instead. With this method, existing players can get jobrep for new jobs.
This checks to make sure that jobrep metadata isn't nil so that new players do not get stuck in an infinite loop, and instead creates new jobrep metadata for them.
There may be a better way to do this, but this works.
It causes the index count to be skewed, and in turn causes an error in the thread and it never runs again until restart. Using the pairs alleviated this in a test environment.