Honorbuddy v2.5.11837.752

[size=+1]Currently Known Bugs[/size]

• HB-1286: ProfileManager gets confused if Botbase is changed
• HB-1302: WoWSpell.CanCast reports false when moving and shooting steady shot
• HB-1322: Honorbuddy ignoring neutral quest mobs that are part of <Objective>
• 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-1337: Serious lagging on Battlegrounds
• HB-1340: Unable to turn in quest while under water to 'dead' NPC
• HB-1342: RunLUA causes the WoWclient to close
• HB-1348: "Error Trying to Save Settings File" File Already Exists
• HB-1350: DungeonBuddy: rework Upper Blackrock Spire
• 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-1378: ProfessionBuddy: Expand InBagCount() to account for profession bank?
• HB-1380: DungeonBuddy crashes (related to graphics load?)
• HB-1383: DungeonBuddy recognizing completed dungeons, but not leaving them
• HB-1391: AutoEquip does account for gem stats
• HB-1395: Singular throwing exceptions when Priest tries to use Lightwell in dungeons
• HB-1399: ProfessionBuddy emit wrong messages due to handler detach failure
• HB-1405: Lost City of Tol'vir: Problems with vendor runs
• HB-1406: Lost City of Tol'vir: Stuck on stairs otw to Lockmaw
• HB-1407: Lost City of Tol'vir: Stuck in combat at Enslaved Bandits
• HB-1408: Gatherbuddy2 not using Swift Flight Form in non-English client
• HB-1409: Stormstout Brewery: Problem handling Hozen Party Animal
• HB-1410: Vortex Pinnacle: Not taking slipstreams after killing boss
• HB-1411: ProfessionBuddy: "GetMail->CheckNewMail appears to be unused"

