I'm not sure why but this has been starting to crash my client. It'll work for a few hours and then the client will be stuck causing me to force close. Anyone else getting this?? Seems weird.
I'm not sure why but this has been starting to crash my client. It'll work for a few hours and then the client will be stuck causing me to force close. Anyone else getting this?? Seems weird.
i got this Error 42002 too. the bot runs now just every 3rd run.
No errors here. Anyway who ever gets errors, i may advice to not bot ATM. In D2 when account got flagged, it usually hanged on making games.
E: i mean when cd-key get flagged, someone would have corrected me so had to edit :P
Last edited by munkki666; 05-03-2014 at 04:36 AM.
Any way to slow down the entering of the game a little bit? When it joins too fast I get stuck at the loading screen....thanks fellas.
has the drops been nerfed? I ran it for 10 hours and I got one legend lol
Hey guys, I just wanted to share some thoughts on how we might be able to optimize the chest running script.
First and easiest fix to help maximize your useful runs (runs where a chest is looted). If the chest 1 detection fails, don't have a detection function for chest 2, just have the bot click where the chest would be then run through the loot search. This will guarantee you never miss the 2nd chest, meaning your only problem becomes the ability to accurately detect the first chest.
The 2 situations I have seen with chest 1 detection: The chest is not there but the bot thinks it is and much less commonly the chest is there and the bot thinks it is not.
Proposed solution: is it possible to have the bot mouse over where the chest would be and do a pixel search on the blue color that appears when you are hovering over a clickable like a chest or armor/weapon rack?
I am not very good with coding these (I don't know the scripting language), but if someone is capable of making these changes, could you please evaluate the idea and code it if you think it is viable? I'm more than happy to monitor the bot and report back on results![]()
open the au3 file and search for
change it toCode:Func RoutineSiege() While $UnPaused MouseClick("left", 237, 503, 1, 0) ;Clicking Resume Game
This will make to bot wait after leaving the game and clicking resume game (if you increase / decrease 5000, 5200 it will wait longer/shorter ) .Code:Func RoutineSiege() While $UnPaused Sleep(Random(5000, 5200, 1)) MouseClick("left", 237, 503, 1, 0) ;Clicking Resume Game