Honorbuddy v2.6.15695.836 (for WoWclient 7.0.3.22293) [SIZE=+1]Hotfix v2.6.15695.836 [/SIZE] 3rd party Quest Behaviors should properly compile now [SIZE=+1] Known Issues [/SIZE] Quest bot not recognizing quest NPCs for collect item objectives is caused by a bug in World of Warcraft itself. We are constantly updating questing profiles to workaround this issue. Please use the profiles from Buddy Store for daily updates. Garrison API might still not be fully functional yet. Dungeonbuddy might not be fully functional yet. [SIZE=+1] [/SIZE] [SIZE=+1]Changelog[/SIZE] Code: Bug fixes: -------------- * Core - Fixed a performance issue caused while the toon is stealthed. (HB-2884) - Running Wild should properly be used as a ground mount now. (HB-2507) - Fixed an issue with Honorbuddy Installer where it might recognize Windows 10 as an earlier version of Windows (HB-2831) - Fixed an issue where Honorbuddy would fail to repair items when needed (HB-2914) * ProfessionBuddy - GetMail action is now fixed. (HB-2921) - PB should now be able to properly use all trade skills again (HB-2911) - Buying or selling items on AH no longer causes WoW to crash (HB-2920) * QuestBehaviour - MountHook should properly purchase Pandaren mounts now (HB-2853) - KillUntilComplete should properly loot slain mobs now (HB-2830) - MountHook will now be removed when the bot is stopped or a new profile is loaded. (HB-2832) * Questing - Kill and CollectItem objectives will no longer skip quest npcs while being attacked by other units. (HB-2559) - Quests in log will no longer affect AvoidMob profile tag while not running Quest bot. (HB-2779) * Singular - Holy Priests have been fine-tuned a bit and should now be able to do Bronze Proving Grounds with common quest gear. (HB-2923) - Fixed a bug where stopping the bot in a battleground while using BGBuddy would cause attacking players in world content. (HB-2829) - Feral, Balance and Guardian Druids should now cast Healing Touch instead of waiting for health to recover after combat ends. (HB-2915) - Discipline Priest should now only cast Penance as a heal if the player knows The Penitent talent. (HB-2916) - Protection Paladin will now use more of its intended abilities. (HB-2893) - Monk Mistweaver will no longer try to cast and wait for the channeling of Soothing Mist. (HB-2904) - Restoration Shaman will now properly heal and fight as needed while in an instance context. (HB-2922) Other changes: -------------- * Documentation - Sharpened the documentation for LocalPlayer.Totems (HB-2501) [SIZE=+1]Reporting Bugs[/SIZE]Please report confirmed HBcore bugs to THIS thread! When reporting a bug, please include your full log file (found in your bot folder under the "Logs" directory, sort by creation date to find it easier), a full and detailed explanation of the bug, as well as any screenshots or profiles that may be useful in tracking down the bug.Ref: [Guide] How to attach your log Here are other threads where it may be appropriate to report your problem, instead of here: ArchaeologyBuddy thread DungeonBuddy thread FishingBuddy thread GarrisonBuddy thread GatherBuddy thread ProfessionBuddy thread Singular thread [SIZE=+1]Releases[/SIZE]Honorbuddy: Installer (recommended) / Zip Honorbuddy Deutsche Version: Installer (recommended) / ZipFor German users, this Honorbuddy client must be used. Other Honorbuddy version(s) will not work for you. Ref: Honorbuddy Deutsche Version - Pressemitteilung [SIZE=+1]Requirements [/SIZE] v4.6.1 Microsoft Visual C++ 2015 Redistributable Update 3 (x86) (vc_redist.x86.exe) [SIZE=+1]Notes[/SIZE] Comprehensive Changelogs can be found here: Honorbuddy comprehensive changelog HonorbuddyDE comprehensive changelog The open issues listed here are only a fraction of our work load. Many issues we must address are internal, or not for public consumption. [SIZE=+1]FAQs[/SIZE]Is it safe to bot?Answer here: BosslandGmbH:HelpDesk:Is Botting Safe?Will you be supporting a 64-bit version of Honorbuddy in this release?No. The game developer continues to ship a 32-bit WoWclient. We've had this discussion many times in the past, and the answer is "no, not until its absolutely needed". Here are two posts to get you started: The Senior Development staff's stance "64 bit" thread [SIZE=+1]Thread Management Rules[/SIZE]Posts that have been archived from this thread are available here:HB ARCHIVES: Processed Issues from Releases Posts are archived according to the following rules: Posts that have received a response from the Bossland GmbH staff are archived. Do not assume that because your post was archived, it means we don't care. We are simply keeping this thread clean. This thread is for confirmed HBcore bug reports only. You should have tried to resolve your problem using the Support forum, first. If the Support forum can't resolve your issue, they will ask that you report the problem here. We will only look into bugs reported against the version of Honorbuddy represented by this thread. Bugs reported against any other Honorbuddy releases (including Betas) will be archived immediately without comment. Bug reports without FULL, unedited logs attached will be immediately archived without comment.Ref: [Guide] How to attach your log Either report bugs properly, or do not report them at all. We cannot look into bugs that have little to no information. Bugs reported in such a fashion will be immediately archived without comment. If you wish to submit a feature request to this thread, please make certain it is not already covered.Ref: Feedback for Honorbuddy Improvements This is not a discussion thread. If you derail this thread, you will be muted for up to 30 days. No questions. Archiving may not be immediate, but occur every few days. Enjoy!
honorbuddy 836 Dungeonbuddy - bug leaving the first or second boss without completing the dungeon still ... waiting nine version
The shaman fix is working 100% for me. Been running flawlessly for like 3 hours straight. Great work!
Dungeonbuddy laggy... Enters instance, does NOT auto load the profile. I had to stop / start the bot each time and then it would complete the instance, seems to not want to load the profile or something after accepting que, just sits on status bar "Queing for LFR..." Confirmed 2nd instance (the Nexus) did the same thing, i waited over a minute for the bot to start moving, it never moved. Had to stop it, then start it again and it started to do the dungeon. And again... so this is happening with all my chars in dungeonbuddy. Heals tanks and damage. Is this a ME bug or a honorbuddy bug?
View attachment 4628 2016-07-31 10.12.txt Please fix the questing bot. it keeps giving this "current error" Ever since the new updates. Wasn't like this before all these updates started. the log is from 2 patches ago but its still the same error, i make sure to keep it updated with fresh installs.
New issue, Questing bot continually kills units even after the quest is over, while on the way to turn in the quest. Any unit who enters his path, he will dismount, kill it, loot it, then continue to turn in the quest... which I guess isnt the worst bug in the world but when theres 40+ units within 40m of the path the bot takes to turn in the quest... it delays xp gains by minutes, and eventually hours.
hi again i dpn't know may be iti is my bug but feral druid (using questing bot) doesn't want to aoe. If druid doesnt aoe it take more 50 sec for i dungeon run Uploading 2 Logs 1) Old 829 Routine View attachment Old 829 routine.txt 2) New 836 Routine View attachment New 836 routine.txt Thx.
Any and all rotation issues should be directed to this thread https://www.thebuddyforum.com/honor...riven-cc-plain-version-3-a-6.html#post2232169 as this is the thread dedicated to rotation based issues (singular is the bots coded rotation control)
Heads up everyone using DungeonBuddy. I noticed since pre-patch that Dungeonbuddy often waits before following the tank. I found out why. This can take up to 20-25 seconds after you enter the dungeon. DungeonBuddy kicks in, at the moment the LFG timer reached 0. You can see this by yourself when you enter a dungeon after the queue pops up, and everyone accepts very quickly. You enter the dungeon, tank immediately starts rushing (in case it's not your own tank) and your toon does... nothing. On your screen you see an LFG timer (somewhere between 25 seconds and 0). You need to move the toon manually until the timer reaches 0. Then DungeonBuddy takes over. I do not know why this mechanic has changed in WoW itself, I cannot remember the LFG timer continuing after all five toons enter the dungeon. But, it does. So if you've asked yourself why your toon does not move for the first 5-25 seconds; that's why.
ive touched base on this in a post above, but keep in mind 836 even says "DungeonBuddy may not be working properly" So waiting for an update and a confirmed working version is what you should do, he knows about it.
I'm not sure HB can do anything about this at all, seems a WoW "issue". Well, by design now, of some sort. Or maybe just a bug that the timer keeps running even when the group is already killing mobs. It's not really an issue per se, as long as you are A) the tank yourself or B) the entire group is yours (5 bots). In my case, sometimes the tank is already far away or even dead because my healer starts moving after 20-25 secs. Now that I know what it is, I just follow the tank manually for now until DB takes over.
Uhm its definitly fixable, be patient and let the Devs do their thing. the bug is just based on the fact its waiting for the LFG timer to stop, the fix would be something as simple as forcing the bot to follow the tank if he moves, just like before 7.0. This isn't an impossible problem, the devs are just focused on other aspects of the bots aside from dungeonbuddy atm because there are more important things to fix... You know like core files etc. Just be patient.
Not impatient at all, just wanted to let others know this is a minor issue now. Whether or not a fix can or will be made, it's fine by me. Most important for me now is to get the CR's up and running again (TuanHA en Oracle II for example). Too bad Mirabis stopped developing his though. Anyway; Dungeonbuddy has minor issues (not following tank but going it's own way sometimes - leaving the group before last boss - not accepting quests or not handing them in) but none are real problematic. Questing also works (almost) flawless; I do not have issues and have been questing 1-56 now without having to intervene.
anyone been able to 1-100 with any class at this stage? Not trying to stir any crap but just trying ot see if anyone has been able to afk - or the highest level they've been able to reach on a toon without issue? cheers
Its taking longer due to issues both on Honorbuddy's side and on Blizzards side, nothing we can do about it until shit gets resolved.
I think I found another bug in DungeonBuddy: When your group completes a dungeon and requeue without leaving the instance, the bot sometimes thinks its still the same instance if you get placed into the same dungeon Steps to reproduce: Queue for LFG Dungeon (queueing with 5x lvl 70 will nearly always put you into Utgard Keep) Clear the instance Requeue without leaving the instance Get placed into the same dungeon again -> Bot thinks its still the same instance and waits for the instance lockout timer to run out
The questing bot is bugged on priests in the undead starting zone. It just sits there instead of attacking the neutral mobs. I went ahead and made a lock instead since its just a caster i need, but i made it orc since that is currently working. Might want to look into it ^_^. figured it out, for anyone who runs into this issue with any caster class, go to your "class settings" and set whatever skill you have (i.e. smite, drain life, etc) to 100% so it will cast when the enemy is @ 100%. This will allow the casting that isnt happening.
