I'm not sure if there is another way (specifically debugging):ġ. Not to worry: the filtering would be very much quick till you find the right address (in most cases you'll need 1 Initial GroupScan, followed by 1 GroupScan filtering). Just keep filtering with those found addresses. I don't think you're missing something cause its default color is red. The good of this thread is that more CCrush users can know about this tips. All my tries results in a bunch of address in red. Also, debuging any address (by applying 'find out what access this address') is not a very good idea. We know that looking for a working pointer is quite useless since BlueStacks kind of 'hides' its real process that we have to hack it via Physical Memory. So, we may need to keep searching the address on each stages.
This will greatly reduce filtering later.Īlso, i've just played it again, and it turns out that movement address is not static. Since the game stores those value in particular order, then we can gain advantage in searching the address with GroupScan mode instead the normal one. The float -1 is a constant (i don't know what's the purpose yet). In your example, you put 4 bytes for 2, 4 bytes for 16 and float value to -1. So, is there a way to change, for real, the value, not just blinking? What is wrong? The worst part, I'd already achieve, i.e., find the address. If I tick checkbox under Active column, the value at game screen keeps blinking, nonstop, but showing the old value. At game screen, the value blinks, but don't change.
So, someone could point the right direction to me and warning what I'm doing wrong?Īfter more tries, I could find two address, one for number of moves and the other, for points.īut I have a problem: when I change the value, it changes quickly and come back to the old value. I've also tried opening BlueStacks processes, like HD-Agent, HD-Frontend, HD-Sharedolder, HD-BlockDevice, HD-Network, HD-Service and HD-Adb. I've tried changing settings to search inside memory region types, like MEM_MAPPED, using Windows and Kernel Mode Debugger and also using Query Memory Region Routines and Read/Write Process Memory. I've tried searching Physical Memory, using New and Next Scan, as described in Tutorial, but no address worked. I've searched about it, but only got results about the game running with Crome or Firefox, not an emulation, like BlueStacks. I'm trying to find out the system process or memory address to change values of Candy Crush inside BlueStacks. Posted: Tue 3:04 pm Post subject: Memory address for BlueStacks running Cand圜rush
0 kommentar(er)
