Honorbuddy v2.5.9937.728

[raphus]

Honorbuddy v2.5.9937.728


Changelog

New features:
--------------
  * Character Manager
    - Auto Equip will now wait slightly before equipping items and rolling on items. (HB-381)

  * Core
    - Auto Equip and Talented has been rewritten and integrated with Honorbuddy. They should now work better, more efficiently and with less set up required. (HB-171)

Api Changes:
--------------
    - ItemInfo.SellPrice should now be correct for all cases. (HB-450)

    - Fixed an issue where WoWUnit.HasAura(int) would return true for auras with ID 0. (HB-551)

Bug fixes:
--------------
  * ArchaeologyBuddy
    - Fixed an issue where AB may get stuck forever while trying to loot bugged artifacts. (HB-537)

  * Character Manager
    - Auto Equip should no longer try to equip items that are unique equipped if we already have one equipped. (HB-375)

    - Classes should no longer roll need on items they can't use. (HB-399)

    - Improved logic for needing on loot rolls (HB-421)

    - Monks should now properly equip better weapons and roll on better weapons. (HB-426)

  * Core
    - Fixed an issue where the bot would write strange "FormatException" log messages. (HB-549)

    - Fixed an issue where mailboxes were not properly blacklisted. (HB-445)

    - Npc database has been updated which should contain all npcs in the world. (HB-567)

  * DungeonBuddy
    - Fixed an issue where bot would sometimes get stuck in Electrocutioner 6000 boss room in Gnomeregan (HB-354)

    - Tank will no-longer skip Tuten'kash in Razorfen Downs when 'Kill Optional Bosses' setting is enabled. (HB-368)

    - Slaves and workers in Slave Pens are no-longer chased after they start running. (HB-380)

    - Fixed an issue where followers would not interact with brazier in Blackrock Depths when they had a shadowtorch in bags. (HB-464)

    - Tank will now wait up to 7 seconds for followers to start drinking before pulling a boss if any of them have insufficient. Previous behavior had no limit on how long the tank would wait. (HB-468)

    - Fixed an issue where dungeonbuddy would run into a wall when trying to reach a vendor that can't be navigated to. (HB-555)

    - Fixed an issue where bot would idle at the Drahga Shadowburner encounter in Grim Batol. (HB-556)

    - Increase the avoidance radius of the 'Blight of Ozumat' polls that spawn at last boss in Thron of the Tides. (HB-557)

    - Tank will now complete the gauntlet event leading to last boss in Throne of the Tides faster (HB-559)

    - Fixed an issue in Wailing Caverns where bot would run back and forth while collecting serpentblooms for the quest 'Preemptive Methods'  (HB-560)

    - Tank will now always talk to Brann after Tribunal of Ages encounter is over in Halls of Stone (HB-561)

    - Dps will once again use harpoon launchers to shoot down Skadi in Utgarde Pinnacle (HB-562)

    - Tank will once again talk to Sinclari in the Violet Hold to start the encounter. (HB-563)

  * Navigation
    - The navigator's elevator logic has been improved. As a result Fizzcrank Airstrip elevator will now work properly. (HB-264)

  * QuestBehaviour
    - Fixed a bug with the InteractWith quest hehavior that occurred when the 'GossipOptions' was used and the NPC that was selected for interaction was in combat with the player (HB-536)

  * Questing
    - Fixed an issue with quest pickups where a "Could not find quest giver" error would be thrown up even while the quest giver is nearby (HB-541)

  * UI
    - Fixed an issue where quest data copied from Developer Tools was incorrect or incomplete. Additionally the 'GiverType="Item"' attribute is added to the <Pickup> tag whenever quest is started from an item. Also the UI will no-longer hang while retrieving data  (HB-508)

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​

Requirements

• 4.0
• Download Microsoft Visual C++ 2012 Redistributable Package (x86) from Official Microsoft Download Center
• Download Microsoft Visual C++ 2010 Redistributable Package (x86) from Official Microsoft Download Center

Reporting Bugs
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 that may be useful in tracking down the bug.

Enjoy!

 

[MaxMuster]

these two bugs fixxed?

HB-508 ("Developer Tools no longeer gets questgiver or turnin npcs")
HB-530 ("Honorbuddy "attacking" enemy pets on PVE Realms").

there is nothing in the change log

 

[MaiN]

these two bugs fixxed?

