Open ahcenezdh opened 1 week ago
I think this one is more intuitive and gives you more information about given native: https://vhub.wiki/natives
I used a lot vhub and for me nativedb is way more intuitive, + on nativedb you can search natives based on the gamebuild or the namespace, and the UI from nativedb is way better (at least for me)
There is a theme system, for people doing scripting and staying during hours on the native website, those features can be really cool and everything as said before is open source https://github.com/DottieDot/GTAV-NativeDB
nativedb doesn't have the correct parameters, nor description for given native, vhub does (also a lot of enums, structures, etc), and the data is open source
nativedb doesn't have the correct parameters, nor description for given native, vhub does (also a lot of enums, structures, etc), and the data is open source
Well you can take data from vhub and using it for the nativedb website (just a suggestion here)
nativedb website looks nice, we will look into that. As for "custom" natives, they will very likely be part of yamp API, similarly how alt:V does it.
nativedb website looks nice, we will look into that. As for "custom" natives, they will very likely be part of yamp API, similarly how alt:V does it.
Nice! Will be there to document those natives and contribute
So, it's about the design of GTA5 natives. It would be cool to differentiate GTA5 natives from YAMP natives (the ones added by the platform), as well as having documentation. Instead of just using data from alloc8or, it would be great to do something similar to FiveM and allow the community to contribute to natives.
For example, this native reference is really cool: https://nativedb.dotindustries.dev/gta5/natives. It's fully open source, and we could add examples based on ScRT, etc.