HB ARCHIVES: DungeonBuddy--DO NOT DELETE

Hello,

Is there any ETA on updating the bot to support BRF LFR raids?

Thanks a lot for the great work!

 

One question:
Could the bot rejoin the queue with the group if the group decides to do another run after a dungeon has been completed ?

This way a dps bot can avoid being in the queue for like 10-30 other minutes and speeds up the xp gains alot more.

 

My 2man raf team just accepted a queue from random human tank and entered a new dungeon with him.
Not cool, not cool at all...

See log towards end.

 

Hi My bot runs dungeons nicely, but it skips a lot of Regular mobs, which are no more than 10 yards from the bot, is there a way to have the bot kill everything in range? every mob so to speak, in the dungeon? it kills between hotspots, but say for example theres 10 mobs to the left of its path, it just skips it

any help?

thanks for your concern

 

Hi, Y2krazy, and many thanks for that screenshot and log!

Indeed, we recently noticed this problem also when pursuing the Guardian of the Deep. We've opened up HB-2191("DungeonBuddy: Blackfathom Deeps: Vascillating movement in trying to move to Guardian of the Deep") against this issue.

cheers,
chinajade


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

 

Hi, Tomten2,

Indeed, all non-WoD LFRs are no longer supported. The queue times for these raids are on the order of hours. This makes it nigh impossible to test script changes when problems occur. The senior staff decided it was better to remove the non-Supported raids entirely, rather than let the Community be frustrated by instances that are no longer supported.

cheers,
chinajade

 

Hi, Dan021, and thanks for the follow-up with the Singular log!

We've opened HB-2192("DungeonBuddy: Shadowmoon Burial Grounds: Infinite looping adding and removing blackspots on Nhallish trash groups") against this issue.

The problem appears to be peculiar to your installation, but we can think of now work-around for you at the moment. There are no other tell-tales in the log as to why this might be happening.

cheers,
chinajade


[size=-2]Ref: Dan021's follow-up problem report w/log[/size]

 

Hi, Maro1988,

The staff never gives out ETAs. We work against a comprehensive master list of things to repair. Part of this master list is made visible to the Community in the "Issues & Dispostions" post (The 2nd post of any Honorbuddy release thread.) Your concern is HB-1834 in that list.

cheers,
chinajade

 

Hi, Hugebelow,

No. This was feature request HB-1056("Don't break group, if the group requeues for dungeons"). The request was closed long ago with this disposition:

"We don't like the idea, here's why:
* No control of what is queued for unless leader.
* Only beneficial to DPS role and possibly a disadvantage to Healer/Tank roles because queuing solo potentially has more matchmaking results, unless whole group agrees to queue up which doesn't happen often in our experience.
* And, the most important reason... The more time players spend together, the less of a stranger they become to each other, the more likely they'll try to socialize. Any attempts to socialize with the bot increases the risk of being discovered as a bot.

Because of these reasons, we feel this would be a bad addition to Dungeonbuddy so we're going to decline this feature request."​

cheers,
chinajade

 

Hi, Tomten2,

We don't see anything unusual here. This log is from your healer.

[16:25:44.868 N] [DungeonBuddy]: Dungeon type: RandomDungeon​

You've configured DungeonBuddy to queue for random dungeons. DungeonBuddy will queue and continue to queue for RandomDungeons until you stop Honorbuddy.

From your log, it looks like you finished Shadowfang Keep, and queued (and entered immediately) Wailing Caverns. This is normal behavior. Once a dungeon is complete, Dungeonbuddy will requeue for the next dungeon without leaving the current one.

If your point is that your other toon was a tank, and it shouldn't have entered a group with another tank...
This means that either your tank or the other one queued as DPS instead of Tank. If so, this is not a DungeonBuddy issue.

cheers,
chinajade

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

 

Hi, Applewow,