HB-508 ("Developer Tools no longeer gets questgiver or turnin npcs")
HB-530 ("Honorbuddy "attacking" enemy pets on PVE Realms").

there is nothing in the change log

HB-508 is fixed (last entry in changelog).
HB-530 is still on our todo list (but marked with highest priority).

 

[MaxMuster]

HB-508 is fixed (last entry in changelog).
HB-530 is still on our todo list (but marked with highest priority).

Thx for answer.

Last Question: Can we Delete AutoEquip2 and Talented2 from the Plugin Folder?

 

[MaiN]

Thx for answer.

Last Question: Can we Delete AutoEquip2 and Talented2 from the Plugin Folder?

Yes, you can safely delete them. They are only there to direct (confused) users into HB's settings.

 

[MaiN]

Not to be picky but, where is the "Replace" or "Don't replace loom items"? my 88 warrior just equipped every loom i had in my bag

New AutoEquip will not replace heirloom items if they are still working (ie. if your toon is under level 85 or 80 for old heirlooms). If it replaced items you had with heirlooms, it means the heirloom was better from its point of view.
If you feel this is wrong, can you equip your items again instead of your heirlooms, download the newest beta from here, and then send me the "AutoEquip" log that is produced after it has equipped the heirlooms again. This log file can be found in the same folder as your usual log files. I can then check and see why it is equipping the heirlooms.

Regarding the new autoequip - what do we do at lvl 80 with heirlooms ? i used to go into autoequip settings and tell it to replace heirlooms when i hit 80.

Heirlooms are automatically replaced once they stop working if we get an item that is better.

 

[MaxMuster]

Please add some more settings for Auto Equip, it hurts my heart seeing Assasination Rogues wielding axes while questing :C

Yes thats right, for AutoEquip we need a Option to Select the Weapon Styles we want.
For Example Cast: Two-Hand or One-Hand with Off-Hand
For Example Assasination Rogue: Only Dagger

etc.

 

[MaiN]

Please add some more settings for Auto Equip, it hurts my heart seeing Assasination Rogues wielding axes while questing :C

This is an oversight. Assassination rogues need daggers to execute some of their key rotation spells, is that correct? What about other rogue specs?
This will be addressed in a later update. I don't expect any settings to be necessary.

Yes thats right, for AutoEquip we need a Option to Select the Weapon Styles we want.
For Example Cast: Two-Hand or One-Hand with Off-Hand
For Example Assasination Rogue: Only Dagger

etc.

Weapon styles use sensible defaults. For casters it can switch between two-hander or one hander + off hand, depending on what is available and what combination scores the best.
Other classes use what you would expect them to use. In our testing we found no reason to expose weapon style in the UI.

 

[MaiN]

Right now rogue is the only class with this kind of problem.
If later on bot will switch between 2h and 1h+OH depending on stat combination that would be awesome, except for tank specced warriors and pallies.

Only casters will switch between two handers and one hander + off hand. For classes that use their weapons, there is unfortunately no good way to compare different styles that will give sensible results, so for these we are forced to use one weapon style. This weapon style will be what the player has equipped (so fury warriors will dual wield 2-handers if the player has 2-handers already, otherwise it will dual wield one handers).
Assassination rogues need daggers in both hands while subtlety rogues need a dagger in main hand, and any weapon in off hand. Combat can use anything. Is that correct?

 

[MaxMuster]

Only casters will switch between two handers and one hander + off hand. For classes that use their weapons, there is unfortunately no good way to compare different styles that will give sensible results, so for these we are forced to use one weapon style. This weapon style will be what the player has equipped (so fury warriors will dual wield 2-handers if the player has 2-handers already, otherwise it will dual wield one handers).
Assassination rogues need daggers in both hands while subtlety rogues need a dagger in main hand, and any weapon in off hand. Combat can use anything. Is that correct?

What is with Fury Warrior? They can Equip 2 x 1 Hand or 1 x 2 Hand.
Same for Frost DKs...2 x 1 Hand or 1 x 2 Hand...and for Windwalker Monk the same...2 x 1 Hand or 1 x 2 Hand...

 

[MaiN]

What is with Fury Warrior? They can Equip 2 x 1 Hand or 1 x 2 Hand.
Same for Frost DKs...2 x 1 Hand or 1 x 2 Hand...and for Windwalker Monk the same...2 x 1 Hand or 1 x 2 Hand...

