Best ghom bot!

[Samavayo]

I am experiencing this as well. No solution yet?
Because of this, I have to swap some skills: Entangle to Hungering, and therefore, Cull of the Weak to Steady Shot.
Ghom usually dies before counter goes down to 12; but if this problem occurs, he dies by 5 or even 3.

Sadly, with this problem, I am only doing T2 as instead of T3 to be safe. And yet even with just T2, I nearly died if not for my Beckin Sail cloak that gives me a few sec of smoke screen when HP drop below 25%.

solution:

edit line

[settings]
timeyouneedtogettobossorposition=

set it to 2300 and it will work properly (timeyouneedtogettobossorposition=2300)

[SnowChild]

guys if you want to run your bot even when getting d/cs I made a bot myself that helps for that: (until richardptt implements it in his own bot)

http://www.ownedcore.com/forums/diab...bot-64bit.html (D3 reconnect bot (64bit))

[burgaud]

Right bot is running pretty flawlessly, have encountered a problem though when game loading fails, the bot gets stuck in a loop. It opens quests scrolls to correct location but because the quest is already open with the breached keep highlighted it is unable to find it and cant start the game. it waits, escapes to main menu then does it again.

End up with this



I think this could be fixed by adding in an additional search before to current ones to see if the quest is already open.

Attachment 17931

Edit: this error occured on run 104. to reproduce you can simply set the quest to kill ghom save and exit to menu, then run the bot.

I am getting this error as well.
Any solution already?

[burgaud]

please delete

[hjcn]

I am using a Crusader with Demon Hunter settings and the bot works well up to the end of combat.

After it goes through the combat cycles, it log out of the game without teleporting (Ghom is dead, the crusader is standing on top of loot)

In the config I set it to loot legs, sets, yellows, salvage, teleport before logging out. But no matter what I change, it won't pick up any loot after Ghom is dead. It just logs out.

In the error log, it never registers that Ghom dies. (0/3)

##############################################
### ###
###------------ SUMARY -----------------###
### ###
### Total Runs - 3 ###
### Total Success » Legendaries » - 0 of 0 ###
### Total Success » Sets » - 0 of 0 ###
### Total Success Rares - 0 ###
### Total Success Magics - 0 ###
### Total Success Gems - 0 ###
### ###
###---------- Stashing -----------------###
### ###
### Total Stash times - 0 ###
### Total Stash set - 0 ###
### Total Stash leg - 0 ###
### ###
### ###
###------------ !!Timer!! -----------------###
### ###
### Total time bot worked: 04 Minutes, And killed Ghom [0] Times of All [3] Runs
### Average Run time : 125.5 Seconds ###
### ###
###------------ ERRORS -----------------###
### ###
### Total Error Nº 1, Times Failed: [ 0 ] This Error Happens when did not Loading the game
### Total Error Nº 2, Times Failed: [ 2 ] This Error Happens when the bot didnt kill boss! Choose a easier torment or add more time to the fight
### Total Error Nº 3, Times Failed: [ 0 ] This Error Happens When it Fails to Enter Portal
### Total Error Nº 4, Times Failed: [ 0 ] This Error Happens When lagged and was in game and looking for Resume button
### Total Error Nº 5, Times Failed: [ 0 ] This Error Happens When pressing M failed or clicking to teleport failed
### ###
###------------- Class -----------------###
### ###
### Runned The Bot As a DEMON HUNTER ###
### ###
##############################################

How would I fix this? Thanks!

[burntangel]

I had the same problem in the beginning Burgaud, glad you got it working. I think it's confusing because it says run the bot, and you can't run the bot until you have both png files in the folder. Having 2 wrong png files in the beginning would maybe help that process? And then have the tutorial explain how to replace them properly by printscreening when the bot freezes each time, and with your point added, ensuring no one makes the mistake of grabbing the jpgs out of the Diablo folder to create the pngs.

[burgaud]

Problems I encounter so far:
#1. Sometimes, after killing ghom and going back to the menu page, the Quest List is not updated and The Breached Keep is highlighted. This prevents bot from continuing because it requires that the next quest be highlighted. A simple fix is to simply "go ahead", or first highlight a later quest (kill azmodan), then immediately scroll back to The Breached Keep which will then be darked.

