Honorbuddy v2.5.11917.754 You must do a fresh install with this build to avoid any issues.HelpDesk: "Clean Installing" Honorbuddy There have been major API changes made with this build. There might be store products that are not updated for this build yet. If you have problems, the first step is to disable use of all third-party products.How to disable Buddy Store streaming [SIZE=+1]Changelog[/SIZE] Code: New features: -------------- * DungeonBuddy - Added movement randomizations to tank following logic to help eliminate stacking of bots (HB-811) - Flying mount is now used when doing vendor runs. (HB-843) - Raid following logic has been improved. (HB-1117) * ProfessionBuddy - InBagCount will now account for items in personal and reagent bank (HB-1378) Api Changes: -------------- - Removed SkillLineAbility.OrangeSkillLevel. Tradeskills are orange when the level in the profession is < SkillLineAbility.YellowSkillLevel. (HB-1412) Bug fixes: -------------- * Core - Corrected Protected Items.xml's entry for Golden Sansam Leaf. (HB-1431) * DungeonBuddy - Updated the script and profile for Upper Blackrock Spire dungeon (HB-1350) - Fixed a bug where tank would idle at a boss instead of pulling it. (HB-1401) - Blocked the inside of the building that contains the portal to Lost City of Tol'vir to prevent bot from running through it to get to other side of building (HB-1405) - Lost City of Tol'vir: Fixed a mesh issue by the stairs to Lockmaw (HB-1406) - Fixed bug where Tank would idle when in combat with a NPC that is attacking NPC (HB-1407) - Fixed a problem where Dungeonbuddy would idle after dungeon completion when running a full group of bots and partyMode leader was not the tank (HB-1383) * ProfessionBuddy - CastSpellAction: no-longer attempts to detach same lua handler for UNIT_SPELLCAST_SUCCEEDED twice (HB-1399) - Fixed a compile error in Mining-Herb (1-600)flying-GB2.xml (HB-1411) * Questing - Fixed a problem where QuestBot would stop if turnin/pickup NPC despawned or was killed during turnin/pickup process. (HB-1414) [SIZE=+1]Reporting Bugs[/SIZE] Please report confirmed 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 [SIZE=+1]Releases[/SIZE] Honorbuddy: Installer (recommended) / Zip Honorbuddy Deutsche Version: Installer (recommended) / Zip→ For German users, this Honorbuddy client must be used—the other Honorbuddy version(s) will not work for you. ← Ref: Honorbuddy Deutsche Version - Pressemitteilung Honorbuddy Asian Version: Installer (recommended) / Zip → For Asian users, we suggest using this client as it connects to our HK auth servers which results in faster login time and consistent connection ← [SIZE=+1]Requirements[/SIZE]The Buddy Dependency Wizard will install these requirements for you, if needed. Of course, you are welcome to install them manually if so inclined. v4.5.1 Download Microsoft Visual C++ 2012 Redistributable Package (x86) from Official Microsoft Download Center [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 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!
[size=+1]Currently Known Bugs[/size] HB-843: Prefer using flying mount when doing Vendor runs HB-1286: ProfileManager gets confused if Botbase is changed HB-1302: WoWSpell.CanCast reports false when moving and shooting steady shot HB-1323: Problem with Kill-form of <Objective> HB-1325: HasItem() does not check for Items in the "invisible" WoD Bag HB-1331: MyCTM fails to move if only "Z" value changes, causing profile termination HB-1335: HBcore and Singular fighting over Druid Travel Form or Cat Form HB-1337: Serious lagging on Battlegrounds HB-1340: Unable to turn in quest while under water to 'dead' NPC HB-1348: "Error Trying to Save Settings File" File Already Exists HB-1353: Settings files are still being corrupted HB-1356: Honorbuddy sometimes sells the 'last' bag HB-1361: Map changes/teleports/hearthing cause GreyMagic errors HB-1391: AutoEquip does account for gem stats HB-1395: Singular throwing exceptions when Priest tries to use Lightwell in dungeons HB-1409: Stormstout Brewery: Problem handling Hozen Party Animal HB-1410: Vortex Pinnacle: Not taking slipstreams after killing boss HB-1423: ProfessionBuddy taking an excessive amount of time to cancel auctions HB-1425: Druid Cat Form Spamming on/off HB-1432: DoWhen: Throws exceptions when profile-provided predicate doesn't properly check for nulls HB-1441: ProfessionBuddy stops when it should learn fishing skill from Trainer HB-1457: ProfessionBuddy crashes WoWclient on SwitchCharacter [size=+1]Singular-specific issues[/size] After a discussion with Bobby53, we are no longer capturing issues here against Singular. Bobby53 has a very thorough and efficient work flow that is independent of the HBcore bug tracking process. We will just need to give him time to 'catch up' to the changes imposed by WoD. He is well aware of all the issues that people have been reporting, and just needs time to address them. Ref: Singular threadRef: Singular - Status of Updates for pre-WoD [size=+1]Bugs in danger of being discarded, due to lack of details[/size] [size=+1]Awaiting Confirmation[/size] [size=+1]Cannot reproduce[/size] Bugs marked as "cannot reproduce" are usually due to problems with your particular Honorbuddy installation. For instance, third-party products that are not working correctly—you should disable Buddy Store streaming for all products. Another cause is interference from external programs or addons. Your best way to recovering from this always starts with a clean install. If you continue to experience problems after conducting a 'clean install', and disabling the streaming of all products from the Buddy Store, you should seek help in the Support forum with your log that captures the issue. HB-1205: In Scenarios, toons are not following the tank "Have not been able to reproduce so assuming it's been fixed until reported again" HB-1408: Gatherbuddy2 not using Swift Flight Form in non-English client "We can't reproduce this. Tried with French WoWclient and it managed to use flying form/travel form " [size=+1]Not a Bug / Won't fix[/size] [size=+1]Duplicates[/size] HB-1422: Gatherbuddy throwing exceptions trying to load profile from ProfesionBuddy "Duplicate of HB-1025" [size=+1]Already repaired for next drop[/size] HB-1025: Gatherbuddy2 needs to handle profiles with no hotspots "Gatherbuddy2 will properly state the reason why a profile could not be loaded instead of showing an exception message." HB-1360: Invisible wall inside Gate of the Setting Sun "Gate of the Setting Sun: Fixed the invisible wall issue" HB-1388: Enable profile line numbers to be captured in streamed profiles? HB-1421: Scholomance heroic issue "Scholomance: Tank will no longer idle at Lilian Voss until she despawns after completing the encounter." HB-1424: CollectItem-form of Objective fails when toon has mob aggro but no mobs to fight "CollectItem-form of Objective will now collect objects when stuck in combat with no mobs to fight" HB-1446: Dungeonbuddy has problems reaching vendors inside buildings "Reverted the change where Dungeonbuddy will use flightor for vendor runs due to problems with reaching NPCs that are indoors." HB-1451: Passing Group Leader to a Tank "Fixed a bug where a tank would idle because of Passing group leader to a tank" Notes: This release is not optimized for performance. Performance optimizations will be addressed after whittling down the severe bugs in our list of known bugs. The bugs listed here are only a fraction of our bug work load. Many bugs we must address are internal, or not for public consumption. The previous 'Known Bugs List' is here. List of Honorbuddy Releases
[size=+1]Post dispositions[/size] These posts have been archived for the reasons stated here. Problem should be resolved in the Support forum Your problem can probably easily be resolved with a clean install, and turning off the use of all third-party products—including all products from the Buddy Store. There is a strong chance the repair for your issue resides in the Honorbuddy:HelpDesk. However, if you are unable to resolve the problem using these resources, then by all means make a new post in the Support forum. And please, don't forget to attach your full, unedited log that captures the issue. Smix Using third-party products that have not been updated for pre-WoD Once again, we draw your attention to the bright red letters in the first post that are easy to overlook Missing critical information (logs, screenshots, etc.) Your post may also be archived "without comment" for this reason. The posts listed here made an effort to report the problem, but the information provided was insufficient to create a bug report (e.g., wrong log, partial log, screenshot needed, etc) Didn't check the "Known Issues" list Log is not against the current release
Hi, HBL0V3, Please see the first post. We only look into issues that have the full log attached. In your case, we will need the profile, also. cheers, chinajade
Hi again, Treek, It sounds like you are referring to our response here. The senior staff member's response to HB-1306 was given here. The staff member actually identified Spyware installed on your system. This spyware must be removed. We strongly believe he is correct, as you are the only one experiencing this problem. But, you should go work this problem in the Support forum, as this is clearly a problem with your installation, and not an Honorbuddy bug. If you do open a Support forum thread, they will need both your Honorbuddy log, and the WoWclient crash log from the same event. cheers, chinajade
Hi, Studio60, The largest gap we find in the log you attached is 10 seconds as you are traveling to the digsite: [11:20:59.163 D] Activity: Moving to the digsite [11:21:08.881 N] (Singular) PerfMon: FPS:97 Latency:113 [11:21:18.932 N] (Singular) PerfMon: FPS:98 Latency:113 [11:21:28.975 N] (Singular) PerfMon: FPS:92 Latency:113 [11:21:39.045 N] (Singular) PerfMon: FPS:89 Latency:113 [11:21:49.112 N] (Singular) PerfMon: FPS:100 Latency:113 [11:21:59.114 N] (Singular) PerfMon: FPS:103 Latency:113 All your looting takes less than 1 second: [11:25:20.303 D] Activity: Looting Archaeology Find [11:25:21.625 D] Interacting with Vrykul Archaeology Find (GameObject Id: 207189) ... [11:26:45.401 D] Activity: Looting Archaeology Find [11:26:46.661 D] Interacting with Vrykul Archaeology Find (GameObject Id: 207189) ... [11:28:09.686 D] Activity: Looting Archaeology Find [11:28:10.996 D] Interacting with Vrykul Archaeology Find (GameObject Id: 207189) Your log does not demonstrate the problem you describe. Please go to the Support problem to have the issue investigated if it happens again. This log provides no evidence of an Honorbuddy bug. cheers, chinajade [size=-2]Ref: Studio60's original post w/log[/size]
Hi again, Treek, You're absolutely right, we miscorrelated your failure mode to the wrong bug report. We apologize for that. We have now opened HB-1457 ("ProfessionBuddy crashes WoWclient on SwitchCharacter") against this issue. We can think of no work-around for the issue at the moment. cheers, chinajade
Hi, FadetoGrey, Yes, GoThruPortal was modified a few builds ago to deal with portals that transport you without affecting a zone change. There is an example of one of these toward the end area in Mount Hyjal that deals with Ragnaros. If you would like to report a bug, we will need a full log of the event please, along with what ever profile fragment can repeat the issue. cheers, chinajade
I am aware of the problem with the log. But without a log my problem would have been immediately disregarded. The "Interacting with..." log entry appears in the HB client as soon as the Gameobject spawns. But the character then does nothing for about 64 seconds until he finally interacts with it. He also does not react to being attacked during this time so the combat mechanics are not taking over. After the fragments have been looted, the bot resumes his work. I tried it with two other characters. One with the same ingame addons and one without any ingame addons. The result is the same. The log states he is interacting, the ingame action happens 64 seconds later. Another character, same addons View attachment 4748 2014-11-05 17.08.txt Yet another character, no addons View attachment 7396 2014-11-05 17.18.txt
No, there is no bug, the behavior is great! I have find out my issues with it. That what i only need is to have the oportunity to adjust the yards of the length vector more than 15 which is the default. In any way, tnx for the reply
Hi! I am using the questbehavior GoThruPortal and I notice that I get an error in Honorbuddy saying: [GoThruPortal-v1728(warning)] Seems we missed the portal. Is Portal activated? Profile needs to pick better alignment? Even though it did went through a portal. Everything is working fine though, it's just this error but it has no consquences, only showing up. This only happens when moving from inside the dungeon to the world. From world to inside the dungeon ThruPortal is working fine! Here is a log: View attachment Portal Log.txt Already tried changing the WoW Coordinates but I doubt that the issue. I have a run waypoint right in front of the portal and the X Y Z coordinates of the ThruPortal 4 yards away from the runcode.