Date of Test: 4.2.2013 Dungeon Name: Role Used: (Tank, Healer, etc) Healer DUNGEON STATUS (below): Fully AFKable? [ ] Minor Issues? [ ] Major Issues? [ ] Issue Explanation: a)Where (add a screenshot if possible): b)What bot does or does not do?: Joined Dungeon, and standed still then. Did nothing in the Dungeon c)Penalty (death? stuck? Wipe? Kick?): Kick d)Suggested solution (If any): Help Log: View attachment 4612 2013-02-04 18.21.txt
The botbase itself is updated with the new version of HB. The dungeon scripts auto update when highvoltz makes a new version available (unless you've disabled that feature).
Summary: Move here and there .. but no kill boss and trash Class: Warrior 89lvl CustomClass: Singular Role: DPS Queue Type: Random Queue Party Mode: Off Dungeon: Shadow Pan Monestery (Normal)
a quick question h4mi1, have you done the quest that you pick up when entering the dungeon ? Im having similar problems. Im running with a 5 a new man bot team, and they are picking up the quest at the start and then start to run towards the last boss pulling the whole dungeon with em. If I steer them to the first boss they just stand around. Not fighting, not healing, not reacting to getting beat on. I will try to see if I can disable this in the dungeonscript. Edit: to clarify, it's the leader that runs off, the followers just follow and does nothing, that's why I thought it was similar to your situation.
Hey, Highvolts have you started your 5 man team and how is it going? - - - Updated - - - Hey, Highvolts have you started your 5 man team and how is it going?
Hey highvolts...for sure u made a very nice toy working well so far ^^ My set is 1)DK running tank (choice Farm and the script needed) 2)PALA DPS (choice none) following and killing 3)PALA HEAL (choice none) following and healing everyone. Everything run smooth killing boss and the moving to portal at the end. Then tank (leader) wait for everyone leaving instance to reset...done..and reenter. The only problem is the 2 and 3 dont follow !! i have to manually enter them. Is there something i make badly or i should know ? Thax for ur answer . (or anyone)
Is it just me.. or do we miss a script.. for Assault on Zan'vess horde version.. as horde version is dungeon ID 537 as for alliance it is 593. But when i change it it still can't find it.. auto update is off and with update on.. yep back to alliance version.. Tried it als custome script also changed the gyrochopper name and ID to Kor;kron gunship ... still no go (also did the profile, and that one he does load... \\ What am i missing or doing wrong... ? Update... Found another one... Script+profile: Theramore's Fall DungeonID 566 in profile... while we as HORDE enter it's 567 Assault on Zan'vess DungeonID 597 in profile... while we as HORDE enter it's 537 Assault on Zan'vess works when you edit the Script and profile on the fly (while DB is running) although you need to manually enter the gunships. Theramore's Fall works when you edit the Script and profile on the fly (while DB is running).. although i can't leave my group alone as i don't know when they hang again.. worked perfect with a 3 man alliance group. It seems to be HORDE only problem.. don't know if Blizzard did and dungeon ID update with their last hot fix.
I have a problem with this bot. I've been trying to use it to farm VP, and it only queues me to dungeons, it moves away from fire and stuff, but the bot does not follow a path in the dungeon, does not attack, etc. I don't know what to do.
This has been on my nerves for a while now, Why is it that most of the time the bot says " You have not selected a role " yet I have and it will not que up, it happens on all my toons.
If I remember correctly you need to select the role before you start up HB. Only once though and then it will remember your choice. - - - Updated - - - It seems like something bad has happended to Shado-Pan Monastary. Or can anyone else run that dungeon now ? I thought it was just my new bot team that got into trouble because they hadn't done the quest. But today I tried it with my old team and they do the same thing. Running straigth in, ignoring all mobs, pulling the whole thing, running up to Gu Cloudstrike. They wont fight heal or do anything, when they get to the first boss, they will try to dodge the bads on the ground, but still not fight or heal. I would post a log, but for some reason you have started to put char names into the logs, so I won't
I have been watching the bot a lot and I see that people take shortcuts while the bot still runs around and pulls mobs too get up too them. We cant fix this?
Been working great thus far. Just Shado-pan won't attack. Wish there was a way to grindbot and dungeonbuddy together. ha
It will go to pick up quests but won't actually click on them to pick them up. If I click on the quest manually it will accept it.
My next "brilliant mistake" left the screen for a few hours with my group of bots running dungeons. Log me out was set for 10 deaths on healer to log out thinking this would stop the group. Unfortunately log me our setting was also set for after current instance... So I come back to the following. 1 DPS dc one tank doing nothing, 1 dps hearthed. 1 dps and a healer stuck in some kind of chain pulling death loop. No I hadn't updated HB yet. Additionally, for some reason the leader filled a random DPS - so I had a visitor to watch all this nonsense in the palace dungeon that db can't do properly atm. The result? 143 consecutive deaths and a trail of hundreds of skeletons at the entrance to the dungeon. I'm guess several accounts are flagged / reported. Isn't 143 deaths over 2 hours a huge red flag?
sounds like it would be flagged / reported you was doing this with other random people? I would never go afk with in a dungeon while you are botting with randoms.
That's the thing, no I don't go with randoms. It's as if the one that got dc'd left a gap and a random DPS joined. I didn't think DB would do that unless someone manually left group. I have had some one join up unintentionally b4 but immediately downed my 5 bots. Only reason that happened though was because I left group manually.
@razer I got the no roles selected error when I have selected no scenarios / dungeons at all in the bot config for DB. Several releases ago there was a post here about choosing show all dungeons, selecting all, closing, reopening then selecting just the ones you wanted queue for. Not sure if that will clear the error or not.
