What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

HB ARCHIVES: DungeonBuddy--DO NOT DELETE

Honorbuddy v2.5.14505.803


Changelog
Code:
* Updated for patch 6.2.2.20574

New features:
--------------
* Core
- Honorbuddy's compiler now supports C# 6.0 features. (HB-2627)

Bug fixes:
--------------
* DungeonBuddy
- The number of deaths is now updated in the Info tab (HB-2637)

- ScriptHelpers.MoveInsideBossRoom has tank no longer wait for group members to enter room if they are busy dealing with aggro. (HB-2636)

- Fixed the boss step orders for all dungeons whose step order changed in WoW 6.2.2 (HB-2622)

* Questing
- Garrison Missive type repeatable quests' completion status are no longer cached. (HB-2630)
Azjol-Nerub (WOTLK) is a bit buggy, at the first boss, all toons are running to the door, ignoring the Gatekeeper and the Watchers , dying all the time unless I do manual intervention (running a 5man HB team) the "fix zip" is in place, but didnt help
MR. HighVoltz pushed a step fix forward with the .803 release there should be no difference in the fix zip and the actual release of HB now.
 
Last edited:
the reason for it is so that the bot can jump into the middle of a Dungeon and pick up exactly where it needs to go. Otherwise, the bot would go back to the first boss to figure out where it was. It also provides support for stages with multiple parts(ex: Grimrail depot). If you entered the 2nd part of the stage with no "step" numbers to know the first part was done then it would try to go back to the first stages boss although it was on a completely different stage part(this would also create a condition that would loop forever pointlessly).

But the steps are not in the right order...
 
But the steps are not in the right order...
According to the changelog they fixed that. I left my quickfix.zip attached in case one might of gotten missed but .803 should of fixed all that.If not a listing of which ones need to be reviewed by Mr. Highvoltz would be nice

I can confirm the two WOD(Skyreach Heroic + Shadowmoon Grounds Heroic) ones that were messed up are fixed. I just downloaded a fresh copy to check.
 
Last edited:
Quote Originally Posted by Honorbuddy: 2.5 r14460 Build 802 Change Log
New features:
--------------
* ProfessionBuddy
- CancelAuction and SellItemOnAh will no longer include the 'of the ___' suffix when searching AH for random-generated items. (HB-1455)

- Professionbuddy will now include profile line numbers in log messages. (HB-1509)

Bug fixes:
--------------
* DungeonBuddy
- Fixed an issue that caused Dungeonbuddy to exit dungeon prematurely. (HB-2615)







Hi , when i start the DG run with RAF team or alone sometimes bot leave and it start queued again but the dungeon not finished yet. When just i start a bot without team he leave at DG Wod exemple.
he said "Dungeon is Considered complete in 10 seconds . "

He somethimes kill 1 boss and queued and sometimes kill all bot the last on nothing

I found this bug in updated past 3-4 update before the DG That worked well

thx

Please someone may i help me?
 

Attachments

Last edited:
Hi , when i start the DG run with RAF team or alone sometimes bot leave and it start queued again but the dungeon not finished yet. When just i start a bot without team he leave at DG Wod exemple.
he said "Dungeon is Considered complete in 10 seconds . "

He somethimes kill 1 boss and queued and sometimes kill all bot the last on nothing

I found this bug in updated past 3-4 update before the DG That worked well

thx

Please someone may i help me?
Sure, just use this XML. It will add kill verification to the Dungeonbuddy to confirm the bosses are dead(If not it will go kill them). And to defend them they did Fix Grimrail Depot and Mogus palace on .802 and on .803 a number of other dungeons effected by the step syntax issue caused by a update to WoW.
To use this XML: Just overwrite your old one at "HONORBUDDY\Default Profiles\DungeonBuddy\Classic\Dungeons\Stormwind Stockade.xml"
 
