HB ARCHIVES: DungeonBuddy--DO NOT DELETE

New confirmed ;

5) upper spire glitch leaving - bots never complete upper spire, they do 4/5 of the seals, then sit at the end for 20 seconds, then the tank leaves. Even if you get past that part (manually ofc) then you also have to worry about the ramp AFTER 2nd boss, because the tank has no problem going up that ramp, but all the other bots got stuck there at the bottom. Had to manually stop the bot, then start it again after I had walked 15 yards up the ramp away from the rubble debris. Upper black rock pretty much cant be afked either atm .

 

Tank is getting stuck right at the very beginning of Train Depot. Tries to run to hotspot outside of the train. Happens on multiple toons all using different routines.

View attachment 984 2016-08-07 18.45.txt

 

if u read above i already reported this in my thread. found 5 glitches so far.

 

Adding the log is pretty much the most helpful thing you can do for devs. I would suggest going back through all 5 and isolating the event in your logs to assist with troubleshooting.

 

ive got 5 sets of logs, should i really upload them all for every incident? Genuinely I wouldn't mind knowing.

 

As long as they pertain to what you were doing, then yes.

 

Trying to do Proving Grounds, done silver manually and now trying for gold via paid CC (KingWoW). Getting message; "Bot stopping! Reason: All scripted trials are complete" even with singular CC.

 

When I do raids and we wipe, it won't release and run back :/.

 

Whats wrong with DB? At dungeon start its idle 30-40 sec, its rly bad =\

 

I wouldnt say you need to upload every one as long as you can identify that the issue appears in one of them. Like on the log I isolated the hotspot failure. But logs always help... and even if it looks like a huge mess to us the devs can pick out exactly what they need from it.

And I wasnt trying to be a dick telling you to post the logs, they genuinely do help resolve issues faster.

 

the issue does NOT appear in any of them, aside from the Train issue you posted already. The other issues are not logging anything, they just stand still and dont move.

 

Hello!

At the dungeon star bot idle 20sec-1min. Its rly bad.

I think this is cause

[08:19:49.344 N] (Singular) info: 22 seconds since Dungeonbuddy BotBase last called Singular
[08:24:14.917 N] (Singular) (Singular) info: 74.2 seconds since BotBase last called Singular

View attachment 2560 2016-08-09 11.12.txt

 

2 thing: One; you are downloading meshes at that time. Happens only when you first enter a dungeon, for the first time that is.
Second: DB waits for the LFG timer to run out. This can take anywhere from 5 to 35 seconds. I do not know why this has changed.

 

anyone else got the issue during dungeoning if the bot wants to equip new gained items (AutoEquip) - it stucks by the message "this item cant be traded after equiping anymore" ... is there any plugin available who clicks on yes? or addon? thanks

 

Yes, that issue is still there. You need an addon to click YES for now, or a plugin.. it might still be around somewhere.

 

Yeah I have modified some wow addon to support this,
just copy it to the warcraft interface addons folder - should be activated by default, including some other confirmations.
- problem solved-

 

Auchindoun: When the Vigilant Kaathar spawns Holy Shield, the bot starts throwing out a bunch of errors and the group dies.

 

I notice that the passing of the leader causes a delay in the following of the tank, and sometimes even causes my character to not move because the group has moved so far ahead. Is there a way to disable the passing of the leader?

 

Anyone from the team or whoever working to fix DungeonBuddy? WoD dungeons are terrible, just terrible...

 

unfortunately who solved the problems with the dungeons was Zonehunter user, the more it is no longer active and hence we are left without correcting anything in dungeons!