There are no Dungeonbuddy configurables for this. The dungeons are scripted to behave a certain way. It may also be possible you are using a third-party combat routine that is not behaving properly. To analyze anything further, we'll need to see a full log.

Ref: [Guide] How to attach your log​

cheers,
chinajade

 

I didn't see who initiated the requeue (my toons or tank) but it was done with people still in the group and bot rejoined a new dungeon with the same people.
The expected outcome would have been that my toons leave the existing group after turning in quest (can that be the culprit, it teleports out and into dungeon to turn in quest again?) and then requeue alone.

 

Thanks for the fast reply and all the concern Also, if anyone else has this problem, the fast workaround i have found is using a plugin called "Jumpy" (which can be found around here, on the forum). An extra jump provides the bot with the push needed to step on the next group of mobs and engage in combat. It can also help the melee dps in the fight against ner'zhul (where they get out of range by 1 yard when they try to kill adds and avoid them in the same time).

 

[size=+1]Update on HB-2156[/size]

@Kaelhoel, we're directing this at you since it appears to be a problem unique to your installation...
Ref: Previous response

HB-2156 has been marked as "Incomplete" with the following note added to it:

"Our guess is the followers don't have 'LeaderName' in Dungeonbuddy settings assigned to the leader's name and that is causing them to leave the group which also causes the leader to also leave. We will need to see a log from one of the followers to verify."​

If you can get us a log of a follower or two that is experiencing this problem, we'll attach it to HB-2156. If a log cannot be produced within the next few days, the report will probably be closed.

cheers,
chinajade

 

Hi again, Tomten2,

Indeed, you appear to have analyzed the issue correctly.

• Dungeonbuddy does 'leave the dungeon and reenter' to quickly get to the quest-giver/turnin at the entrance to some dungeons.
  
• Dungeonbuddy can't break group while this in in progress, as leaving the group would prevent re-entry to accomplish the turn in.
  
• If the human group member re-queued (and queue popped) before these Dungeonbuddy actions were complete, the issue you describe would indeed occur.

We're not seeing a whole lot that can be done to improve his situation. If it is a concern, perhaps turn off the 'questing' capabilities of Dungeonbuddy while you are running with humans.

cheers,
chinajade

 

Hi again, Dan021,

HB-2192 has already been found and repaired, and should be available in the post-.782 Honorbuddy drop.

cheers,
chinajade

 

Hi where can i get profiles for the other wod lfr raids? thx

 

Hi Guys! Thanks for an amazing product!

I'd like to request that DungeonBuddy be made to loot the Core of Iron from the Grimrail Depot and the Corrupted Blood of Teron'gor from Auchendoun after these heroic dungeons are finished. These items are for the Legendary quest and currently the bot leaves the dungeon without looting them. Thanks!

If anyone knows of a plugin that can loot items by name or ID in the meantime I'd appreciate a link. Thanks

 

Hi, Chasemay,

We've opened the following feature requests:

• HB-2207: Dungeonbuddy: Grimrail Depot: Loot "Core of Iron" before leaving dungeon
• HB-2208: Dungeonbuddy: Auchindoun: Loot "Corrupted Blood of Teron'gor" before leaving dungeon

cheers,
chinajade

 

First thing that comes to mind, but im guessing its not that easy, would be:

1. Don't let bot accept queue ( /role check) pop from anyone outside the specified Dungeonbuddy "Leader/Follower list". (Just decline it and turn in quest, its very common practice by humans)
2. Don't let bot queue with anyone in party outside the specified Dungeonbuddy "Leader/Follower list". (Simply prevent requeue until the "leave dungeon and reenter / turn in quest" behavior is completed.)

This means bot will just decline any requeues until quests is turned in.
And it will refuse to queue itself for failing "other party members" check and leave ?

Once its "alone" it'll just queue up like regular ?

While RAF'ing(Even heirloom solo play) the quests are worth insane experience and a really good feature, don't wanna turn it off ;(