Last edited:
Is there any way to impliment a function where my bot leaves the dungeon after hes stuck or didnt do anything`? For example if my bot is stuck or lost the group that he leaves the dungeon as a kind of emergency out. it would also be great if i could configure if i even wait for the healer to regenerate mana.

i also have the problem if the bot just waiting in the Stonecore right before Ozruk.
 
Last edited:
Is there any way to impliment a function where my bot leaves the dungeon after hes stuck or didnt do anything`? For example if my bot is stuck or lost the group that he leaves the dungeon as a kind of emergency out.
You would need to request a plugin be made for that as I don't recall one that's been made for that yet.


it would also be great if i could configure if i even wait for the healer to regenerate mana.
If your hosting the healer just set it to drink/eat at % you want it to be at before moving on. If not you'll need to also have a plugin made for such.

i also have the problem if the bot just waiting in the Stonecore right before Ozruk.
just waiting as a tank, dps, healer? whats the setup its waiting with? does the HB caption anything while it "waiting" like waiting for tank?
 
Stonecore trash before 2nd to last boss is EPIC glitch and pulls all the trash and can tell exactly what it is.. its executing the bot to move and then walks out of leader range. then attepts to walk back to leader then back to spot over and over and over til leader pulls then after combate it walks back to the spot on the hill before the trash. then after the group as moved to the boss itll hug the wall and pull al lthat trash while walking to the group log doesn't show exact location and my log is to long to submit


after further review here is a pic execute behavior for that location is taking priority over all else and even when the group is ahead its cause major gltitchy bot movment
 

Attachments

  • grjio.webp
    grjio.webp
    35.5 KB · Views: 30
Last edited:
Having an issue, running Shadowfang Keep with the Farm option, it is running it fine but not looting any mobs except bosses. Anyone else encounter this?
 
has anyone edited profiles so that it runs in timewalking? Just need to add the instanceID/ZoneID

if you have them, mind uploading?
 
has anyone edited profiles so that it runs in timewalking? Just need to add the instanceID/ZoneID

if you have them, mind uploading?
Its already been uploaded read below.

Timewalking Support

After some fidgeting around, I managed to get full support for Timewalkers dungeons implemented including Random Timewalker Dungeon.

Features:

  • Recycles DungeonBuddy scripts for WOTLK, and BC where available.
  • Dummy CS files for dungeons that wouldn't show in the list (The Arctraz, The Opening of the Dark Portal)
  • Addition of CS files to enable the random queue selection properly. (it was brought to my attention it would queue for specifc dungeons if only the dungeon profiles were in place, bypassing the random option in the blizz ui which I felt could be dangerous, so figured out a way to make it choose the appropriate random id, and not queue by specific timewalker dungeon).

This has only been tested to work with Warlords of Draenor opened. Please let me know if it shows up for all other levels appropriate to do Timewalking (BC is 70+, LK, is 80+).

WARNING: Even though the individual dungeons show up under "Unknown", I strongly recommend that you do not queue for the dungeons this way. The Timewalking dungeons have different id's than the normal versions, which means by queuing for these specifically, you are bypassing the built-in queing system. Since there is no interface to queue for these dungeons specifically, I believe that this can be detected fairly easily. (@highvoltz - If you could modify the DB core to block queuing for these specifically, that would be great.)


The Download: View attachment 184993

Instructions

Extract the contents of the zip file into the root of your HonorBuddy folder. The zip file contains two folders in the current layout of where DungeonBuddy stuff is located based off the root folder since this requires placement of new files in both "DefaultProfiles\DungeonBuddy" and "DungeonScripts" folders.
 
if the bot has quests to turn in and it takes to long to turn them in the bot will leave the dungeon group and not turn the quests in unless it re enters the dungeon " sometimes it never does and out levels the quests" so its basically lost exp any way to force quest turn in over "dungeons considered complete in 10 seconds" ?
 
STONECORE

Stonecore does not seem to be working? Levelling a 5-man team through Dungeonbuddy and they will stop right before Ozruk and do nothing. I tried to take over the tank manually, but the rest of the team won't move at all at this point even though Honorbuddy is active on all of them so I had to pull the boss back to where they were standing in order for them to do anything. After Ozruk was killed I restarted Dungeonbuddy on the tank to see if they would move towards the final boss but they just stopped in the same spot as before.



