HB ARCHIVES: DungeonBuddy--DO NOT DELETE

[chinajade]

Finally, the pathing seems to be continually off when trying to run up the stairs in the second wing after the Twin Ogron encounter. I routinely get stuck at the bottom of the steps unless I pause and run up myself.

Thanks,
FJ

Also in imperator's room it seems to prioritise a set kill order regardless of marks.

Once again, we are unable to chase issues such as these without the full log that captures the event.

cheers,
chinajade

 

[chinajade]

Since the last update, my Dungeoneers are hearthing to their garrison and getting stuck in the Dwarven Bunker when trying to repair. Any way to solve this?

Hi, Kaelhoel,

Navigation inside the garrison is highly goobered at the moment. Buildings are 'dynamic' is the best way to describe it, and the current Honorbuddy mesh system does not adequately address the problem. But, the problem is being worked.

The only work-around available to you is to turn off DungeonBuddy's "Hearth to sell/repair" option.

cheers,
chinajade

 

[chinajade]

Thanks for investigating my issue. Tried with clean HB and the problem is still present. Dungeonbuddy on all 5 accounts, 1 leader, 4 followers. Queuing Normal WOD dungeons. It goes smooth for all dungeons except shadow burial grounds which turn Queue from "random" to "specific" when it ends

Edit: I was monitoring BSG a bit... actually the switch from random to specific happens not only at the end of the dungeon, but also somewhere in the middle of the run

It goes like:

enter burial ground from random queue
kill a boss
switch to specific
(I manually switched to queue random wod normal dungeons)
killed 2nd and 3rd boss
killed last boss
I checked DB config and dungeonbuddy switched to specific normal dungeon again

Hi, Tsatsa, and thanks for the follow-up,

HB-2099 ("Dungeonbuddy has "no valid dungeon to run" after completing Shadowmoon Burial Grounds") has been opened against this issue.

cheers,
chinajade

 

[TaeTae]

My 5 dungeon running characters in party mode are getting constantly stuck. Well they aren't even getting stuck, they just stop doing anything. They don't do anything at all. At random points in each dungeon - low level ones atm, only Deadmines and SFK, they just stop at random points and sit about until I reappear to leave and restart the bot, then it happens 5 minutes later.

Frustrating I'm sure you find.

There are no errors appearing in HB, I wonder whether this is a HB update issue and you need to update the scripts?

 

[chinajade]

My 5 dungeon running characters in party mode are getting constantly stuck. Well they aren't even getting stuck, they just stop doing anything. They don't do anything at all. At random points in each dungeon - low level ones atm, only Deadmines and SFK, they just stop at random points and sit about until I reappear to leave and restart the bot, then it happens 5 minutes later.

Frustrating I'm sure you find.

There are no errors appearing in HB, I wonder whether this is a HB update issue and you need to update the scripts?

Hi, Taetae,

We've no chance to investigate the issue without a log capturing the problem. Without a log, we can only guess. As a guess, we'll suggest your Honorbuddy installation is damaged and you'll need to do a 'clean install':

Honorbuddy:HelpDesk:"Clean installing" Honorbuddy​

cheers,
chinajade

 

[botur]

Hi, Tsatsa, and thanks for the log.

Sadly, the log does not illustrate the problem you describe.

DungeonBuddy will not change your Dungeon-type choices. Our guess is you've got a plugin or something else interfering with proper operation. Please try replicating the problem with a 'clean install' of Honorbuddy (no third-party plugins--from the store or local install), and see if the problem still exists.

cheers,
chinajade


[size=-2]Ref: Tsatsa's original post w/log[/size]

hi Chinajade sorry but u wrong same thing constantly hepens 2 me 2 difrent PC both fresh instal 0 plugins, scripts, rutines - pure HB and always after Shadowmoon Burial Grounds bot just change from random 2 specific (empty selection) and stops
im unable 2 run random WOD's couse of this and..

second thing: few posts back u answered that singular movment set 2 auto is responsible for tank turnig its back 2 boss again: no it is not (at least not in this case). in most WOD dungeons no metter what "movment settings "(tested all posible settings) always on same fights tank and some mele dps stop fighting and they turn back 2 boss usualy after avoiding aoe dmg . big example is Grimrail Depot dungeon when (2nd or 3rd dont remember ) boss apear in one cart, fight for few % of hes hp and then run away to apear again later in the dungeon. at that fight my full mele dps team on normal with 633-638 gear die very often cous after some of boss attacs they just turn its back to boss and stand still, only ever winning if healer have luck in keeping tank alive . second example Skyreach last boss after beam attack leavs aoe on ground tank turn back and run and then dont start attack again only thing that helps is when one of adds apear then my team start 2 fight again usualy until next aoe
ther r MENY more examples of that type of movment in almost every WOD dungeon (mop on same settings runs perfect !!! )
this is very anoing couse only becouse of this one type of error my team need 2 be in lfr gear 2 even have chance 2 finish all wod normals im not even trying random hc at this point


