CHANGELOG 2.0.0.3895 TO 2.0.0.3956 Code: ADD - WoWPlayer.Minions - Returns a list of minions belonging to the player (excluding non combat pets), pet's/totems/various guardian characters ADD - WoWUnit.IsTargetingAnyMinion - Returns a boolean indicating wheter this mob is targeting any of the local players minions. (pet's totems guardians bloodworms etc..) ADD - Profile tag 'Vendor' now has a new attribute - 'Entry2' - This allows you to specify a 2nd entry for the same NPC. This is especially useful for worgen NPCs, who have 2 different entries, depending on their transformation state. ADD - WoWUnit.IsBeast, IsDragon, IsUndead.. etc. added. ADD - StyxWoW.Me.IsActuallyInCombat - A temporary workaround to WoW's combat bug. - This is experimental. Use at your own risk. ADD - CustomForcedBehavior has a bunch of new methods exposed for retrieving, and validating XML attributes for profiles. This should allow for consistent checking across all behaviors, thus, making profile writer's lives a bit easier. (Kudos to chinajade for the original implementation) ADD - Experimental stuck handling added. - If you use this, please, report all bugs. Complaints will be ignored, unless valid. [Enabled by default. See General Settings tab] ADD - Experimental stuck handler will create a global blackspot file - DO NOT EDIT IT MANUALLY. This file is NOT for profile blackspots. This is for global world 'stuck' areas. They are created automatically. ADD - BlackspotManager class - Allows CC/Plugin developers to add blackspots at runtime. - Global blackspots may not be modified, but may be 'read'. FIX - Bugsubmitter works again, it no longer uses the first line multiple times, when pasting logs on pastie. FIX - Should no longer ignore being attacked by players of the opposite faction when grinding/questing etc. Default include target's filter now handles both units and players in combat with the local player and/or any of it's minions. FIX - MailFrame.SendMail should no longer throw exception if you pass null for attachmentItems. FIX - Should no longer not run the handler for LOOT_OPENED causing the bot to wait 10 seconds for the 'we have looted this thing' boolean to be set, Now waits until the LOOT_OPENED event is raised in the loot branch and then handles it accordingly. FIX - WoWUnit.Auras/PassiveAuras/ActiveAuras and Debuffs should work properly now. FIX - Should no longer ignore targets in combat with your pet. FIX - Quest bot should now loot when in 'bugged' combat. FIX - Should no longer wait 1.5s after killing a target, while in BGs. [The wait is to resolve some WoW lag issues when grinding] FIX - All injection routines have been modified to throw exceptions if invalid arguments are passed, that could cause WoW to crash. - This may cause issues with certain plugins, but should automatically resolve itself. CHANGELOG FOR ArchaeologyBuddy Code: *FIX* It should properly land after getting attacked before landing *FIX* It should properly land on all digsites now *FIX* It should properly move out of bugged spot in Nek'mani wellspring CHANGELOG FOR Gatherbuddy2 Code: *NEW* GB2 will now blacklist nodes that it failed to gather after 3 attempts *NEW* Added an option to ignore elites or not *FIX* Small pauses between hotspots is fixed *FIX* Elite mob detection has been fixed *FIX* Fixed issues with Guild Vault behavior not working for some cities *FIX* Repair and Mail runs should work properly now. *FIX* Blackspots in profiles works properly now. GB2 will not go for nodes that are inside a blackspot area of the current profile. Code: [SIZE=3][COLOR=red]If you are getting this exception: Invalid Executor, Styx.Helpers.CharacterSettings threw an exception, or [/COLOR][/SIZE][SIZE=3][COLOR=red]Error - Endscene hook failed: Value cannot be null. Parameter name: EndSceneProc passed to Executor constructor was invalid, or[/COLOR][/SIZE] [SIZE=3][COLOR=red]something similiar to that. Then you need to do this /run print(GetCVar('gxApi'))[/COLOR] [COLOR=red]open the chatbox in wow copy paste that press enter. If it prints D3D9 ure all good if it says D3D11 you have to open your Config.wtf file and edit this row: SET gxApi "D3D11"[/COLOR] [COLOR=red]Make sure it looks like this: [/COLOR][COLOR=red]SET gxApi "D3D9"[/COLOR][/SIZE][SIZE=3][COLOR=red] [/COLOR][/SIZE] This Version includes ArchaeologyBuddy, Gatherbuddy2 and Instancebuddy do not use the old AB/GB2/IB - they won't work. In order to use Hb your WoW client must be fully (100%) patched Download Here: Honorbuddy 2.0.0.3956 Starting from the next Honorbuddy release and for all future releases its required to post your bug reports on our Bugtracker tool. That means that we wont accept bug reports on forum The Hb release tread will remain locked link:Buddy Bugtracker Main Page So,in order to be able to use this tool you have to register 1)Press the big blue "Open a new account" button and then you have to fill in your email here 2)Next step is to visit your inbox for our confirmation email 3)Go back at Bugtracker's main page fill your info and you will be able to see this 4)in order to create a new bug report you have to choose the "New" option this action will lead you to product selection page you have to choose Honorbuddy [v2]: Honorbuddy 2 if you want to report an Hb bug or Third Party Utilities if you want to report an Instancebuddy bug 5)now you are able to see this page(if your selection was Hb2) or this(if your selection was Third Party Utilities) 6)Final steps are to give us as more information as possible about the bug what steps we have to follow in order to reproduce it on our machines and your log as attachment and then hit the Submit button link:Buddy Bugtracker Main Page