BK Ghom Bot (fully customize-able skills)

[Blitzzzz]

Regarding my previous problem of a crusader chasing after pixels thinking it is loot? I think that might not be the real problem.

I find that sometimes, after killing ghom, my crusader moves upwards of the map, and when that happens, during the "loot phase" the mouse is not able to detect item names which are located downwards of the map. And the character then moves upwards even more whilst attempting to scan around for loot, before teleporting away.
I've observed that legendaries are sometimes missed this way too.

Is there any way we can rectify this?
The main problem I've seen lies in the character moving around after Ghom has been killed. If we have some way to stop the movement immediately after Ghom's death, that should prevent the character from moving out of the scannable loot area problem.

[burgaud]

Regarding my previous problem of a crusader chasing after pixels thinking it is loot? I think that might not be the real problem.

I find that sometimes, after killing ghom, my crusader moves upwards of the map, and when that happens, during the "loot phase" the mouse is not able to detect item names which are located downwards of the map. And the character then moves upwards even more whilst attempting to scan around for loot, before teleporting away.
I've observed that legendaries are sometimes missed this way too.

Is there any way we can rectify this?
The main problem I've seen lies in the character moving around after Ghom has been killed. If we have some way to stop the movement immediately after Ghom's death, that should prevent the character from moving out of the scannable loot area problem.

[Fight]
LastSeenTimeOut=1000

The only way for detecting GHOM being still in the room is by pixel scanning his purple name (all bosses have this). However, some skills, most especially from Crusaders causes the screen to flash, to blur and so much more such that Ghom's name would "disappear" for a short moment. By including the above setting wherein "Ghom is absolutely dead" occurs only after his name is no longer on the screen for "LastSeenTimeOut" duration.
Having a shorter LastSeenTimeOut means your toon will stop attacking/moving earlier.
Having a longer LastSeenTimeOut means there will be less errors detecting Ghom.
LastSeenTimeOut=500 should be ok.

This will force bot to stand still and attack in place. And considering GHOM is melee, you wont have problems.

[Fight]
ForceToStand=1

Do not worry if Ghom fled far; BOT will nonetheless close in periodically with MaxDistance setting every 5 seconds.

[Fight]
MaxDistance=250

BTW. What is your config.ini? Can you post it?

[nonameowns]

woah after today farming, I got 3 rare legendaries. ice climbers, rimeheart, and shard of hate. That's is total of 4 rare legendaries with rare mojo I found last week. Haven't find furnace or SMK yet though :C

I noticed you updated the bot, is it more efficient than before or just made it easier to use?

[burgaud]

woah after today farming, I got 3 rare legendaries. ice climbers, rimeheart, and shard of hate. That's is total of 4 rare legendaries with rare mojo I found last week. Haven't find furnace or SMK yet though :C

Furnace, I am not sure if I found one with BKBot or not, but one thing for sure, I have salvaged it without knowing its real value. I believe I once salvaged all 2handers with low DPS, or no socket as I was running out of space.
Oh crap. You'd reminded me of Rimeheart (the Frozen sword).. sadly, I salvaged that one too (same story)!

I noticed you updated the bot, is it more efficient than before or just made it easier to use?

It is not more efficient than version20140604, just some minor bugfixes (in the quest selection); But support for non-english is the only highlight for this. As I find more time experimenting with different resolution, Id be able to support them as well.

[dochollywo]

Sigh...

ImageSearch.au3 did not declate variables.
and perhaps you have your autoit in strict var declaration

edit ImageSearch.au3 to declare variables by inserting local on $result and $array as shown:

Func _ImageSearchArea($findImage,$resultPosition,$x1,$y1,$right,$bottom,ByRef $x, ByRef $y, $tolerance)
	;MsgBox(0,"asd","" & $x1 & " " & $y1 & " " & $right & " " & $bottom)
	if $tolerance>0 then $findImage = "*" & $tolerance & " " & $findImage
	local $result = DllCall("ImageSearchDLL.dll","str","ImageSearch","int",$x1,"int",$y1,"int",$right,"int",$bottom,"str",$findImage)

	; If error exit
	if $result[0]="0" then return 0

	; Otherwise get the x,y location of the match and the size of the image to
	; compute the centre of search
	local $array = StringSplit($result[0],"|")

	$x=Int(Number($array[2]))
	$y=Int(Number($array[3]))
	if $resultPosition=1 then
		$x=$x + Int(Number($array[4])/2)
		$y=$y + Int(Number($array[5])/2)
	endif
	return 1
