Quote:
Originally Posted by Ploxasarus
If you have zoom/fov then you can find where clipcam is being done ( camera occlusion ). Strafe has to do with character movement and can be traced into from the X/Y cords.
|
I figured out how to find the new address for the strife thanks to your CE table.
I just searched assembly for the pattern from an earlier post of yours and viola.
Being an autoit programmer I just now have to figure out how to read and write an array of bytes again taking me some time but for now I've gotten it reading as a double.
I'm sure I can find the rest of them that you have scripts made up for now.
I was just having issues starting from scratch and locating these addresses, because for some reason when you use the UnF trainer to change a value cheat engine is not detecting any changes within the memory for me. But that's solved.
The only thing I'd then further be curious with is with the X/Y/Z locations how would one start to trace into the strife given those addresses?
My X/Y/Z values work properly without error, and are nowhere close to the address I'm using for the strife (which is two addresses since you're script writes to two locations) and while in memory view I see no changes to the memory values around or near the X/Y/Z addresses when activating the strife. So I'm still slightly lost....without your CE table I'd be left without the knowledge that I now have.
I still got you on Skype Plox if you ever decide to get on hit me up blinko9 is still my handle. I'd like to discuss a few opcodes with you like you posted up for the example you did for detecting mouse location within the client by scanning the assembly.