Changelog 2.0.0.5462
Patch 4.3 Update
General
------------------
* WoWFishingBobber -> IsBobbing works
* Item related plugins, features etc. should be working properly again
* Queueing for BG works again
* Movement info has been updated properly.
* Quest statuses have been fixed
* Creature cache info has been fixed
* Skill stuff has been fixed properly.
* Item cache info has been partially fixed. Need confirmation.
* Honorbuddy should now properly ignore "Mutilate" and "Mutilate Off-Hand" in the spell book as a learnable spell. (Causing trainer bugs) Thanks Blizz!
* An issue with "rotation" API on objects has been resolved. This may have been the cause of some strange issues with the facing of units not updating properly.
* "Learn Flightpaths" is disabled until further notice. We will re-enable the functionality once we figure out the best way to deal with the new flightpath learning.
API Changes
------------------
* SpellManager.Spells is now a SpellCollection object. (Inherits from Dictionary<string, WoWSpell> to provide backwards compatibility) When accessing this with an invalid index (SpellManager.Spells["An Invalid Spell"]) it will throw an exception with a useful error message.
* Unit.CurrentEclipse has been changed to return an int, instead of uint. This is to fix a small bug. Eclipse power is -100 through +100. Documents provide details.
* WoWSkill constructors are now internalized. You can no longer create one via the native memory pointer. (This is due to changes in WoW)
Gatherbuddy2
------------------
* GB2 will now ascend to sky while waiting for res sickness.
Quest Behaviors
------------------
- COLLECTTHINGS (Chinajade contrib) --
- Fixed a problem where the behavior would vascillate about mobs at the edge of the collection distance
- Fixed a problem where targets were being prematurely auto-blacklisted while on foot (i.e., "taking too long to reach the target")
- Enhanced pathing such that it no longer 'backtracks' to a hotspot, if the hotspot was passed on the way to a target
- The hotspot-form of CollectThings now accepts a name as an attribute for each hotspot (<Hotspot Name="Cathedral Square fishing dock" ...>). This is useful for debugging a profile. The name is also used to inform the user (via the HB status line) of the current local destination while the behavior is running.
- The hotspot-form of CollectThings now allows a 'randomize starting' position attribute (<CollectThings RandomizeStartingHotspot=true/false...). This is useful if the profile will be run in a high-trafficed area such as Stormwind/Orgrimmar. It 'spreads out' all toons using the same profile at the same time to remain low key to the server population.
- The hotspot-form of CollectThings can now (optionally) limit which hotspots are selected as starting points for the behavior (<Hotspot StartPoint="true"...>). You may mark more than one hotspot as a 'StartPoint'. These will be used to select a starting point when RandomizeStartingHotspot is true. If no hotspots are marked as "StartPoint" and RandomizeStartingHotspot is 'true', then all hotspots will be considered.
- KILLUNTILCOMPLETE changes (from Kickazz006) --
- Mage pull spell now spelled correctly ("Frostbolt")
- Priest pull spell changed from "Shoot" to "Smite"
- Warlock pull spell changed from "Curse of Agony" to "Shadow Bolt"
- DEATHKNIGHTSTARTWAITFORPATROL (Chinajade contrib) --
- Added additional user feedback (and debug output) to try to isolate why this behavior seems to fail for some people.
- Ref: http://www.thebuddyforum.com/honorbuddy-forum/support-issues/32321-dk-starting-zone.html#post342285
If get this when you try to login on the bot:
Honorbuddy does not support the currently active 'gxAPI' please change it to 'D3D9'
Then you need to do this:
Open your Options->Advanced->Graphics API make sure it's set to DirectX 9 if it isn't change it and restart wow then restart and login on the bot again.
In order to use Hb your WoW client must be fully (100%) patched
Download Here: Honorbuddy 2.0.0.5462
edit: Use the CollectThings Behavior attached if you plan to quest!
