This allows server owners to become ESX admins on their first joins, based on if they have the `command` ace permission or not.
If they do have that ace, they can `setgroup <id> admin`, so access-wise that's ok.
I would commit this to master, but since v2 is not yet ready, PlumeESX uses "v1-final".
Automaticly stop resources that
- a) not compatible with ESX, for example spawnmanager
- b) does the same as esx does, but what esx probably does better
- Only save weapon components if needed, wont save default clip anymore, and if no other component is available then its not saved at all
- Tint index not stored if not above 0
- Weapon label not saved in database since its useless
- Validate weapon on player load
- Implemented two new xPlayer functions:
- .getWeaponTint(weaponName)
- .setWeaponTint(weaponName, weaponTintIndex)
Thanks to @profex1999 for co authoring this!
Co-Authored-By: Andrea Passarini <profex1999@users.noreply.github.com>
- Removed xPlayer .displayBank()
- Fixed issues with giving weapon using commands
- Modified ESX.UI.ShowInventoryItemNotification() to take string instead of table
- Minor adjustments and variable renames
- Fixed lower case weapons not droppable
- Removed /disconnect command becasue fivem implemented their own
This commit implements a new way of saving and getting player coords.
Player coords are synced with its assigned xPlayer, the syncing interval is defined in the configuration file.
Also coords wont sync if the player is too close to their previous location.
Existing servers must change their database to account for the new length of the position varchar, at 53 chars max. There's also a column default value specified in the sql file.
New xPlayer functions:
- .getCoords()
- .setCoords() (x,y,z,heading (optional) table
- .updateCoords()
The last one is used for syncing coords from client (interval). The second one will teleport the player. First one is a renamed .getLastPosition()
Linden