[Stable] Honorbuddy 2.0.0.3804

[Nesox]

CHANGELOG 2.0.0.3740 TO 2.0.0.3804

ADD - WoWMovement now supports 'timed' movement. Note: if you lock up the thread without pulsing WoWMovement.Pulse, your timed movements will NOT be stopped.
ADD - unit.MovementInfo has lots of new properties: IsFalling, MovingForward, MovingBackward, MovingStrafeLeft, MovingStrafeRight, MovingTurnLeft, MovingTurnRight, IsMoving, IsStrafing, IsSwimming, IsFlying, CanFly, IsAscending, IsDescending, JumpingOrShortFalling, FallingFar
ADD - BG bot now supports WSG, TP, BfG, and IoC.
ADD - BG bot will automatically re-queue a battleground, if it has been in the queue for more than 25 minutes.
ADD - It's now possible to add items to Forcemail in the 'ForceMail.xml' file in the root of hb.
ADD - the 'GrindTo' tag now has a Condition attribute wich you can use to set a custom condition instead of just Level.
More info: http://www.thebuddyforum.com/mediawiki/index.php?title=Honorbuddy_Profile_Tag:_GrindTo

ADD - It's now possible to pickup quests from items with the PickUp tag. 
example: <PickUp QuestName="The Howling Wind" GiverType="Item" QuestId="9861" GiverId="24504" />

FIX - Will no longer start doing other things after looting if it's supposed to skin a mob. It also won't run away before looting a mob.
FIX - BotEvents.Player.OnMobLooted is now fired when the player loots a mob.
FIX - Honorbuddy will no longer try to skin Herbable/Minable mobs.
FIX - Mounts such as the 'Headless Horseman's Mount' should now be properly be recognized as both a flying/ground mount
FIX - Overall performance should be ALOT better.
FIX - WoWPartyMember - some information was being read incorrectly, and causing bad data to be returned. This has been fixed.

For Bugreports! Make sure you make a new account unless you already got one:
Buddy Bugtracker Main Page

[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 Instancebuddy and ArcheaologyBuddy, do not use the old IB/AB - they won't work.

In order to use Hb your WoW client must be fully (100%) patched

Download Here: Honorbuddy 2.0.0.3804







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