EndFunc

I cant say if that will solve it, as I am not getting any error with imagesearch.au3 but judging from the error, it should.
Let me know if that is indeed the solution

The solution was quite simple. Your original code is fine. I had to run the script in x86, since I have the x64 version of AutoIt installed.
Maybe hint it in your instructions. x64 is quite common now.

[Blitzzzz]

BTW. What is your config.ini? Can you post it?

[RunTime]
Model=Your Bot's Name
HERO=1
RunTime=12H,12H
RestTime=10M,10M
LogFile=log.txt
Battle.net=C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe
CreateGameTime=30000
TownPortalDelay=5000


[Fight]
MaxDuration=200000
WaitBeforeMoving=800
FightPosition=1292,280
FightPositionTimer=750
MaxDistance=800
ForceToStand=1
LastSeenTimeOut=1000


[Skills]
TimeOut1=1000
TimeOut2=1000
TimeOut3=1000
TimeOut4=1000
TimeOutL=0
TimeOutR=1000
Target1=Attack
Target2=Attack
Target3=Attack
Target4=Attack
TargetL=Attack
TargetR=Attack


[Loot]
SalvageOrSell=Salvage
Set=1
Leg=1
Gem=1
Rare=1
Blue=1
White=1
LootTime=5000
LootDelay=0000


[LootColor]
Set=0x00FF00
Leg=0xFF8000
Gem=0x99BBFF
Rare=0xFFFF00
Blue=0x6969FF
White=0xFFFFFF


[Stash]
Stash=1,2,3,4
BackpackDelay=1000


[KeyBindings]
KeyForceMove=V,56
KeyForceStand=SHIFT,10


