[OpenSource] WoW Bot Project C++

[Vragoth]

This looks like fun I would use a Hook as I have not seen Blizzard attempt to detect bots in a long time... But it would be fun to try and do it out of process... +rep

I would rather be safe then sorry.
Hooking may be the easiest and fastest way to do it.
Not hooking may take longer and more work but it'll be worth it in the end.

[ejt]

I would rather be safe then sorry.
Hooking may be the easiest and fastest way to do it.
Not hooking may take longer and more work but it'll be worth it in the end.

Agreed. Now could we please stop taling about hooking in this thread?

There are alot of pros and cons with hooking compared to out-of-process for sure, but in this code there is no hooking and probably never will be and the simple reason for that is that its to easy to detect if Blizzard decide the want to start banning the software. If you want to do in-process hooking you should do either of two options: (a) keep the project a secret and only release to the people you trust (including closed-source) or (b) develop a great anti-warden protection and keep that closed-source.

Glider used hooking (with a very good warden protection) afaik, and look at how that turned out. HonorBuddy uses out-of-process and still kicking.

For those of you waiting for an update, I've been out of town for a few days but will be picking up the development again.

[Thongs]

IIRC, isn't it the other way around - Glider was OOP and HonorBuddy is in-process?

[~Unknown~]

Agreed. Now could we please stop taling about hooking in this thread?

There are alot of pros and cons with hooking compared to out-of-process for sure, but in this code there is no hooking and probably never will be and the simple reason for that is that its to easy to detect if Blizzard decide the want to start banning the software. If you want to do in-process hooking you should do either of two options: (a) keep the project a secret and only release to the people you trust (including closed-source) or (b) develop a great anti-warden protection and keep that closed-source.

Glider used hooking (with a very good warden protection) afaik, and look at how that turned out. HonorBuddy uses out-of-process and still kicking.

For those of you waiting for an update, I've been out of town for a few days but will be picking up the development again.

Glider was sued in court. Honorbuddy I know for a fact is in-process. Both of these bots have had banwaves. Not discouraging your choice to be OOP, but don't just give reasons that don't make any sense at all.

[NewNerr]

Hi,
It seems that I cant download it with SVN, could you check it?
Thanks

[nsfnd]

Hi,
In WoWLocalPlayer.cpp
This

return Mem.Read<int>(Descriptors::PLAYER_FIELD_XP);

should be like this.(From [[pBase+08] + 0x477 * 4]

return Mem.Read<int>(Mem.Read<unsigned int>(ObjectPointer + Descriptors::DescriptorOffset)+  Descriptors::PLAYER_FIELD_XP*Descriptors::DescriptorMulti);

[hamburger12]

Haha did you remember Pirox? Also that bot got a Banwave and it was passiv ;-) so it's the way you solve your stuff and if you use the luascripting without injection its may easyer to detect the bot, if you don't use the right way to get the data ;-)

[DarkLinux]

The ban wave was from an archaeology script that even the devs new was not safe...

[CreativeXtent]

where is the dl for this?

[firepong]

where is the dl for this?

Read about 75% down the first post and you will see a SVN link. The only way to get it right now is to download through SVN.

P.S. I'm slowly converting this over to C# and making it use GreyMagic instead of the way it's working right now. Got a few things working, but it's going slow lol

[gxavier]

Great work ejt!

But did you stop working on this great project?

Will there be updates in the future (5.2)?

[firepong]

Great work ejt!

But did you stop working on this great project?

Will there be updates in the future (5.2)?

All you have to do is grab the updated Descriptors and Offsets from the latest Info Dump thread and punch them in and recompile it. I did it and it works just fine. Make sure you add in the Descriptors that are new and remove the old ones as well as going through the code to make sure that it is still calling the right things. Other than what I just said, everything else is the same.

[gxavier]

All you have to do is grab the updated Descriptors and Offsets from the latest Info Dump thread and punch them in and recompile it. I did it and it works just fine. Make sure you add in the Descriptors that are new and remove the old ones as well as going through the code to make sure that it is still calling the right things. Other than what I just said, everything else is the same.

Thank you firepong - it works!

But ejt said that he will add some new functionality.

So will you extend this great project in the future, ejt?