Leaderboard

View File Real Racing 3 (12.6.8) Cars/Events Unlocker REAL RACING 3 CARS/EVENTS UNLOCKER Current version: 12.6.8.6.3 Working RR3: 12.6.8 Description: Run this script to unlock all cars and old closed events/races!!! Instructions: Run the script wherever you want, then go to the garage and get any car for free (also old nascar cars). Script will re-open old finished events Known issues: May not work on all devices/emulators. Note: Video: Submitter MarioRossi93i Submitted 12/15/2020 Category LUA scripts  

It doesn't matter how clever he is, if he can crack show the script source keys. Example: local Key_1 = {{80,49,61,29,70,55,23,61,60,35},{68,88,45,42,63,26,22,18,22,46},{64,83,58,86,62,99,82,67,29,57},{79,79,51,18,72,75,48,58,51,46},{90,66,50,22,20,44,17,25,13,40},{72,16,59,52,40,51,37,71,18,79},{56,87,97,87,23,51,98,95,11,78},{67,98,61,82,24,55,26,37,68,74},{91,69,52,89,38,37,57,40,40,19},{80,67,67,39,69,69,59,53,63,81}} local Key_2 = {10,6,9,7,8,4,8,2,8,7,10,1,1,1,8,1,9,6,1,1} On the source key encryption does not exist. local sourceKey = {69,57,82,98,26,80,80,67,37,80} How to decrypt this code: Example = needDec({55,10,147,63,226,126,23}) We'll call the destroyer El. If El can really break my encryption, I just ask El to show you the source of the code (sourceKey). At least he showed it on video when he decrypt.

Aimbot doesnt go in enemy coordination its about the how many turn for example Edit to 99999 it turns very high

I guess you can found some tutorials for pointets here. Honesty finding pointers easy on PC but for android its hard.

Finding coordinate easy. Use float and fuzzy search then move your player to higher or lower place then refined using increase or decrease search . do it some times and found your player z coordinate. Now go to memory editor and look nearby values you can found x and y co-ordinate and all done. About aim lock I don't know that much but try to use pointer search to find it or search weapons related values then pointer search. Another method search random values and try to edit them if you found any helpful stuff. Good luck !!

orait...here we go. MM_CoinGem.mp4

Nice ryms man

If you already know the hex value for 2020 then search it directly in hex format

Your encryption free and good . But its not best because now someone decrypted elgg encryption and in sellg we can't use old gg

The code dont work

Their is many ways to approach this... None of which are a definite, especially if this drop rate is truly done server side. 1. Find enemy HP. Navigate nearby/pointer search. Start find nearby and other pointer data. Sometimes drops are related to enemy or linked to enemy. Drop might already be determined and linked to enemy before he is even killed. Basically drop is generated on level load, no enemy kill. 2. Focus on finding weapon info. Like id numbers or utf and pointer search to find weapons. Then, before opening level. Unknown search. Start level and get weapon to drop. Then unknown changed and then search for that specific id/utf. Then you can pointer search your way back to see if anything nearby to pointers could be related to this drop. Which could be related to info done in method 1. 3. Game is il2cpp. Do a dump, search the dump for "rarity" "drop" "chance" or other keywords that may be related... Forthis game, some things from the dump that MIGHT be of use.... public Rarity get_Rarity(); // RVA: 0xBE8BA4 Offset: 0xBE8BA4 [CompilerGeneratedAttribute] // RVA: 0x889DC4 Offset: 0x889DC4 public void set_Rarity(Rarity value); // RVA: 0xBE8BAC Offset: 0xBE8BAC public string get_RarityString(); // RVA: 0xBE8BB4 Offset: 0xBE8BB4 public void set_RarityString(string value); // RVA: 0xBE8C50 Offset: 0xBE8C50 [CompilerGeneratedAttribute] // RVA: 0x889DD4 Offset: 0x889DD4 public int get_Chance(); // RVA: 0xBE8DA0 Offset: 0xBE8DA0 [CompilerGeneratedAttribute] // RVA: 0x889DE4 Offset: 0x889DE4 public void set_Chance(int value); // RVA: 0xBE8DA8 Offset: 0xBE8DA8 [CompilerGeneratedAttribute] // RVA: 0x889DF4 Offset: 0x889DF4 private int <DropChance>k__BackingField; // 0x114 [CompilerGeneratedAttribute] // RVA: 0x8720D0 Offset: 0x8720D0 public int DropChance { get; set; } [XmlAttributeAttribute] // RVA: 0x8A0F90 Offset: 0x8A0F90 public int get_DropChance(); // RVA: 0xCC4C08 Offset: 0xCC4C08 [CompilerGeneratedAttribute] // RVA: 0x88AC64 Offset: 0x88AC64 public void set_DropChance(int value); // RVA: 0xCC4C10 Offset: 0xCC4C10 [CompilerGeneratedAttribute] // RVA: 0x88AC74 Offset: 0x88AC74 then you could edit the lib file. Or use GG to edit offsets (if on mobile device) typically XA memory range. You'll want to use ARM to HEX to modify the offsets correctly. 4. Could try search random float values and mass editing... Not ideal, but more of a last resort. So start with .19~.21 float, edit all to like 1.0. One problem with this, you don't know if percentages are float, dword or double. 20% could be, 20.0 float/double/dword. 0.20 float/double. Then you don't know if its an even .20... Might be 0.1975. Again, this really isn't a good method. Hope this helps. Figured it is far less time to type this entire post than to attempt to do the methods mentioned above.