Quote:
Originally Posted by savsuds
It gives me address of 00455860. When I searched for the Hex pattern, There is no -0x1E. Also it comes up in red. The only times I have seen red is if it is incorrect. I don't know what my next question should be.
|
@
[Only registered and activated users can see links. Click Here To Register...]: The pattern leads you to 00455860 which is correct so far.
Code:
SetValue('ClickToMoveFix', '0x' & Hex(GetScannedAddress("ScanClickToMoveFix", -0x1E), 8))
The -0x1E is the offset from the found address and will leads you to 00455842 which is
almost the correct address.
GWA2 is weird as pattern-scanning has a static offset of +0x1.
So when you also decrease the found address by 1 you'll get the correct address (00455841).
Somewhere in GWA2 you'll found this piece of code:
Code:
WriteBinary("83F8009090", GetValue('ClickToMoveFix'))
So when you'll look in your debugger you'll see the change:
Code:
00455841 3D D3010000 CMP EAX,1D3
becomes (after initialize GWA2)
Code:
00455841 83F8 00 CMP EAX,0
00455844 90 NOP
00455845 90 NOP
Thats the whole trick ... for me it works.
Could you explain how you tested it?