[WoW] [6.2.2.20490] Release Info Dump Thread

[WiNiFiX]

Removed as requested by VesperCore

[lolp1]

Some free offsets I got from good old reflector, some bots really need to obfuscate properly.

Why would that be? I think it's more like they don't care.

[dragonbane24]

Thanks for the ui frame stuff.


Side note, there is no reason I can think of to bother with porting any existing large code bases to x64. You gain practically nothing. You're not safer from detection, you're not more compatible, you're not gaining worth while performance, you're not getting access to any libs written for x64 wow, etc. If writing a brand new code base, it perhaps might be worth it just because why not?

You're welcome. Again, I can't guarantee everything is 100% correct yet. I still need to double check it a bit. But it seems to read through properly.

I don't know if the performance is better or worse in 64 bit vs. 32 bit. Blizzard went through the effort to make a 64 bit version of WoW for some reason and I had to disable it from launching that 64 bit version so that I could still use the bot. I figured it is one less layer of calls it may have to make through the Windows WOW32 layer. Now I can go back to using the 64 bit version for my main playing as well as botting. It won't gain me much but won't hurt me either. It didn't take too long to convert the code over, mainly just swapping uint for ulong here and there as well as some specific code where Arutha (or myself, can't remember) did an offset of 0x04 instead of 0x08. Maybe 6-10 hours of tinkering overall. And 75% of that was just finding the new offsets.

In the end I'm guessing it is another potential red flag in the bot detection if they see you are using a 32 bit client on a 64 bit OS. Since that means you had to go and change that manually. Does HonorBuddy have a 64 bit version or is it 32 bit only? I've never used it.

[lolp1]

You're welcome. Again, I can't guarantee everything is 100% correct yet. I still need to double check it a bit. But it seems to read through properly.

I don't know if the performance is better or worse in 64 bit vs. 32 bit. Blizzard went through the effort to make a 64 bit version of WoW for some reason and I had to disable it from launching that 64 bit version so that I could still use the bot. I figured it is one less layer of calls it may have to make through the Windows WOW32 layer. Now I can go back to using the 64 bit version for my main playing as well as botting. It won't gain me much but won't hurt me either. It didn't take too long to convert the code over, mainly just swapping uint for ulong here and there as well as some specific code where Arutha (or myself, can't remember) did an offset of 0x04 instead of 0x08. Maybe 6-10 hours of tinkering overall. And 75% of that was just finding the new offsets.

In the end I'm guessing it is another potential red flag in the bot detection if they see you are using a 32 bit client on a 64 bit OS. Since that means you had to go and change that manually. Does HonorBuddy have a 64 bit version or is it 32 bit only? I've never used it.

32 bit only. They would never ban some one for using a 32 bit client that they provided. Convenience is the only real factor of re-writing working x32 code in Wow imo.

[dragonbane24]

32 bit only. They would never ban some one for using a 32 bit client that they provided. Convenience is the only real factor of re-writing working x32 code in Wow imo.

Oh, agreed. Never for just using the 32-bit client. But maybe just by running the 64-bit client, they know I'm not using HBuddy. Might get me the benefit of the doubt if I ever get reported. I mean it's a small chance... but I'll take any extra luck I can get. I sometimes use my main account to bot and I don't want to lose it. (I understand the risks, but I take 'em anyway.)

I wonder if they would ever prevent the 32-bit client from working on the 64-bit Windows? If they ever decided to add that code then it would be another (slight) set back for the Buddy users. (As if the last massive ban wave wasn't a big enough deterrent...)