Sam 298 Posted November 14, 2019 Posted November 14, 2019 Our new NativeDB is now live and available for all to use. This is a project that we've been working on keenly since the game was launched, as we thought that having a proper and fully relational database for native functions would be a massive help for everyone. The NativeDB can be freely edited by registered members, and we hope that everyone finds the enhanced functionality to be useful: Search natives by return type, name or hash. Filter search results by game version and whether or not the native has any comments. WYSIWYG editor for native descriptions, including attachments/images support. Basic code editor to provide code examples for any native. Add descriptions for every native function parameter. Fully featured comment threads on all native pages. Ability to report natives/parameters/comments to website moderators. Revision history for all natives and parameters - can be restored by moderators. If there's any issues, feedback or suggestions that you have for the NativeDB, please let us know in this topic. 1 Quote
Sam 298 Posted November 26, 2019 Author Posted November 26, 2019 November 26: The NativeDB has been updated with a bunch of new namespaces and names. 1 Quote
HughJanus 244 Posted January 9, 2020 Posted January 9, 2020 Can I ask how the process of finding those native functions (names) works? Quote
LMS 674 Posted January 9, 2020 Posted January 9, 2020 Trying to put it simple: Back in the days of GTA IV all names for native functions were included in in the game's exe file. Over the years and games this has changed quite a bit, with GTA V on console using hashed names instead of the "real" name. Since the hashing scheme on that version was known (it is the very common RAGE hashing scheme jenkins) it was possible to brute force a lot of the names. With GTA V on PC things changed again and R* went for a 64bit hashing scheme now for which the algorithm remains unknown. Furthermore hashes are most likely salted as they have changed between versions to make our lives a bit harder (the official reason being anti cheating more or less but everyone that has joined a public lobby in V knows how well this works). At this point for any new native, it was impossible to verify its original name, so people started guessing/estimating it based on the observed behavior and what other natives in the same code region were doing. These guessed names are often prefaced with a _. We don't know what exactly they do and what their name is, but usually the guesses are quite good. To document them you can try passing some values to them, decompile them, debug them, look at the game scripts etc. whatever works best for you 1 Quote
HughJanus 244 Posted January 10, 2020 Posted January 10, 2020 (edited) [this comment didnt make sense, so I removed it] Edited January 22, 2020 by HughJanus removed superfluous comment Quote
Cyan 35 Posted February 17, 2020 Posted February 17, 2020 17th February: We've updated the native DB again with new natives that were added in a previous game release, as well as sync some natives that weren't named locally with datasets elsewhere. 3 Quote
Cyan 35 Posted April 28, 2020 Posted April 28, 2020 Something that's been missing with the site is the ability to see what's changed, which is especially important with the community Wikis. We've now added a new 'Recent Changes' button to see all the new recent changes in all of the Wiki. Edits will also now be visible on your profiles, and the All Activity feed. 1 Quote
HughJanus 244 Posted April 30, 2020 Posted April 30, 2020 It seems some information from earlier is still missing (e.g. in the native PLAY_PAIN there was a description with the painIDs which is missing). Is there any way to fix that or did you overwrite earlier comments and descriptions while updating? Quote
Cyan 35 Posted April 30, 2020 Posted April 30, 2020 1 hour ago, HughJanus said: It seems some information from earlier is still missing (e.g. in the native PLAY_PAIN there was a description with the painIDs which is missing). Is there any way to fix that or did you overwrite earlier comments and descriptions while updating? Our update should have only touched natives where nothing had been changed. I will take a look into it. Quote
HughJanus 244 Posted April 30, 2020 Posted April 30, 2020 5 hours ago, Cyan said: Our update should have only touched natives where nothing had been changed. I will take a look into it. It didnt happen after the latest update, it was the one before that already erased some comments and descriptions. Quote
Cyan 35 Posted May 1, 2020 Posted May 1, 2020 On 4/30/2020 at 8:39 PM, HughJanus said: It didnt happen after the latest update, it was the one before that already erased some comments and descriptions. I've messaged you so that we can look into this a bit more. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.