;KeyCodes
;08 BACKSPACE key
;09 TAB key
;0C CLEAR key
;0D ENTER key
;10 SHIFT key
;11 CTRL key
;12 ALT key
;13 PAUSE key
;14 CAPS LOCK key
;1B ESC key
;20 SPACEBAR
;21 PAGE UP key
;22 PAGE DOWN key
;23 END key
;24 HOME key
;25 LEFT ARROW key
;26 UP ARROW key
;27 RIGHT ARROW key
;28 DOWN ARROW key
;29 SELECT key
;2A PRINT key
;2B EXECUTE key
;2C PRINT SCREEN key
;2D INS key
;2E DEL key
;30 0 key
;31 1 key
;32 2 key
;33 3 key
;34 4 key
;35 5 key
;36 6 key
;37 7 key
;38 8 key
;39 9 key
;41 A key
;42 B key
;43 C key
;44 D key
;45 E key
;46 F key
;47 G key
;48 H key
;49 I key
;4A J key
;4B K key
;4C L key
;4D M key
;4E N key
;4F O key
;50 P key
;51 Q key
;52 R key
;53 S key
;54 T key
;55 U key
;56 V key
;57 W key
;58 X key
;59 Y key
;5A Z key
;5B Left Windows key
;5C Right Windows key
;60 Numeric keypad 0 key
;61 Numeric keypad 1 key
;62 Numeric keypad 2 key
;63 Numeric keypad 3 key
;64 Numeric keypad 4 key
;65 Numeric keypad 5 key
;66 Numeric keypad 6 key
;67 Numeric keypad 7 key
;68 Numeric keypad 8 key
;69 Numeric keypad 9 key
;6A Multiply key
;6B Add key
;6C Separator key
;6D Subtract key
;6E Decimal key
;6F Divide key
;70 F1 key
;71 F2 key
;72 F3 key
;73 F4 key
;74 F5 key
;75 F6 key
;76 F7 key
;77 F8 key
;78 F9 key
;79 F10 key
;7A F11 key
;7B F12 key
;BA ;
;BB =
;BC ,
;BD -
;BE .
;BF /
;C0 `
;DB [
;DC \
;DD ]

[Blitzzzz]

I'll try setting the last seen timeout to 500 & maxdistance to 250 Will observe over a period of a few hours later on and let you know. Thanks!

[burgaud]

BTW. Also transmog your gears and apply dull color dyes on them too. I have all my toons and gears dyed black and transmog to the very first item.

You got no idea how some items' color effects could fool pixelsearch thinking they are loots on the ground.

LootDelay=0000 can be a problem.
Basically, you are telling bot to immediately LOOT when things are still not stabilized. ie, some of your skill effects are still flying off and honestly, Crusaders got the most if not ALL of the skill colors looking like loots! Fist of Heaven, Consecrate to name a few.

these would be a good setting but if you are using those troublesome skills. you may need to increase LootDelay as well.
LootTime=4000
LootDelay=3000

[dex301]

For some reason the bot won't start diablo 3 after it opens battle.net. I created the play.png and tested it. It shows up on the pngtester. It just closes then reopens. Help?

Here is what the log file says

6/21/2014 11:34:51 PM Stabilizing Battle.net
6/21/2014 11:40:11 PM Start : BK Ghom Bot v20140620
6/21/2014 11:40:11 PM MaxRunTime : 3.0H,3.0H
6/21/2014 11:40:11 PM RestTime : 10.0M,10.0M
6/21/2014 11:40:11 PM Battle.net : C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe
6/21/2014 11:40:11 PM FightPosition : 1282,100
6/21/2014 11:40:11 PM KeyForceToMove : V,56
6/21/2014 11:40:11 PM KeyForceToStand: SHIFT,10
6/21/2014 11:40:23 PM Reset

[burgaud]

It just closes then reopens. Help?

What does it closes? Battle.net Launcher?

Do you have D3 as Diablo III? or did you rename it to something else?



This eludes me:
Part1

6/21/2014 11:34:51 PM Stabilizing Battle.net

Part2

6/21/2014 11:40:11 PM Start : BK Ghom Bot v20140620
6/21/2014 11:40:11 PM MaxRunTime : 3.0H,3.0H
6/21/2014 11:40:11 PM RestTime : 10.0M,10.0M
6/21/2014 11:40:11 PM Battle.net : C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe
6/21/2014 11:40:11 PM FightPosition : 1282,100
6/21/2014 11:40:11 PM KeyForceToMove : V,56
6/21/2014 11:40:11 PM KeyForceToStand: SHIFT,10

Part3

6/21/2014 11:40:23 PM Reset

The sequence of events does not correlate with each other.
#1. How come the time difference between Part1 and Part2 is >5 minutes? The most should be 60 seconds of time difference for the next log entry.
#2. Part2 is not the next sequence after Part1. You omitted something in between.
#3. Part3 is not the next sequence after Part2.
There are only 2 possible ways for a Reset to occur:
First, when there are Too many Errors encountered. This will show up before a Reset. However, this is not possible to happen immediately after a Part2 - the most is 3 minutes after a Part2 (aka LoadConfig) for a Too many Errors encountered log entry to occur.
Or Second, When "Diablo III.exe" is not detected. However, THAT should not appear based on the sequence of events you posted.

Conclusion: Please post a more complete log.txt between 11:30:00 to 11:45:00 all 15 minutes so i can know what really happened to you.


#2.

[dex301]

It just repeats. Here is the entire. It will open battle.net launcher, sits there for about a minute then closes then repeat. I even tried changing my monitor resolution to 1920x1080 but still have the same problem.

It's Diablo III. I never changed the name.



6/21/2014 11:33:31 PM Start : BK Ghom Bot v20140620
6/21/2014 11:33:31 PM MaxRunTime : 3.0H,3.0H
6/21/2014 11:33:31 PM RestTime : 10.0M,10.0M
6/21/2014 11:33:31 PM Battle.net : C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe
6/21/2014 11:33:31 PM FightPosition : 1282,100
6/21/2014 11:33:31 PM KeyForceToMove : V,56
6/21/2014 11:33:31 PM KeyForceToStand: SHIFT,10
6/21/2014 11:33:31 PM Reset
6/21/2014 11:33:41 PM Stabilizing Battle.net
6/21/2014 11:34:41 PM Error: Battle.net unresponsive
6/21/2014 11:34:41 PM Reset
6/21/2014 11:34:51 PM Stabilizing Battle.net
6/21/2014 11:40:11 PM Start : BK Ghom Bot v20140620
6/21/2014 11:40:11 PM MaxRunTime : 3.0H,3.0H
6/21/2014 11:40:11 PM RestTime : 10.0M,10.0M
6/21/2014 11:40:11 PM Battle.net : C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe
6/21/2014 11:40:11 PM FightPosition : 1282,100
6/21/2014 11:40:11 PM KeyForceToMove : V,56
6/21/2014 11:40:11 PM KeyForceToStand: SHIFT,10
6/21/2014 11:40:23 PM Reset
6/21/2014 11:40:33 PM Stabilizing Battle.net
6/21/2014 11:41:33 PM Error: Battle.net unresponsive
6/21/2014 11:41:33 PM Reset
6/21/2014 11:41:43 PM Stabilizing Battle.net
6/21/2014 11:45:59 PM Start : BK Ghom Bot v20140620
6/21/2014 11:45:59 PM MaxRunTime : 3.0H,3.0H
6/21/2014 11:45:59 PM RestTime : 10.0M,10.0M
6/21/2014 11:45:59 PM Battle.net : C:\Program Files (x86)\Battle.net\Battle.net Launcher.exe
6/21/2014 11:45:59 PM FightPosition : 1282,100
6/21/2014 11:45:59 PM KeyForceToMove : V,56
6/21/2014 11:45:59 PM KeyForceToStand: SHIFT,10
6/21/2014 11:45:59 PM Reset
6/21/2014 11:46:09 PM Stabilizing Battle.net
6/21/2014 11:47:09 PM Error: Battle.net unresponsive
6/21/2014 11:47:09 PM Reset
6/21/2014 11:47:19 PM Stabilizing Battle.net
6/21/2014 11:55:57 PM Start : BK Ghom Bot v20140620
6/21/2014 11:55:57 PM MaxRunTime : 3.0H,3.0H
6/21/2014 11:55:57 PM RestTime : 10.0M,10.0M
6/21/2014 11:55:57 PM Battle.net : C:\Program Files (x86)\Diablo III\Diablo III Launcher.exe
6/21/2014 11:55:57 PM FightPosition : 1282,100
6/21/2014 11:55:57 PM KeyForceToMove : V,56
6/21/2014 11:55:57 PM KeyForceToStand: SHIFT,10
6/21/2014 11:55:57 PM Reset
6/21/2014 11:56:11 PM Stabilizing Battle.net

[dex301]

I got it to work, for some reason the tool tip for autoit was in the way. When i maximize the battle.net launcher screen or move it, it finds it just fine.

Thanks for the reply and help. Is there a wizard build that works the best for this bot?

[burgaud]

I noticed you updated the bot, is it more efficient than before or just made it easier to use?

Oh forgot to add this: New version will not use a skill that is greyed (not enough resources).

This should give you more DPS, ie:
Without resources and you used HOTA, you will be doing normal attack instead: normal damage, no fury regen.
With new version, Bot will instead use your other attack skills say Frenzy. That should give you more DPS, and regen fury at the same time.

This should give you "Less Guess Work" trying to figure out the optimal timeout between resource spenders.

This is very evident with Akarat Champion Crusaders or Sith DH. When in these mode, you regen resources faster and therefore you want to attack with resource spenders more often than when not in these modes.

[ir3gr3t]

Other than the difference in the PNG, it requires recognizing the name of the map in English:

If you want to make it work in Russian version, please post these screen shots:
#1. Open your backpack, put an Account Bound item in your backpack (Leg, Set, Crafted Rare). Then point mouse on top if this item, item tooltip will pop up, take screen shot.
#2. goto Breached Keep Level 3, take screen shot
#3. go down to Larder, take screen shot
I need these screen shots in PNG, unmodifed resolution, without your name.





PAUSE - to pause
HOME - to reload config
END - to exit

Thanks. Do you guys have a beginner wiz build for this run? i have a new level 70 wiz. i want to farm a specific item for my wiz but i dont know which build is efficient. so far most of my gear are from wd which is my main. i have around 600k dps and 11m toughness. i cant kill ghom on my current build and he cant kill me either. its frustrating, does anyone here use wiz for this run?

[burgaud]

@ir3gr3t

Here is what I use just now on T4 now

[Fight]
MaxDuration=200000
WaitBeforeMoving=500
FightPosition=1292,280
FightPositionTimer=750
MaxDistance=900
ForceToStand=1
LastSeenTimeOut=1000

[Skills]
TimeOut1=60000
TimeOut2=60000
TimeOut3=60000
TimeOut4=1000
TimeOutL=1000
TimeOutR=0
Target1=Attack
Target2=Attack
Target3=Attack
Target4=Attack
TargetL=Attack
TargetR=Attack

This Build uses EB and Meteor as the main resource Spenders. Depending on your gear's Elemental Bonus, Choose the more appropriate runes to benefit these two skills. A fast weapon is best to bring up Arcane Dynamo (Huge +60% DPS Boost) before casting a resource spender.

Another build is MM Conflag, requiring Mirror Ball, Magic Missile, and the +Hydra Wand. It is also a Fire Build. Can down Ghom much faster than the above.