HB ARCHIVES: DungeonBuddy--DO NOT DELETE

* DungeonBuddy
- Fixed an issue that caused bot to leave some instances before they were complete. (HB-2918)

After the first run my bot left the dungeon just as before the fix.

View attachment 10600 2016-08-04 10.32.txt

 

helo. I have an issue after last update "waiting for healer to get in range" in treeroot status text. bot doing nothing except waiting and dying becouse of that. Im not in paty mode/ Im SOLO no healers around and never be. i use Dungeon buddy. Need a fix!

 

So it looks like my bot is having the same issues as the above. My tank is leaving right after entering

[DungeonBuddy]: === Dungeonbuddy Settings ===
[DungeonBuddy]: Party Mode: Leader
[DungeonBuddy]: Combat Movement: False
[DungeonBuddy]: Kill optional bosses: False
[DungeonBuddy]: Tank In Random Groups: True
[DungeonBuddy]: Pickup Quests: True
[DungeonBuddy]: FollowingDistance: 8
[DungeonBuddy]: AbandonLowLevelQuests: True
[DungeonBuddy]: Loot Mode: Always
[DungeonBuddy]: InsideInstanceRepairPercent: 10
[DungeonBuddy]: OutsideInstanceRepairPercent: 50
[DungeonBuddy]: InsideInstanceMinFreeBagSlots: 3
[DungeonBuddy]: OutsideInstanceMinFreeBagSlots: 15
[DungeonBuddy]: Item Sell Quality: Rare
[DungeonBuddy]: HearthOnVendorRun: True
[DungeonBuddy]: GroupLootMode: Personal
[DungeonBuddy]: Port Outside Instance To Sell: True
[DungeonBuddy]: Port Outside Instance To Buy: True
[DungeonBuddy]: Port Outside On Ghost Sighting: True
[DungeonBuddy]: Mail Boe Items: False
[DungeonBuddy]: LeaderName: (blank)
[DungeonBuddy]: Party Members
[DungeonBuddy]: ****
[DungeonBuddy]: ******
[DungeonBuddy]: *****
[DungeonBuddy]: *****
[DungeonBuddy]: Role: Automatic based on spec. The Tank role will be used
[DungeonBuddy]: Dungeon type: RandomDungeon
[DungeonBuddy]: Raid type: None
[DungeonBuddy]: Scenario type: None
[Singular] Hotkey: To add a LOGMARK, press: [Shift+Alt+Ctrl+M]
[Singular] Your Level XX Tauren Protection Paladin Build is
[Singular] ... running the Dungeonbuddy bot in Orgrimmar
[Singular] ... Zone: Kalimdor using my INSTANCES Behaviors in a group of 5
[Singular] ... in a group as TANK role with 5 of 5 players
[DungeonBuddy]: Queuing for Random Classic Dungeon
[DungeonBuddy]: Queuing for Random Classic Dungeon
[DungeonBuddy]: Accepting LFG propsosal in 8 seconds.
Not in game
[Singular] Your Level XX Tauren Protection Paladin Build is
[Singular] ... running the Dungeonbuddy bot in Orgrimmar [5-player Normal]
[Singular] ... Dungeon using my INSTANCES Behaviors in a group of 5
[Singular] ... in a group as TANK role with 5 of 10 players
[DungeonBuddy]: Entered Maraudon - Earth Song Falls dungeon and using default script
[DungeonBuddy]: Successfully loaded default profile for Maraudon - Earth Song Falls
[DungeonBuddy]: Dungeon is considered complete in 10 seconds. Reason: Completed
[DungeonBuddy]: Leaving group. Reason: Tried to queue 3 or more times without success
[DungeonBuddy]: Left dungeon: Maraudon - Earth Song Falls
Not in game
[Singular] Your Level XX Tauren Protection Paladin Build is
[Singular] ... running the Dungeonbuddy bot in Maraudon
[Singular] ... Zone: Kalimdor using my INSTANCES Behaviors in a group of 5
[Singular] ... in a group as TANK role with 5 of 5 players

 

"All pre-WoD raids are not supported, and the scripts have been removed. It takes hours to queue for these raids, which makes it impractical to test repairs."

Wouldn't it be nice to still have these raids but with the "farm" option?

 

My followers are not clicking on the ports in auch, bug or wrong settings?

 

Same here.

Have grinded timewalking afk for 20 hours and got 2 completed

 

I know on the OP's page that it says Hellfire Citadel has no ETA; however - I was curious to know if this was something that was planned or on the docket for HB? I only use the bot for DB and questing - so not having Hellfire Citadel is kind of a bummer. It looks like the expansion will be out before it would even get worked on though. Is there any reason why this raid would not be included?

 