p.s. sorry no logs i use the downtime 2 do full fresh instal on both pc but u have logs from other ppl post with same problems i just confirm what thay claim (at least im my case - same thing )

 

[chinajade]

hi Chinajade sorry but u wrong same thing constantly hepens 2 me 2 difrent PC both fresh instal 0 plugins, scripts, rutines - pure HB and always after Shadowmoon Burial Grounds bot just change from random 2 specific (empty selection) and stops
im unable 2 run random WOD's couse of this and..

Hi, Botur,

In this post, we clearly state this issue has already been captured.

second thing: few posts back u answered that singular movment set 2 auto is responsible for tank turnig its back 2 boss again: no it is not (at least not in this case). in most WOD dungeons no metter what "movment settings "(tested all posible settings) always on same fights tank and some mele dps stop fighting and they turn back 2 boss usualy after avoiding aoe dmg . big example is Grimrail Depot dungeon when (2nd or 3rd dont remember ) boss apear in one cart, fight for few % of hes hp and then run away to apear again later in the dungeon. at that fight my full mele dps team on normal with 633-638 gear die very often cous after some of boss attacs they just turn its back to boss and stand still, only ever winning if healer have luck in keeping tank alive . second example Skyreach last boss after beam attack leavs aoe on ground tank turn back and run and then dont start attack again only thing that helps is when one of adds apear then my team start 2 fight again usualy until next aoe
ther r MENY more examples of that type of movment in almost every WOD dungeon (mop on same settings runs perfect !!! )
this is very anoing couse only becouse of this one type of error my team need 2 be in lfr gear 2 even have chance 2 finish all wod normals im not even trying random hc at this point

p.s. sorry no logs i use the downtime 2 do full fresh instal on both pc but u have logs from other ppl post with same problems i just confirm what thay claim (at least im my case - same thing )

We run Grimrail Depot almost every day in low gear (630-ish) on normal AND heroic, and have never experienced the issues you describe. This is most likely a problem with your installation or machine. Only a log will help us isolate the problem.

cheers,
chinajade

 

[botur]

Hi, Botur,

In this post, we clearly state this issue has already been captured.




We run Grimrail Depot almost every day in low gear (630-ish) on normal AND heroic, and have never experienced the issues you describe. This is most likely a problem with your installation or machine. Only a log will help us isolate the problem.

cheers,
chinajade

1st sorry did not read the last page ( im after whole night reintaling )

2nd ill try 2 deliver logs if proplem reaper in new version & instal
- did u run on "mele" only team, maybe here is my problem ?


ok i tested new relese even from difrent pc just 2 be on the save side no old settings linger .
i instaled HB from install not from zip i
- disable movment in singular
- changed loot from boss only
-set kill optional bosses
-set movment in dungeon buddy setings
-set party neames
and thats it i think

and still same problem tank dont fight .Nitrogg on first part of encounter ... i mean for some parts it das but most of the time tank "assfacing" boss insted of fighting so nothing changed with fresh instal and i didnt put my usual settings this time (my settings woks great in pandaria )

View attachment 5520 2015-03-25 14.54.txt

ps while i was writing this i put my bot on skyreach and on last boss same ting "assfacing" all the time almost all tank das is fighting ads and when boss is alone he ran from it or satnd with bos behind him

 

[Maelnum]

Figured I might help you out regarding:
HB-2096("DungeonBuddy: Shado Pan Monastery (heroic): Rogue always get stuck at Sealed Chamber door")

This happens because rogues choose Cloak and Dagger as Lvl60 talent by default. They use it on serpent (first boss), get behind him and are stuck near end of the instance until rest of the group gets there.
Solution: take a different lvl60 talent or I suppose you could prevent singular from using it on that fight from within the dungeon script.

 

[chinajade]

Figured I might help you out regarding:
HB-2096("DungeonBuddy: Shado Pan Monastery (heroic): Rogue always get stuck at Sealed Chamber door")

This happens because rogues choose Cloak and Dagger as Lvl60 talent by default. They use it on serpent (first boss), get behind him and are stuck near end of the instance until rest of the group gets there.
Solution: take a different lvl60 talent or I suppose you could prevent singular from using it on that fight from within the dungeon script.

Thank you, Maelnum!

We've added your insight to HB-2096.

cheers,
chinajade

 

[innomina]

Is there a schedule for more LFR's coming out?

 

[chinajade]

Is there a schedule for more LFR's coming out?

Hi, Innomina,

You can track the progress of bugs and feature requests on the Currently Known Issues list you can find in the latest release thread. We do not give out schedules.

cheers,
chinajade

 

[chinajade]

1st sorry did not read the last page ( im after whole night reintaling )

2nd ill try 2 deliver logs if proplem reaper in new version & instal
- did u run on "mele" only team, maybe here is my problem ?