[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.

You can find Singular's current status here:

Singular - Status of Updates for New Version ​

​

[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-1334: Gatherbuddy attempting to mine as Druid while in shape-shifted form
  
  "Tried with a lvl 90 druid with both glyph of stag and without. All working good on my end"​
• HB-1341: Dungeonbuddy is not releasing corpse
  
  "Can't reproduce so probably Overcome by Events (ObE)."​
• HB-1360: Invisible wall inside Gate of the Setting Sun
• HB-1368: ArcheologyBuddy tripping inactivity timer
  
  "Been running AB for a day and couldn't reproduce this"​

[size=+1]Not a Bug / Won't fix[/size]

• HB-1159: TradeskillAction throwing exceptions
  
  "This is from the open-sourced version of PB which is outdated and no-longer maintained. "​
• HB-1299: GrindUntil Condition not terminating
  
  "The original submitter reports this is no longer a problem in '.752. The bug has been closed as 'Overcome by Events' (ObE)—the problem was probably repaired by a fix to another bug."​
• HB-1306: Reports of HB causing WoWclient crash and BSoD
  
  "The WoW crash log contains no traces of anything Honorbuddy would touch, but it contains a DLL that we have seen on previous reports of crashes (4-5 reports in 5 months): rlls.dll. This is some spyware:
  http://deletemalware.blogspot.dk/2011/04/remove-relevant-knowledge-uninstall.html"​
• HB-1374: ProfessionBuddy queues for Battlegrounds if stop/started while cooking&fishing
  
  "The secondary bot was set to BGBuddy and the current PB profile is responsible for setting the Secondary bot to the correct botbase."​
• HB-1375: ProfessionBuddy's AHBot not undercutting properly?
  
  "Working as intended. Cancel the undercut auctions first by running 'Cancel Auction' to make room for new auctions."​
• HB-1382: InteractWith: Not defending itself if attacked while trying to interact
  
  "Caused by having framelock disabled."​
• HB-1396: ArcheologyBuddy unable to locate any digsites
  
  "The user is possibly using an addon that interferes with AB. Even when all 4 digsites are blacklisted AB will still write them to the log with a 'blacklisted'' annotation. This article should help the user isolate the source of the problm: BosslandGmbH:HelpDeskrograms that Interfere with BosslandGmbH Products"​

[size=+1]Duplicates[/size]

[size=+1]Already repaired for next drop[/size]

• HB-1177: Singular's "Pull More" appears to be pulling mobs on <AvoidMobs> list
  
  "Until fixed, workaround is to set Class Config setting PullMoreUsage to None.
  Added support for AvoidMobs list checking based on CurrentProfile"​
• HB-1224: Mail is using evil version of 'Sleep'
  
  "MailFrame.TakeAttachedItems, OpenAllMail() and OpenAllMailCoroutine methods are now marked as obsolete. To take their places, 3 new coroutines, MailFrame.GetMailAttachmentsCoroutine, OpenAllMailCoroutine and OpenAllMailFromCoroutine have been added."​
• HB-1316: Honorbuddy Updater throwing exceptions
  
  "Starting from this version, Updater will now properly ask for admin privileges when UAC is enabled."​
• HB-1317: Honorbuddy ignores quest mobs fighting other mobs
• HB-1318: Honorbuddy is not skinning
  
  "WoWUnit.CanSkin no-longer checks the skill level since mobs can be skinned at any level now."​
• HB-1345: <Objective> no longer handles "group kill credit" correctly
  
  "CreatureCacheEntry has been updated to work in WoW 6.0"​
• HB-1373: PerformTradeSkillOn throwing exceptions trying to Enchant
  
  "Repaired a NullReference exception in PerformTradeskillOn"​
• HB-1381: ProfessionBuddy running AHBuddy just opens and closes the AH frame
  
  "Vendor frames had been changed to close the frame at the start to ensure the frame is opened at correct NPC.
  Unlike normal Vendors, it does not matter which Auctioneer the bot visits, so its fine to leave an Auctioneer's frame open.
  Thus, we've now made Auctioneers an exception to the Vendor 'close frame' machinery.
  The result is 'Buy Item On AH' and 'Cancel Auction' will no longer close the auction frame on start."​
• HB-1387: InteractWith: Throwing exceptions in attempts to buy items
• HB-1389: ProfessionBuddy repeatedly opens and closes the Vendor frame
  
  "'Sell Item' and 'Buy Item' will no longer close the vendor frame on start. This was added to ensure the vendor frame was opened at the correct NPC however it been reverted since this change broke some profiles."​
• HB-1393: Singular throwing IndexOutOfRange exceptions when using PullMore
  
  "Appears to be bug in code assessing whether an objective within a quest is complete. Fixed in next release of Singular"​
• HB-1394: Herbalism & Mining should ignore level requirements
  
  "All herbs and minerals will be shown in the Gatherbuddy2 GUI now as there are no required skills anymore."​
• HB-1402: Bgbot Isle of conquest & AV
  
  "Fixed a bug where the bot may stand still in the start area of IoC."​
• HB-1403: InstanceTimer is using wrong default value
  
  "InstanceTimer's default value for 'Timer' has been changed to 360000 (6 mins) to agree with WoWserver changes. (was 750000—12.5 mins)."​
• HB-1404: Updated Protected Items.xml
  
  "Updated ProtectedItems.xml. All bags should now be protected. Added harvestable herb and ore 'pieces'. Several new pets added."​

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.

 

[size=+1]Post dispositions[/size]
These posts have been archived for the reasons stated here.

Problem should be resolved in the Support forum

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

 

You can use the following to dismount.

Code:

[COLOR=#333333]<CustomAction Code="await CommonCoroutines.Dismount();" /> [/COLOR]

CommonCoroutines.Dismount is a coroutine and if you would like to know more about how to use them in HB check this link https://www.thebuddyforum.com/honor...62972-using-coroutines-logic-development.html

 

Hi, Jordi1104,

Your log shows your problem is with a third-party product—please contact the author for solutions.

cheers,
chinajade


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

 

Hi, MNC,

We'll need your full Honorbuddy log that captures this event please.

cheers,
chinajade


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

 

Hi, StarWash,

You can find the latest status of bugs here:

'.752 Known Bugs List​

This is all the information that is available. We don't give out ETAs.

cheers,
chinajade

 

Hi, Giwin,

Until this bug, the Kill-form of <Objective> has always handled 'group kill credit'. But, this only works for the built-in command, and does not extend to quest behaviors.

cheers,
chinajade

 

Hi, Chemical, and thanks for the log.

This log does not demonstrate the problem. Since that particular bug is supposed to be repaired in .752, we must assume you observed the problem in an older version of Honorbuddy.

If the problem happens again with .752, and you've got a log of it, we'll be happy to take a look.

cheers,
chinajade


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

 

Hi, MNC,

This is a problem with a product you are streaming from the Buddy Store that has not been updated for pre-WoD yet.

Please disable streaming for all products from the Buddy Store, as described in the first post of this thread. We believe the problem is probably your selected Combat Routine, but not certain.

Since this problem is not an Honorbuddy bug, but a problem with your installation, please follow up to the Support forum, if you can't figure it out.

cheers,
chinajade


[size=-2]Ref: MNC's log[/size]

 

Hi, WTB A Noob, and Psuwannanon and many thanks for those logs.

The number of work-arounds you have tried to solve the problem are very impressive... Kudos!

Alas, your problems are instances of:

• HB-1342: RunLUA causes the WoWclient to close

I've added your information to HB-1342, and the issue is marked "Critical". But, the workload is very heavy and there are a number of "Critical" issues in the queue.

Sadly, Kick's profiles are somewhat RunLua heavy, and it would not be practical to comment out the instance you are bumping into at the moment.

cheers,
chinajade


[size=-2]Ref: WTB A Noob's problem report w/logs[/size]
[size=-2]Ref: Psuwannanon's original post w/log[/size]

 

Hi, Sea, and thanks for the logs.

It appears your Honorbuddy installation is damaged, and I would love to know how it was accomplished.

Both logs say the same thing:

[09:45:37.650 D] System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeLoadException: Could not load type 'Styx.CommonBot.Routines.ICombatRoutine' from assembly 'Honorbuddy, Version=2.5.11837.752, Culture=neutral, PublicKeyToken=50a565ab5c01ae50'.
at PureRotation.Managers.HotKeyManager.BotEvents_OnBotStopped(EventArgs args)
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at Styx.CommonBot.BotEvents.
(Delegate , Action`1 , Object[] )
[09:45:37.651 D] [UserSettings-v1581(debug)] Bot stopping. Original user settings restored as follows...
Original Settings intact--no changes to restore.​

Honorbuddy doesn't provide an ICombatRoutine interface since the pre-WoD drop. You may have copied something from an old installation on top of .752. The culprit could also be a product you are streaming from the Buddy Store that has not been updated for the pre-WoD drop.

I'd try disabling the streaming of all Buddy Store products as described in the first post of this thread. If no joy, the second correction attempt would be a 'clean install', also described in the first post of this thread.

If you can't figure it out, please follow-up to the Support forum, as the problem is most definitely with your installation, and not an Honorbuddy bug.

cheers,
chinajade


[size=-2]Ref: Sea's original post w/logs[/size]

 

Hi, Sapcecake, and thanks for the log.

This is a profile problem, it turns out. In v3528 of the Honorbuddy profile pack, the quest ids for these quests were explicitly changed.

I'm not certain why, but my guess is the profile has been aligned with WoD (not pre-WoD) "starter zone" changes. I'll try to catch up with Kick, and find out why these changes were made.

For now, as a work-around, you may have to manually run the Blood Elf 1-5 quests.

cheers,
chinajade


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

 

Hi, Gleeky,

This appears to be how the profile you are running is supposed to operate.

cheers,
chinajade


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

 

Hi, Sea,

Again, Honorbuddy no longer provides the ICombatRoutine interface. A product you've got installed is trying to access ICombatRoutine, which no longer exists. This is not a problem with Honorbuddy, nor is it a problem with the Questing profiles you are trying to run. The problem lies in a third-party product.

If you need help isolating the problem, please follow up to the Support forum, as this is not an Honorbuddy bug.

cheers,
chinajade

 

Hi, Wuzzery, and many thanks for the log.

After looking through the log, we could find nothing untoward either. As such, we opened:

• HB-1380: DungeonBuddy crashes (related to graphics load?)

The only suggestion we have at the moment, is to install Honorbuddy to someplace other than your Dropbox.

cheers,
chinajade


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

 

Hi, Spy1337, and thanks for the log.

This is not an Honorbuddy bug, but a problem with your installation. You should do a clean install as described in the first post of this thread.

If you are unable to resolve the problem, you should follow-up in the Support forum since your problem is not an Honorbuddy bug.

cheers,
chinajade


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

 

Hi again, Gleeky.

We were able to catch up with Zakanator, and he provided enough details to write up this problem. Against this issue, we've opened:

• HB-1381: ProfessionBuddy running AHBuddy just opens and closes the AH frame

cheers,
chinajade

 

Hi, Lancer34,

Your Singular is throwing all kinds of exceptions indicating a damaged installation of Honorbuddy. The first step to recovery is to do a 'clean install' as described in the first post of this thread.

If you are unable to get it working properly, please follow up to the Support forum with a fresh log.

This is not an Honorbuddy bug—the problem is with your Honorbuddy installation.

cheers,
chinajade


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

 

Hi, Wullie,

Thank you for all the great details and the logs!

Against this issue, we've opened:

• HB-1382: InteractWith: Not defending itself if attacked while trying to interact

Sadly, we don't know of a work-around for it at this time. Are you by any chance using the ElvUI addon? If so, can you disable it, and see if the problem persists?

cheers,
chinajade


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