THE CUNNING OF STRATHOLM

Another one that is not working correctly is The Cunning of Stratholm. Doing a full 5-man botting team within that dungeon is a nightmare. They have some serious difficulties with activating the scenario. On the first go no-one interacted with Chromie at the bridge so the whole conversation between Jaina, Arthas and Uther didn't start at they all moved to the entrance and waited without nothing happening. On the second try they did manage to talk with Chromie in-front of the bridge so they started the conversation, but the healer ended up falling into the water and get stuck and instead of porting outside and in again it just kept trying to get out of the water by swimming into the wall.

After getting the healer out of the water, and then successfully interacting with Arthas in order to start the actual instance and the purging the team got to 5 out 6 in the first portion of the dungeon and all of a sudden they all ended up moving back to entrance of the entire dungeon far outside Stratholm and they would just sit there for an entirety.


THE NEXUS

This instance is having some issues as well. The tank does seem to have some difficulties with detected mobs. On the way to Omorok the Tree-Shaper the tank tends to ignore some of the adds before him so he ends up pulling 2-3 packs of adds when running to pull the boss. These adds aren't the worst, but it sure puts a lot of strain on the healer and my team has end up wiping a few times due to this.

The most important issue is the lack of sensible tactics on the last boss (Keristrasza) as the bots does not seem to fully utilise the jumping mechanics of this boss. This is not a huge problem in normal mode as the damage from the boss when not jumping is survivable so in most cases (but not all) it will work out okay. But on heroic and timewalking difficulties it makes it next to impossible for the bots to kill this boss. I'm not entirely sure this is due to a lack of scripting so the bots simply ignore the mechanic, or if it has something to do with timing. It does seem to be like the bots are trying to jump, but they seem to do it way too late so the damage has already been caused to the team when they suddenly decides to jump.



The Nexus and Stonecore are rather important to get sorted out in my opinion. The Nexus is already relevant due to Timewalking dungeons, and Stonecore is supposed to be added as a Timewalking dungeon in a few weeks so it should be prioritized as well. Instances like The Cunning of Stratholm is of less importance as it's only a part of levelling, but having dungeons that does not seem to work is not ideal so perhaps it should be removed?
 
STONECORE

Stonecore does not seem to be working? Levelling a 5-man team through Dungeonbuddy and they will stop right before Ozruk and do nothing. I tried to take over the tank manually, but the rest of the team won't move at all at this point even though Honorbuddy is active on all of them so I had to pull the boss back to where they were standing in order for them to do anything. After Ozruk was killed I restarted Dungeonbuddy on the tank to see if they would move towards the final boss but they just stopped in the same spot as before.

Yep having the same issue.
But it looks like no official is maintaining the botbase anymore. Only Zonehunter cares for it.
 
I have a question about the Timewalking dungeons. I've been running a 5-man team of 90s doing heroic pandaria dungeons. They seem to handle these without too many problems. However, when I try to use them to do random Timewalking dungeons, they really struggle. I know gear scales for Timewalking but would it make a difference if they had better armor? Or is it a bot problem? I'd love to use them to grind out some of those dungeons but it seems they struggle too much.
 
Finding issues with 5man heroic mop team.
Siege of Niuzao Temple - not killing General Pa'valak to unlock wall to Win Leader Ner'onok
Temple of the Jade Serpent - kills lorewalker stonestep then marks instance as complete without killing Sha of Doubt.
Brewstout Brewery - kills Hoptallus then marks instance as complete without killing Yan-Zhu the uncasked
Scholomancer - Kills to Lilian Voss then marks instance as complete without killing Darkmaster Gandling (also get stuck at rattlegore, running against unopened gate without engaging/pulling rattlegore)

Is this intended? Ends up with the team being on dungeon finder CD for at least 5-7minutes and doesn't get the completed bonus for the instances

attaching a log from yesterdays runs
 

Attachments

Last edited:
Back
Top