No longer being released.
No longer being released.
Last edited by Aristona; 10-25-2012 at 03:48 PM.
Would this inflict a ban? Considering you're actually memory scanning, easily tracable.
Memory scanning is not that easily traceable.
Btw. try scanning for the following bytes: 0x44, 0x33, 0x5F, 0x49, 0x54, 0x45, 0x4D . That should get you pretty close to the AH address.
Why dont u replace Mouse Click with SendMessage/PostInput so it can be background :P
Indeed, but there is no other way of making a bot without hooking the process. Perhabs only if you can pixel track the numbers. (or I may be mistaken)
I'm not good with WIN32 API's. I was using it on my unused laptop so never bothered to upgrade actually.
I'd say safest bet would be just use loads of pixel recognition, barely tracable, and throw in some random movement.
However, good job and kudos, easily read and well commented code.
Reading memory vs pixel recognition makes no difference from a security standpoint, neither one is detectable by warden. Only writing/injection is.
That said, a bot of this nature warden is the least of your worries - there's a boat load of server side behavior checks. How often are you querying the AH, what are you looking for, how long are you on for, etc. AH botting must be throttled to within reasonable human behavior.
pretty clever !
I liked your idea, gonna study and learn a way to read the attributes
Hmm, how are we sure about what Wareden does. What I heard, it doesnt recognize mouse/keyboards events (so no need for random clicks). It doesnt recognize memory reading. If this is fact, why are ppl using detectable bots jsut for a slight increase, if autoit is not possible to get caught with??
Thanks for the source and the miniature guide on finding the addresses for the buyout slots.