This particular problem can also occur when joining a game but timed out. In this manner, the quest list is now highlighted to The Breached Keep which therefore prevents bot from continuing further.

Bot is completely stuck and this can last till i reset it. I believe this is a major problem need fixing badly.

#2. perhaps experienced by hjcn, after killing Ghom, bot simply exits the game thinking it did not kill Ghom. I am using DH, and is on the spot designated for DH (right side), and when Ghom is killed, Ghom is near the Left Bottom Post which is about half a screen away yet completely visible from DH. Ghom is too far away for bot to recognize? This has occurred to me 3 times in a row right now. I am still getting the EXP and Gold, but not the loot in this case.

[stolentoys]

Hey richardptt

Just wanted to let you know i had the boss loot a Set piece Helm and i also had another legendary in my inventory when the bot went to stash it stashed the legendary but sold my set helm.

I have a few screenshots if you need to see anything to make adjustments or anything.

[hjcn]

@burguad I failed to mention the bot is also standing on top of the loot. I think that is within loot range, but the bot didn't know that it had indeed killed Ghom and logs out instead? Not sure if that has happened to you as well.

[cheatersprosper]

Does anyone have any suggestions for settings on VMware so that this won't crash my whole computer by leaving it on overnight? Or is it a Diablo optimization thing?

[Woink]

Gaarrhhhh! I really want to get this up and running, I'd love it if someone that knew how these kind of things work would help a fellow man out. Maybe over skype or something. I've tried asking for a solution here in the thread but that did not work out very well so if there's anyone willing to help me please throw me a PM!

Thanks in advance.
Woink

[SnowChild]

Gaarrhhhh! I really want to get this up and running, I'd love it if someone that knew how these kind of things work would help a fellow man out. Maybe over skype or something. I've tried asking for a solution here in the thread but that did not work out very well so if there's anyone willing to help me please throw me a PM!

Thanks in advance.
Woink

Is there any way you can describe your problem better? can't you run it at all or does it stop at some point? the more details, the easier it is to help you.

[Woink]

Is there any way you can describe your problem better? can't you run it at all or does it stop at some point? the more details, the easier it is to help you.

Okay here's the best I can do to describe my problem.

I've created my .pngs exactly as the tutorial told me to. I edit the config to fit my needs. I start the bot and it runs like a charm, often for about 30-40 games without any problems other than it stashing off-hands thinking its legendaries, this doesn't bother me to much tho. But then something wierd happends and I have no clue what it is. It just stops picking the quest and giving me that error (At the quest selection menu)

[burntangel]

Okay here's the best I can do to describe my problem.

I've created my .pngs exactly as the tutorial told me to. I edit the config to fit my needs. I start the bot and it runs like a charm, often for about 30-40 games without any problems other than it stashing off-hands thinking its legendaries, this doesn't bother me to much tho. But then something wierd happends and I have no clue what it is. It just stops picking the quest and giving me that error (At the quest selection menu)

Woink, that explanation is consistent with the Ghomquest.png not being correct. Try setting it to T6, and force yourself to die and see if it ends up at that error right away. If that's the case, then it is definitely that png and you need to screen shot when the error occurs and rebuild from there.

[burgaud]

Okay here's the best I can do to describe my problem.

I've created my .pngs exactly as the tutorial told me to. I edit the config to fit my needs. I start the bot and it runs like a charm, often for about 30-40 games without any problems other than it stashing off-hands thinking its legendaries, this doesn't bother me to much tho. But then something wierd happends and I have no clue what it is. It just stops picking the quest and giving me that error (At the quest selection menu)

I do not think this is a PNG file error.
To Wit: if it is, then you wont be able to run 30-40 games.

I believe the problem is that, either due to lag, or death, or perhaps a server glitch, when the game goes to "Menu Selection", the quest log ramains that you are still doing "The Breached Keep" quest and thus, the bot does not know how to proceed because it firstly requires that the game is already in the "Tremors in the Stone" quest.

There is no solution to this problem unfortunately. It is hard coded into the bot to first check "The Breached Keep" quest is dark, then and only then will it pick "The Breached Keep" quest from the list and select "Kill Ghom" subquest.

Can you please verify, confirm your case, by taking a screen shot of the Quest List when your error is occuring?