if you want it to be real fast edit SnipeBuyout.lua and remove Sleep(1000). haActionSearch() works like this:
- clicks search button
- waits for results with 1 ms polling delay
- succeeds if something found else fail
if you want it to be real fast edit SnipeBuyout.lua and remove Sleep(1000). haActionSearch() works like this:
- clicks search button
- waits for results with 1 ms polling delay
- succeeds if something found else fail
Thanks for the clarification! Unfortunately, I believe removing haSleep in SnipeBuyout will hit the input limit error within seconds, and get me banned soon after. I'm using haSleep(2900) currently and I'm still getting kicked after an hour or so.
Last edited by lycra2; 08-12-2012 at 10:44 AM.
well theres your answer... AH bots can only be so fast. unless theres some special way to disable that input limit error
you could always hate**** it and use the relogin function but abusing that will surely get you banned. though a few input limit errors wont because regular users get them all the time.
I'm plenty happy with the speed now. My sniping success rate is way higher and the items that are purchased are better quality items with the same search parameters. The relogin function will be useful for the disconnects, but is problematic for now, because the "Search Equipment For" box resets to the default hero after login. For now, I suppose I can have it search once for a class specific armor if it logs in, but I'm not exactly sure how to script that. haActionReLogin() is true as long as I'm not disconnected, not just when it is called to login. So I can't use that to trigger a conditional operation. Can you give me a hint?
Last edited by lycra2; 08-12-2012 at 01:08 AM.
im changing relogin to return false if it does nothing.... so it will only return true if it successfully relogged in. that way you can redo whatever filters if it happens. ill update in a few hours once i improve relogins speed too
Thanks for the new update! Since I can't test this unless I get kicked, let me know if this is correct:
haRelogin('user','pass')
while true do
haFilterType('Mighty Belt')
end
I placed this at the end of the main loop.
well its more like this
you can test relogin without hitting input limit by disconnecting your internet then calling haSearch(). you will get dc error which is effectively the same thing.Code:while true do .. my main bot loop which will break if it fails.. haRelogin(..) end
ChuiChui, I've been searching on these forums but can't find too much information on how/what activity the warden monitors. I was wondering if you have any info I could read? From what I understand in these posts you do considerable memory reads but only one memory write? Is that correct?
Thanks
No body knows how Warden finds people. There are certain things that are obvious (like memory INJECTION - different than memory read/write), but honestly... if you bot you will be caught. I know of plenty of people who ran AutoIt bots that only used pixelsearching, which rann only 6 hours a day, and took 15 minute breaks each hour, and they still got banned. My advice: bot it as fast as you can until the next banwave - use your profits to buy a new game
regarding warden people concern themselves way too much with the client side... when warden mainly bans based on server side detection. ie: if you spam them 24/7 in a manner no human would do.
client side warden only checks if youre writing to its instruction memory. even then thats limited because many legit apps, like FRAPS, do the same. it no longer even scans your applications either (due to some lawsuit).
thanks for this. this isn't as complicated as it looks lol, all anyone has to do is read the readme and they should have everything they need to make their own script.
Hmmmmm....
Thank you very much for making background botting possible again This bot is just amazing.
Great job so far!
- Lennix
ya that last one took some effort... its actually fully backgroundable now (except stash stuff) as opposed to 0.9.4 which required the filters part showing up
ChuiChu, First tnx you for this wanderfull proggi. i use it succesfull since ver 9.3
Now i'm i the only having this problem where we are all istant snipping on the same item, apparently bugging it?
I mean it look like, many items i bind on, get bugged as soon as i snipe them, and my guess is that many oter happyauctioner snipe it the same istant, result, the item become bugged and noone can buy it.
Is it just me?