I think I'm making some progress .
I think I'm making some progress .
Last edited by Dearleader; 10-22-2008 at 12:28 AM.
Jesus christ that shit is ugly. Do yourself a favor and scrap it.
Throw me a bone...I'm trying to fix as much as I can to make it better; What exactly would you change or scrap to make it better. Do you just think the code looks ugly or it's just inefficient. Thanks.
I meant all of it.
Take a look at the stuff Charmander posted and you'll see how the structs changed, the change of the relative offsets is caused by a change of the structure, you'll just need to port these structures to autoit and ofcourse fix the pointers, I'm not shure if the nextObject ptr is still at the same offset, you'll need to check how WoW walks to linked list to get your new offset.
There is a lot of work to be done to get this bot back to run, you should over think if it's worth the effort, it wouldn't be harder to recode the entrie bot in an other programming langueage like cpp or Java (if you use Csharp plx use Mono, Microsoft .Net Framework is evil and Visual Basic is even more evil!).
I would have written "Hell that shit is ugly." but you're still right :-) autoit looks like dog crap...Jesus christ that shit is ugly.
I hacked 127.0.0.1
Down with the man!!!
Micro$$$oft suckss$
the difference is in a few values, these were the only values changed in last patch, you want so bad fix it, use IDA or some other program. Also that list may be messed that you are working on also because its a pretty intensive patch..
Code:Const $G_WMRTlsIndex = 0x00E2563C Const $G_WMRStaticMapIdOffset = 0x00E18DB4 Local $wowObjectPointer = _ReadProcess($wowProcessHandle, $TLS_Slot + 8, "ptr") Global $wowPlayerGUID = _ReadProcess($wowProcessHandle, $TLS_Slot + 16, "uint64")
Last edited by Justink15; 10-21-2008 at 03:10 AM.