ok i tested new relese even from difrent pc just 2 be on the save side no old settings linger .
i instaled HB from install not from zip i
- disable movment in singular
- changed loot from boss only
-set kill optional bosses
-set movment in dungeon buddy setings
-set party neames
and thats it i think

and still same problem tank dont fight .Nitrogg on first part of encounter ... i mean for some parts it das but most of the time tank "assfacing" boss insted of fighting so nothing changed with fresh instal and i didnt put my usual settings this time (my settings woks great in pandaria )

View attachment 173018

ps while i was writing this i put my bot on skyreach and on last boss same ting "assfacing" all the time almost all tank das is fighting ads and when boss is alone he ran from it or satnd with bos behind him

Hi again, Botur, and MANY thanks for that log.

The log does indeed demonstrate the problem. We've opened HB-2126("Grimrail Depot: DungeonBuddy appears to be disabling 'facing' for melee toons at inappropriate times") against this issue.

The problem will take a while to investigate. There are immediately three different places it could lie: DungeonBuddy, Singular, or the HB CombatRoutineCapability API that allows DungeonBuddy and the CombatRoutine to coordinate.

cheers & thanks again for the follow-up,
chinajade


[size=-2]Ref: Botur's problem report w/log[/size]

 

[Tarathiel2]

DungeonBuddy is having trouble repairing in the Garrison. It seems to constantly look in an endless loop for a vendor, Lumba the Crusher that is not here in the current phase. This only happens if it teleports from the dungeon directly into the garrison, it's working fine if it hearths from somewhere else. Restarting HB fixes the problem, but it's still a headache as reloggers don't detect it.

View attachment 6608 2015-03-26 20.53.zip

 

[chinajade]

DungeonBuddy is having trouble repairing in the Garrison. It seems to constantly look in an endless loop for a vendor, Lumba the Crusher that is not here in the current phase. This only happens if it teleports from the dungeon directly into the garrison, it's working fine if it hearths from somewhere else. Restarting HB fixes the problem, but it's still a headache as reloggers don't detect it.

View attachment 173285

Hi, Tarathiel2, and many thanks for the log.

We've opened HB-2134("DungeonBuddy: Having issues using Garrison repair vendor") against this issue.

cheers,
chinajade


[size=-2]Ref: Tarathiel2's problem report w/log[/size]

 

[Kaelhoel]

Trying to do Draenor normals in a 5-man group, I keep finding my team with the deserter debuff. It appears that only the tank and healer are entering the dungeon.I don't know if this is relevant, but I have two party members with the same name on different realms. [Removed toon names —chinajade]

Log:View attachment 12036 2015-03-28 14.13.txt

 

[Mydruid]

Hey Chinajade,

Quick question I'm wondering if you can help me with.

Is it possible with dungeonbuddy to create a custom script that will queue for certain dungeons based on level of character or of characters in the party? Or perhaps with Professionbuddy?

Some dungeons aren't ideal to bot with due to the pathing groups take but setting a specific dungeon quickly becomes obsolete as you out level it.

Any help would be greatly appreciated.

EDIT: I have a semi workaround for this issue. Most dungeons are fine so random queueing works. What I did was take the code from the Oculus.cs and put it into the dungeons I didn't want to do (Vortex Pinnacle). I have to eat the 30 minute deserter but that is better than having to manually change dungeons or risk getting reported. Ideally there is some way to do it like in my OP. I think with Professionbuddy it should be doable but I dont know how.

While doing all this I figured a way to skip to the next task in HBrelog would be very useful. Does anyone know of a way to call the HBRelogSkip.cs from the Quest Behaviours in Dungeonbuddy. I'm looking at the plugin LogMeOut as that gives options to call LUA based on a number of factors, the one I am interested in being level. Again any help would be appreciated.

I attached my Vortex Pinnacle file in case anyone is interested in the idea.

 

[Zardoz1]

Trying to do Draenor normals in a 5-man group, I keep finding my team with the deserter debuff. It appears that only the tank and healer are entering the dungeon.I don't know if this is relevant, but I have two party members with the same name on different realms. Tank is xxx-BloodfangRealm & healer is xxx-JudgementRealm.

Log:View attachment 173433

Shouldn´t be the reason. Did you check the spec settings from your DD´s? F.E. if your warrior is Arms and spec setting is Fury the warry won´t enter the dungeon. Had this issue with one of my DD´s. You have to do the specc setting in HB settings, not in combat class.

PS: remove the names.

 

[Dan021]

Hello, been using dungeonbuddy for a while and i came across this bug. In shadowmoon burial grounds, right before Nhallish, bot stops and keeps applying blackspots to 2 hidden packs of mobs that appear after u "step" on them. Also attached log:

 

[odano1988]

few months back i suggested a fix for bloodmaul slag mines exit cordinate. If you want to farm bloodmaul slag mines you cant with the hbuddy version because it never exits, the cordinate isnt close enough to the exit. I have fixed it on my end and fix it every time a new hbuddy drops but still wondering why i was ignored when it is a problem. At the time I posted the correct cordinate and nothing was done.....