Where and when errors occur, take screen shot; and NOT from where it is not having problems.
Using the previous screenshot and log.txt, It was obvious to me that it was not moving.
However, this new screenshot tells different things:
1. Ghom is already up front
2. BKBOT is still in "Larder Corridor"
This implies to me that GHOM's purple name is not recognized.
Checking further, his purple name is different from 1920x1080 and 1600x900.
Download new version. Tested with 1280x720p
Last edited by burgaud; 06-28-2014 at 09:10 PM.
Sorry for the confusion, I just downloaded the new version and it works perfectly fine now
One more thing, when I'm using wizard and turned into Archon mode, the bot won't use Archon Blast skill, even though I set TimeOut1=1000. When it turn back to normal mode it can use the skill I put in the first slot perfectly normal. Also, it sold a legend I just looted, so i tested if it will sell set gear too, and it does
I'm guessing the colors on 1280x720 are different, because I tested on 1920x1080 and 1600x900 and both didn't sell any legend or set gear.
Last edited by khongx; 06-28-2014 at 10:18 PM.
That unfortunately is the drawback to the new version with "better skill availability check".
It first takes a screen shot of the skills icons when it first go down to larder.
It uses this template to determine if skills are available (not grayed, no cooldown)
When you turned into archon, these icons changed and therefore, recognized as NOT available.
Solution: No solution as of now.
How about using a Wiz build I posted (i was able to do T4) while an archon build using same gear barely do T3
Wait for an update wherein, user will be able to use archon (second skill icon sets) and be able to use skills.
Selling of legs? this means, the delay for checking leg is too short for you. dig up a few threads before regarding increasing duration for leg checking.
It does work to checking leg on 1280x720p, i;ve tested it on a Wiz recently after it found an SMK (albeit lame roll).
at any rate, I'd return back to you in 8 hrs.
For the Archon is not a problem, even without Archon Blast I still able to kill t4, but just few seconds slower without it. For the legend checking, I changed the delay from 250 to 500, then 1000 and it still selling the legend and set gears, as if it didn't recognize those items are Account Bound at all. Also, it didn't put in stash either.
This is what I did to make it work on my laptop, I had to customized my resolution to 1600x900 (my default maximum resolution is 1366x768 ). After this, even with 250 for the delay checking leg, it still works fine.I tested running d3 on1280x720 and 1600x900 with my screen resolution of 1600x900 everything runs very smoothly. So I went and tested out what happen when I changed my screen resolution to 1280x720 then ran d3 on 1280x720, 1600x900, and the resulted was that both of them did sell leg and set gears. So maybe the problem was the screen resolution, not the d3 resolution.
Last edited by khongx; 06-29-2014 at 12:41 AM.
I have found a very reliable method of forcing D3 to play in different 16:9 resolutions without downgrading my native desktop resolution. Secondly, D3 is designed and intended to be played on 16:9 resolutions, here is proof:
In light of these, I have decided that I will not be developing BKBOT for non 16:9 resolutions and instead, teach you how to set up D3 to play in the supported resolutions: 1920x1080, 1600x900, 1280x720 natively-without Letterbox.
Here is how:
#1. Resize Desktop to desired Target Resolution
#2. Set D3 to run on desired resolution in FullScreen; click accept click apply
#3. Set D3 to Windowed Mode
#4. Manually resize D3 to smallest size and move to top left corner
#5. Restore Desktop back to maximum size
#6. Change D3 to Windowed Fullscreen.
It should now be running in desired resolution and anchored at Top-Left corner, now compatible with BKBOT
CAVEAT: This however is temporary. Each time D3 runs, it will load covering the whole desktop again.
I do not know if this will work for Win7.
Last edited by burgaud; 06-29-2014 at 04:58 PM.
Version 20140630 contains hotfixes to identify AccountBound text properly on 1280x720
Tested to stash BOA items
Tested to not sell BOA items
Tested to not salvage BOA items
Tested to pick up loots
Archon Build is now re-supported. You have to specify "Archon" as Target for that skill:
TimeOut1=500Code:Arcane Strike Archon Build Non-Archon Mode +-------+---------+---------+---------+---------+---------+ | 1:EB | 2:Buff1 | 3:Buff2 | 4:Buff3 |L:MMissle|R:Archon | +-------+---------+---------+---------+---------+---------+ Will cast BUFFs 1 to 3 first, then during fight, will cast EB and enter into Archon Mode In-Archon Mode +-------+---------+---------+---------+---------+---------+ | 1:AB | | | |L:AStrike| | +-------+---------+---------+---------+---------+---------+ Will spam Arcane Blast, and Spam ArcaneStrike non-stop
TimeOut2=60000
TimeOut3=60000
TimeOut4=60000
TimeOutL=0
TimeOutR=60000
Target2=Buff
Target3=Buff
Target4=Buff
TargetR=Archon
If Ghom is still alive after 20 seconds (Archon's UpTime), BKBOT will spam Skill#1 and Left Mouse.Code:+-------+---------+---------+---------+---------+---------+ | 1:EB | 2:Buff1 | 3:Buff2 | 4:Buff3 |L:MMissle|R:Archon | +-------+---------+---------+---------+---------+---------+
Last edited by burgaud; 06-29-2014 at 10:13 PM.
i already download from the drop box
but icant see any attachment (1. Install AutoIT. This bot does not include EXE file; only the raw AutoIT source file.)
how to install it guys ?
I will forget at times to set the game back to private game instead of a public game. So if i just start this and walk away it will do the correct campaign, hero, difficulty but then leave it at public game. Anyway to add setting it to private to ensure everything is correct?
When in Larder Corridor, BKBOT walks to the center of the room while checking for Cut-Scene. When a Cut Scene is detected, it waits for it to finish to start the fight. However, if disconnected, the whole screen Looks like a Cut-Scene and BKBOT will wait INDEFINITELY! The Error Recovery code will not kick in because it was placed After the Wait-Cut-Scene code.
Please modify BKBOT as shown below:
Just move up the TimeOut statement to ensure it checks for errors first.Code:elseif $STATUS = "Larder Corridor" then if IsTimeOut($TimeOut) then $ErrorCount += 5 $STATUS = "Error: Could not find Ghom" elseif PixelGetColor($XCenter,YRatio(45))=0x000000 then ;Cut Scene if $z<>9 then LogMessage("Cut Scene") $z = 9 ;prevents moving due to a sequence jump if _IsPressed("01") then MouseUp("left") ;stop left click if _IsPressed("02") then MouseUp("right") ;stop right click if _IsPressed($KeyMove[2]) then send("{"& $KeyMove[1] & " up}") ;stop moving if _IsPressed($KeyStand[2]) then send("{"& $KeyStand[1] &"up}") ;stop standing elseif IsBossExist() then $STATUS = "Move To Position" if $WaitAfterMapChange>0 then sleep($WaitAfterMapChange) $TimeOut = SetTimeOut($FightPositionTimer) elseif $z < 8 then MouseMove(XRatio((960+1625)/2),YRatio((460+100)/2),0) if NOT _IsPressed($KeyMove[2]) then send("{"& $KeyMove[1] & " down}") elseif $z=0 then sleep(500) $z=1 IsSkillAvailable(0,1) elseif $z<7 then if $SkillTarget[$z]="Buff" then sleep(250) send($z) $FightTimers[$z] = TimerInit() endif $z+=1 endif endif
Im having problem running it on vmware. It is sometimes stuck in the larder portal not being able to go down. any ideas why? but on my desktop it is fine no issues. vmware is 1600x900; desktop is 1920-1080.
almost p700 now. you should write a hellrift bot. that should give more experienze!
I think the problem you have is with regards to BKBOT clicking on the portal down to larder.
This is a hit & miss issue depending on several factors. I suspect it has something to do with either:
a) the game is slow on vmware such that, it clicks faster than the game
or
b) wrong coordinates? but you are getting stuck only sometimes and not all the times. this rules out this possibility
therefore, i suggests you to add more delay
increase that to 1000, upto 2500 in increments of 500. default is 500 only.[RunTime]
WaitAfterMapChange=1000
I also encounter errors here too on 1280x720p resolution vmware.
Honestly, I have tried several codes for this part. Currently I am testing a 2 part system wherein it first walks towards the portal, then after x seconds, bot is assumed to be on top of the portal, click on the spot where bot is (which would be the portal to larder). It is a lot slower, but upon tests on 1280x720 vmware, it seems to be working right.
Last edited by burgaud; 07-03-2014 at 04:53 AM.
Quick question - How do I pause/Abort the latest version of the bot? I used to press "END" key on my keyboard. Doesn't seem to work now.