Memory Hacking Software

Ok, I'm looking for pointers to how much gold a mine has..
I got this far, each time entering the expression into the expression editor.

Code: Select all

[[[[0x8bc22e0+0x8]+0x40]+0x30]+0x54]+0x198

Now, Expression Editor returns this :

Code: Select all

79576436 (4BE3D74)

Which is the same as my orignal address, so all good.


When Pointer Search 0x8bc22e0, and I Disassemble/AutoHack, I'm just looking around at the new values and plugging those into the Expression Editor when I notice my last entry ([[[[0x8bc22e0+0x8]+0x40]+0x30]+0x54]+0x198) now doesn't say 4BE3D74, it says "Unresolvable".


Why did it change? I didn't change or lock any values. All I did was Pointer Search and AutoHack. Didn't NOP anything..

This has happened before, and I don't understand why.

Pros, plz explain/

I’m not quite sure but if i’m correct, but please allow me to try to help...

From your expression: [[[[0x8bc22e0+0x8]+0x40]+0x30]+0x54]+0x198,
the bold-ed expression is quite ’suspicious’..

I would dig the 0x8bc22e0 pointer deeper if i were you. I don’t think that’s
a static pointer yet... That’s all i can think of...


Please correct me if i’m wrong..

Whitehat wrote:I’m not quite sure but if i’m correct, but please allow me to try to help...

From your expression: [[[[0x8bc22e0+0x8]+0x40]+0x30]+0x54]+0x198,
the bold-ed expression is quite ’suspicious’..

I would dig the 0x8bc22e0 pointer deeper if i were you. I don’t think that’s
a static pointer yet... That’s all i can think of...


Please correct me if i’m wrong..

Well, see...

I know this isn't the static. I'm on my way to getting the static.

When I move to the next search, I find some stuff in the Auto Hack.

When I look back at the expression editor to input the new data, I see that my last entry is now Unresolvable

So, I guess my question is really this : "If the expression editor returns 'unresolvable' after initially returning the correct base addy, is it ok to continue going down the path that the now-unresolvable pointer showed me?"

if your answer is this: "do i need to continue searching with that invalid pointers" well then the answer is no.


, is the game you are trying pointer searches on warcraft 3?

SpeedWing wrote:if your answer is this: "do i need to continue searching with that invalid pointers" well then the answer is no.


, is the game you are trying pointer searches on warcraft 3?

Well when I got them they weren't invalid. They showed up fine at first, and even entered.. Then I looked back later and they were "unresolvable". So is that still invalid?

And yes, it is WC III

try going further, ive had games that half way thru the pointer search its unresolvable but the next address i found turned it back to normal. i should also mention that every pointer in the game was like that, so i assume its part of the anti cheat or somethin.

like whitehat said, that address [0x8bc22e0+0x8] doesnt look right, maybe its supposed to be [0x8bc22e0]+0x8] ? that would be a likely cause of your problem too.

[0x8bc22e0+0x8] wouldn't this be teh same as [0x8bc22e8]?
well anyway - try still using the unresovable one, i had it qwith WT, it showed unresolvable but when i added it into my cheat table, it just got the right address, but the pointer still said unresolvable.

Alright, thanks guys, I'll keep going with it. I wasn't sure if it was worth it to go all the way through with the pointer searches if halfway through I failed.

with pointer searches in loa i learned, that if you get a sort of looping in the same area your pointer will turn out wrong

for example, if your base would stay in the area of 0x732000, then you would be wrong, then try a new first pointer.

( if so then start all over from the address that you want to point to )