-
Posts
630 -
Joined
-
Last visited
-
Days Won
13
Content Type
Profiles
Forums
Downloads
Gallery
Everything posted by nok1a
-
We can proceed for sure. PM totally fine.
-
Choice totally up to you
-
Oke so you tried to do the group search manually and after restarting of the game that group search done manually doesn't work. It's fine, i won't try to convince you in anything. Well regardless in any script you make use the print() function to see what your script is doing and if it's really doing same thing as what you did manually.
-
The group search -1,049,624,576A;1,092,616,192A;1,082,130,432A;1,056,964,608A;1,062,333,317A::73 ?
-
You will always do that if you not try to use the print() function to resolve the possible issue. Which is really not much of work since you already now how to find the value and how the script is made.
-
Same for you to, welcome back.
-
It's not a 100% rule. I only said that using two devices can confirm the possibility that the group search is static. But im not sure if they really randomly change. That's a huge assumption. You could only be sure after first checking how the scripts behave and which addresses it gives you and performs actions on using the print() function before claiming the values change.
-
A post about this game exist: hello can someone help me change the level of this game? (#nsbqjbd)
-
I guess it all comes down to finding patterns in anything and use some logic with it based on the knowledge you have of that something. I mean, if your gold is 20 and on another device the gold is 20 to. Then i guess that on both devices there is a number 20 in memory...so something is same on both devices. I mean this pattern makes sense i guess if you do not know about encryption yet. But even with knowing it i think it's a logical thing.
-
Aright, i hope it helped. Take the time and play around with it. At some point it will make sense. And use the print() function see what your script is doing. Like that you don't need to guess or assume.
-
If your not finding the group search it means your using the wrong range to search in. Well, when the script doesn't work have you tried testing at which part it stopped working?
-
Well, gg.searchPointer(0) is not that lazy. But gg.searchPointer(500) with ridiculous big offsets is for sure lazy.
-
Also like it's not ok if your doing pointer search in 3 regions. The pointer you need should only exist in one region. To be fair for what i understand accuracy is important. And putting multiple regions is just being lazy. Even using gg.searchPointer(0) is lazy i find. You don't want to deal with all the results you had so you use gg.searchPointer(0). But of course there are cases in which you have no other choice.
-
Because i was not sure in which regions your values would be. I knew mine. Perhaps for you could be different. So i specified all possible regions.
-
Probably because there was more then 1 result with a matching 1.0 float value to filter on. And that probably happened because of having no accurate memory ranges. I can't be 100% sure because i haven't encountered the issue yet. Yes, your pointer was in region anonymous. So if you know that only specify the pointer search to be in region anonymous. Do that before the results are loaded in the result list.
-
https://support.google.com/googleplay/thread/204717992/my-play-store-is-showing-pending-problem-if-i-start-downloading-any-app-what-should-i-do-in-oppo?hl=en
- 1 reply
-
1
-
Just download the file. The link is a link to this post so it's not important
-
I could. To be honest i have no idea about your understanding of GG Lua scripting. But you should learn it. You would get basics quickly for write a GG script and it's user friendly. Can you send the script you currently have.
-
You typed some character near the brackets that's not supposed to be there or the device saved the file wrong. Happened to me sometimes and then i get that error.
-
Oke i understand, so the problem here is the scripting. I can't explain scripting that well compared to other members in the forum. But you should start by running the print() function to print out your tables and have some understanding of what the script is doing. Use --[[ ]] to ignore most of your code and let GG does it thing line by line. Start with doing the group search, then refine and then store the results in a new table named "t" and print it out...something like this. gg.searchNumber("-1,049,624,576A;1,092,616,192A;1,082,130,432A;1,056,964,608A;1,062,333,317A::73", gg.TYPE_DWORD) gg.refineNumber("-1,049,624,576A", gg.TYPE_DWORD) local t = gg.getResults(10) print(t) Then analyze what GG respond. Make sure GG ignores the rest of the code by placing it as a comment: Also check in the GG scripting documentation what it is that you writted
-
It wasn't in the script because i was already at the right address to perform the pointer search on to get to health value. Your at a different pointer then mine using your group search. The table t contains those 4 results you had from performing a pointer search on that one address you had from your group search. You already addedan offset of 0x8 to all those addresses to get to the address that is supposed to hold the value 256 and you stored the new addresses in the table (sensitivity). use print(sensitivity) for see what's in the table. Only problem is that your doing it for all the 4 addresses in the result list while you only have to do it for the one address in region Anonymous. That's why specify the regions as accurate as possible in which you want find the pointers in in or it will already bring issues. The way you added 0x8 to do the addresses you now do the same for the table t in a loop. healthPointer[i] = {address = t[i].address, flags = gg.TYPE_DWORD} add the offset from your start address to the address on which you want to perform the pointer search on to get the health value.
-
You as well need to add the offset from your start address to the address that you want to perform apointer search on, the one below the 1.0 float value. Then all you have to do is add the last part of the code which was to load the table in the result list and perform a pointer search and do +0x4
-
Your telling GG to store the value at offset at 0x8 in data type float. This means that if sensitivity[i].value == 256 then is same as this: if 3.5873240686715317E-43 == 256 then This will return false. Change the type to dword. You should use print the print function to check out what are in those tables. For example print(sensitivity) It will print your table and then you have a bit of insight of what is happening.