some part can be done, but most can not. Hence bot will not be functional anyway.Quote:
Hi there, I'm also interested to help. My main is also C and C++.
May I also suggest pixel bot? As it is future-proof so we don't have to keep updating the offset.
I had done pixel thingy scripts for D3. It is really not reliable approach and also very faulty behavior with small changes in the client window etc. Writing a bot that only reads memory passively is very safe approach. I did a lot of botting back then in D3 for fun and I noticed the only way that Blizz could detect undetectable bots (both passive or warden proof bots) was using the patterns of bot behaviors. i.e. when you implement A-star algorithm for navigation, bot always tend to move certain locations in each map segment (If you played wow with honorbuddy you most likely have seen some bots moving on top of each other in BGs). I believe blizzard used the same algorithm to find such patterns and one day a lot of people got banned wondering why, because buddy guys insisted that warden still could not detect their bot in the memory. Also, blizz invested a lot of resources against botters (as well as suing some of the bot makers) but I don't think that GGG is going to do this. Therefor no matter what approach we use (pixels, passive or active), not-human behavior of the bot will be its pitfall in the end.