Hey, is there an update to the warden bans? Is this bot still getting banned? I love this bot but don't really want to risk getting my account banned. Thank you.
Hey, is there an update to the warden bans? Is this bot still getting banned? I love this bot but don't really want to risk getting my account banned. Thank you.
If you dun want to risk your account, do not bot
I have got this problem, the mouse going to top left hand corner and print "Looking for the Start Button". It was working well, until today. I have no idea what cause this problem. I re-download and the problem still stays.
Last edited by hUi33; 05-19-2014 at 09:52 AM.
^ I have that same problem as well. Not quite sure how to fix it :/.
Running 1920x1080 16:9 Windowed Full Screen.
[LootType]
Legendary=1
Yellow=0
Blue=0
[Settings]
usepotion=1
Resolution=1024x768
Class=Wizard (Build 2)
Loot=Nothing
ShutDown=0
CloseWhisper=0
RunFor=0
Bankslot=1
[Debug]
SelfOnMap=1737,205
$xratio=1
$yratio=1
Current=Looking for Start Button
CoordName=ChatBoxStash
[Stats]
StartDate=[2014-05-21 19:42:55]
LastDate=[2014-05-21 19:42:58]
Runs=1
Sets=0
Legend=0
Yellow=0
Blues=0
Blacksmith=0
Merchant=0
Repairs=0
XP=0
Gold=0
Resolution=1920x1080
__AddCoordsToArray("Start Game", "", "247,511", "203,500", "239,489", "", "250,370", "163,427", "205,429")
247,511 is the coordinates for my screen, but it doesn't press the Start Game button.
Func Startgame()
$runcount = $runcount + 1
print("Looking for Start Button")
Sleep(Random(1500, 2000, 1))
MouseClick("left", _GetCoord("Start Game", True), _GetCoord("Start Game", False))
Sleep(Random(1500, 2000, 1))
Return True
EndFunc ;==>Startgame
Last edited by Wrinkly; 05-21-2014 at 04:44 AM.
Is this bot dead? There are no updates for days. Anyway bot sometimes keep choosing the wrong quest, so babysitting required.
Hi
If i run autoit/bot on my main computer and send key press, mouse click to a vmware running diablo3, could blizzard detect it?
i took a screenshot, how do i get the hex number representing the color of a point that autoit recognizes?
2 Ways:
Grab autoIt v3 Windows Info (it is part of the auto it suite)
zoom into the screenshot, so that u can easily hit the pixel you want
go into Mouse, drag the finder to this pixel
Copy the Color Value. Voilá
Second way:
Grab with an Photo Editing software (like PS, Gimp or heck even paint) your color picking tool
open up your color. in PS you got an Hexcode, maybe on Gimp too, but idk.
Add 0x in front of the hexcode. Done.
If you didnt got an Hexcode:
Color converter - HEX to RGB and rgb to hex color converter
type in your RGB and press on convert.
i think the problem with the bot recognizing the quest is you have to have ALL the quests completed up to kill ghom. anyways thats my theory. basically this bot will work right if you have the exact quest count completion that lubu has.
i am going to do act 1 quest 1 all the way up to ghom and see if this fixes my problem
EDIT i am not sure that that will fix it...we need to know the exact quests that are done of the person that made the select quest file. cause i just looked and on an account that i have every single quest done i know that sometimes it misses the click as well.
any update on this would be appreciated!!
Last edited by izib; 05-27-2014 at 02:19 PM.
izib you are right, I only have some quests to kill ghom/waypoint which my friend gave me. So what I did was finish ALL act quests. Problem solved.
This is safer than best ghom bot because of emulated mouse movement IMO. But best ghom bot is faster.
there is a bug in diablo, after killing ghom it sometimes doesnt update the quest to "return to stronghold" and the active quest is "kill ghom", since the bot changes the quest to the one before the active, it gets "find the breach".
i'm working on a fix, will let you know if it works in the morning and i will upload the bot with the fix.
note: my fix will only be good for 1366 resolution
d3bot.rar
this should work, only 1366x768 resolution.
should detect and handle the quest bug and disconnect on creating a game.
Hey everything works perfect. Only two problems so far. The main one being after the ghom fight and looting it moves to the middle of the room and attempts to leave the game only to have the leave window close before even attempting to find the actual leave button. Then it bugs out.
The other is salvaging, but I haven't got that far cause the bot won't leave the game after the fight and looting. It opens the menu, but closes it right after. like it's set to click open twice therefore closing it as soon as it opens it.
Glad to see someone still working on this btw. Not all of us have big res screens.
Great! Works now like a charm, but now it will find the quest again go to game then say it's found the waypoint and attempt to leave the game. After that it attempts to find the quest again getting even farther down the list. Damn I wish this thing would run smooth. The fight and everything else seems so much more streamlined then before... even the looting is faster.