There is a helfire plugin called "felfire" you can find it in the store. It uses dungeonbuddy as a botbase but added custom scripts in form of a plugin. Currently its not always looting the bosses but you will get it in the mail later on, other then that it works very good! You can use the que for raids not complete system in dungeonbuddy. Just look up "felfire" in your buddy store.

 

Just how it stands right now, what is worth running a 5 man? Perhaps farming mop dungeons with wod accs?

 

having same issue waiting for healer to get in range anyway to fix that??

 

from a distance bots stop following the leader, or go out to repair and return at the beginning of the dungeon.

waiting for the correction of the dungeon Temple of the Jade Serpent first boss = Wise Mari = bots are running igua crazy to die for water damage

 

Having this issue as well when trying to solo dungeon

 

The bot still leaves after the first encounter the majority of the time? I thought this was fixed?....
Also the bot is prioritising out-of-combat heals over looting, so it will heal after an encounter and then skip looting to follow the group.

 

Can and will provide logs for whatever you need, but here are the bugs ive seen and have recreated at least twice over.

1) Dungeonbuddy mass suicide - So every so often, while doing skyreach, the 3rd boss (the raven that comes down) as it dies, falls off the edge, and sometimes so do the bots? The tank jumps after the body of the bird followed closely by every other bot. My guess is the tank bugs thinking the boss is still alive and moving, and the bots following the tank mass suicide. Does not happen everytime but ive run it 11 times and its happened twice.

2) Dungeonbuddy Auchindoun teleport glitch - So everytime (and i mean everytime) i run this instance, the healer / dps cannot take the teleporters to the next area, which means the tank goes and stays there waiting for healer and group, but they are sitting on other side of the teleporter. They will take the LAST teleporter (the one to the boss) but only once the tank has LANDED at the boss. This means I have to manually click 4 teleports 3x. Not that big of a deal except that I cannot afk farm these dungeons.

3) Dungeonbuddy Grim Batol Train Glitch - So once the bot clears the first boss, it gets on the train car. After it clears the train car, it goes towards the middle of the traincar and tries to run into a wall spamming my bot log with "Moving tank to POI XXXX" Even if you stop the bot, move him to the next pack, and start it again, it STILL goes back to this same car, same spot, and continues to run into the wall. This happens everytime and won't continue the instance, I have to manually take over the tank and the rest follow fine.

4) Dungeonbuddy Everblooms - It does fine up until the end boss, then it for some reason does not send all the bots through the final portal, and it doesnt start the encounter. I have done it 7 times now, and only had it successfully make all bots through the portal. This isnt that big of a deal again, except that i cant afk bot.


These are the issues i've been able to recreate btw, not the ones ive noticed randomly happen. I dont care about those, as they are anomalies... i just log em for my personal self then if I can recreate them like the ones above, Im attempting to seperate the logs and post em all here.

Anyways I can get logs for any of these issues if asked, just tell me what point of view you'd prefer, tank, healer, or one of the dps (1 melee 2 ranged currently)

 

Is there a way to disable

"Activity: Waiting for more DPS to get in range"

When tanking in public? Because my tank and heals can take the whole dungeon by themselves =P

PS.: Please, don't worry about me being reported... because I don't...

 

While playing with others, the tank is supposed to wait for the group, thats why it "waiting for more ... "

But if you are certain what you are doing, you can change the mode to farm, and tick the current dungeon in the list.

 

But if I set it to farm, do I have to go to the location? I want to use the dungeon finder =P

The problem is that ppl go alone and the tank just stand still way behind waiting dps to get near them...

I've tried to find on the codes both script and profile, and found shit to disable that...

If they're near me, good! If not I will take the boss anyways with my healer... That's what I want. But the way it is now, if the dps rushs up the tank stay behind and just get stuck "waiting on dps to get near"...

Any tips are welcome and thank you for the answer!

EDIT:

Again, as I was typing it got stuck behind... the DPS way ahead in the dungeon... My tank is in the middle "Activity: Waiting for more DPS to get in range"...

If anyone figure this out, theres 5$ @ paypal for you! =)

 

Indeed, I see no automatic way to disable this. The Farm-switching method is good to be changed, once we are inside dungeon, then on dungeon complete, to return to the previous queue method.

Thats the cons of running not full own party in LFG, real people are acting weird sometimes.

The other solution is to queue as dps+healer. It should be fast enough too.

 

Yeah, I know... but its because I got hit only in 2 accounts... I don't wanna start new characters on other active accounts...

Anyways, if you don't know a solution to disable this shit, I don't think there is one... So, I'm gonna give up...

Thanks for your attention and tip =)

 

Hi, when i start farm dungeon with solo character, bot waiting healer and do nothing