As I said, for those cases, it will use the users preference.

 

[MaiN]

Combat Rogues use Daggers in OH and Fist Weapons, Axes, Maces, or Swords in MH.

Combat should use any type of one handed weapon for both main hand and off hand. As far as I'm aware, this is how the behavior should be for combat rogues.

 

[highvoltz]

"Improved logic for needing on loot rolls (HB-421)"
= Nice job.


As for Dungeonbuddy, there is now almost 10 versions released with the bug on the bridge right before the last boss in Shado-Pan Monestary, it attempts to skip the group of mobs there, only leading to navigation trying to CTM to a spot on a hill next to the bridge. This causes the toon/tank to get stuck... And Dungeonbuddy cannot continue. It's my only beef and I've screamed about it for months. I don't need a log. It's pretty simple to identify/find.

Here is the exact spot, watch this video and skip to 22:13:
[video=youtube;HkC9mdJDf0Y]https://www.youtube.com/watch?v=HkC9mdJDf0Y[/video]

That bridge, on left... small mound "hill" on left... The bot continues to try to skip the mobs straight ahead and go around them to begin the fight. It's kinda stupid logic honestly. But it's so the boss doesn't get triggered. Either way it happens no matter what... and fighting the boss and mobs happens both ways. Straight through (manually) or around it... A spell kicks back the toons in dungeonbuddy group to those mobs. So either method... You fight them.

Are you sure you're using latest version of the script for this dungeon?
Perhaps you have the 'Custom Scripts Path' option set and it's using an older script version? I ran the instance about 5 to 6 times several days ago without any stucks here.

 

[MaiN]

did a fresh instal, but i am getting these error (and onces like this with any profile i try)

