Added an in house skill system, nests skills tables inside player metadata. This is convenient for us as data tied to player - no save logic/load logic required on our end. Tested in qbx/esx no issues. Given slapping *large* tables in this would be bad but this is tiny and useful.
This will return the players money by type, I recommend not using this as its the client and not secure or to be trusted.
Use case is for a ui or a menu I guess?
the getinventory export returns a table of nested values, inside there is a inventory table. This gets us by on the compatibility. It appears that many of the exports have changed, I have tested this on the latest version with a resource that makes use of these items. Also they use amount, I "think" they used to use count but im 100% they use metadata & info tables.
Touched up incorrect or missing Intellisense parameter annotations across several functions. Added some missing descriptions to improve editor support. Still more to do, but this is a small step forward for overall developer workflow. Also small fix in picklexp
Added cleaned up and improved functionality for placeable object.
Example is in unit tests.
Cleanup whitespace and removed accessibility as not used/not documented and doesnt appear to be useful with our current work flow
This is very wip, also a good bit of inventories dont support it at all. I have tested this in ox_inventory but not the others. uploading into repo as it does not break anything and may encourage collab
Targets updated to have boxzone
Entities dont require a model and are effectively points with on spawn on despawn
onplayerloaded and onplayeriunloaded now pass source