[UserSettings-v1294(error)] [MAINTENANCE ERROR: Error processing attribute 'GroundMountFarmingMode.']: Object reference not set to an instance of an object.
FROM HERE (NullReferenceException):
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet.<BuildRecognizedSettings>b__15(<>f__AnonymousType8`2 <>h__TransparentIdentifier10) in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 706
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
at System.Collections.Generic.List`1.AddRange(IEnumerable`1 collection)
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet.BuildRecognizedSettings() in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 701
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet.get_RecognizedSettings() in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 538
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet..ctor(Dictionary`2 changes) in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 458

[UserSettings-v1294(error)] [MAINTENANCE ERROR: Error processing attribute 'KillBetweenHotspots.']: Object reference not set to an instance of an object.
FROM HERE (NullReferenceException):
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet.<BuildRecognizedSettings>b__15(<>f__AnonymousType8`2 <>h__TransparentIdentifier10) in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 706
at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
at System.Collections.Generic.List`1.InsertRange(Int32 index, IEnumerable`1 collection)
at System.Collections.Generic.List`1.AddRange(IEnumerable`1 collection)
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet.BuildRecognizedSettings() in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 701
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet.get_RecognizedSettings() in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 538
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet..ctor(Dictionary`2 changes) in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 458

[UserSettings-v1294(error)] [MAINTENANCE PROBLEM]: Problems encountered with provided argument
FROM HERE (ArgumentException):
at Honorbuddy.Quest_Behaviors.UserSettings.ChangeSet..ctor(Dictionary`2 changes) in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 525
at Honorbuddy.Quest_Behaviors.UserSettings.UserSettings.BuildPresets() in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 353
at Honorbuddy.Quest_Behaviors.UserSettings.UserSettings..ctor(Dictionary`2 args) in c:\Users\Bas\Downloads\Honorbuddy 2.5.9937.728(1)\Quest Behaviors\UserSettings.cs:line 55

MaiN, i have problem with "user setting" in quest behavior.cs
this problem same as skmoonlight

i have the same problem

I pushed a beta with a fix to this issue. You can grab it here.

 

[Hawker]

Dungeonbuddy is not working. It wont vendor, and will stuck in town.

Please post a log.

 

[MaiN]

don't they benefit from a fast offhand due to the energy proc?

I don't know, but even if they don't, is that energy proc enough to warrant only using daggers? I can add support to weight sets so they take speed into account, but I don't know if it matters much.
I do know for assassination you need daggers to use Mutilate, so assassination rogues definitely need to only equip daggers; I'm just not sure about the two other specs.

* Character Manager - Auto Equip will now wait slightly before equipping items and rolling on items. (HB-381)

Did a fresh install and it is not rolling on the loot.. it says in log waiting 6 seconds to roll but it will not roll

Can you download the beta and use that, and if it happens again, send me the log and the AutoEquip log as well (found in the same folder as the regular log - it's only created on beta builds).

Also does this mean we can delete the talented and auto equip in plugins folder?


and btw mine rolls on items in dungeons just fine! great update

Yes, they can be safely deleted, and will be sooner or later.

 

[ShortRound]

This is the equipment guidance from Icy Veins with regard to rogues.

Assassination
As an Assassination Rogue, you will always want to use Daggers in both your Main-hand and Off-hand slots. Your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Combat
As a Combat Rogue, you will always want to have a 2.6 speed weapon in your Main-hand slot.
In your Off-hand slot, you can use a Dagger or a 2.6 speed weapon (the latter being viable thanks to

Combat Potency).

If you are dual-wielding 2.6 speed weapons, then your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Subtlety
As a Subtlety Rogue, you will always want to use Daggers in both your Main-hand and Off-hand slots. Your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Hope that helps.

 

[zeldrak]

This is the equipment guidance from Icy Veins with regard to rogues.

Assassination
As an Assassination Rogue, you will always want to use Daggers in both your Main-hand and Off-hand slots. Your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Combat
As a Combat Rogue, you will always want to have a 2.6 speed weapon in your Main-hand slot.
In your Off-hand slot, you can use a Dagger or a 2.6 speed weapon (the latter being viable thanks to

Combat Potency).

If you are dual-wielding 2.6 speed weapons, then your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Subtlety
As a Subtlety Rogue, you will always want to use Daggers in both your Main-hand and Off-hand slots. Your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Hope that helps.

^All the way, this.

On another note, as for the "new and improved" AutoEquip 2 and Talented being integrated into HB, what do the weight set developers do when they want to make their own weight sets like they did with the old AE2? I took a look at the new .xml files and they have both Talented and AE2 weights combined into a single .xml file. Are the developed weight sets from places like MaxDPS.com, AskMrRobot.com, and other places not compatible anymore? Also, could you post a list of updated weight set tags, such as the <DPS> tag, etc?

 

[MaiN]

This is the equipment guidance from Icy Veins with regard to rogues.

Assassination
As an Assassination Rogue, you will always want to use Daggers in both your Main-hand and Off-hand slots. Your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Combat
As a Combat Rogue, you will always want to have a 2.6 speed weapon in your Main-hand slot.
In your Off-hand slot, you can use a Dagger or a 2.6 speed weapon (the latter being viable thanks to

Combat Potency).

If you are dual-wielding 2.6 speed weapons, then your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Subtlety
As a Subtlety Rogue, you will always want to use Daggers in both your Main-hand and Off-hand slots. Your most damaging weapon should always be in your Main-hand slot (unless it only fits in an Off-hand slot).

Hope that helps.

This is very specialized and for end game raiding; for leveling, who cares if their combat rogue is using a 2.6 main hand weapon.
I will change rogue logic to always use two daggers for assassination/subtlety, but use any two one-handers for combat. From my research it does look like subtlety can viably use any two one-handers with a hemorrhage spec though, so I'm not too sure about that one.

 

[MaiN]

^All the way, this.

On another note, as for the "new and improved" AutoEquip 2 and Talented being integrated into HB, what do the weight set developers do when they want to make their own weight sets like they did with the old AE2? I took a look at the new .xml files and they have both Talented and AE2 weights combined into a single .xml file. Are the developed weight sets from places like MaxDPS.com, AskMrRobot.com, and other places not compatible anymore? Also, could you post a list of updated weight set tags, such as the <DPS> tag, etc?

They make a new class profile (which is the new term for the combined talent trees and weights). The current weight sets are from AskMrRobot.com, I believe. They need some adjustments for leveling though (stamina should be weighed as survivability is important), which is on my todo list.
As for weight set tags, they are always available here: Styx.CommonBot.CharacterManagement.WeighableStatType. We use the names of the enum members as the tag names.

EDIT: Also, multiple class profiles for the same specs are supported. They are selectable from the settings window.
EDIT 2: I misunderstood your question about the currently developed weight sets. No, they are no compatible anymore, but they should pretty easily be convertible to the new class profile system. If you do not specify a talent tree in a class profile, HB will not select talents for you.