What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Release] Honorbuddy 2.0.0.5800

Status
Not open for further replies.
raphus

raphus

Well-Known Member
Joined
Jun 17, 2010
Messages
2,094
Reaction score
492
Changelog 2.0.0.5800


​
If you are having issues, please make a clean installation of new build before posting any bug reports.

​
Bugfixes
--------------
* Flightor will now act better at mounting in water for druids and all other classes.


API Changes
--------------
* HasAura(id) has been added to WoWUnit.
* MountUpEventArgs now contains a destination arguement. Due to changes, new methods have been added to Mount class to allow a destination location. Several methods have been marked as Obsolete
* Druids and Shamans will now use Ghost Wolf and Travel Form as mounts in combat. Shamans will also use Ghost Wolf as a mount while indoors.
* Ghost Wolf and Travel Form are also counted as ground mounts until a ground mount is learned. (Low level support)


BGBuddy
---------------
* Mount Up Distance setting has been added. BGBuddy will only mount up if the destination is further away then Mount Up Distance.
Its suggested to be lowered for melee chars. Druids and Shamans will be using Travel Form/Ghost Wolf for distances lower then 60 yards if you are using Singular, so you can keep it a lot lower for shamans and druids.
* IoC alliance gates have been fixed. Characters should not get stuck at intact gates.
* IoC unloading/loading tiles in an infinite loop has been fixed.
* SotA logic has been reworked. It will move towards gates to attack/defend.
* It should now wait for the boat to dock in SotA before starting to move.
* Siege Weapons have higher prio at targeting now. It will go for siege weapons first if you are not getting attacked. It will also not attack siege weapons that are not driven.


Singular
--------------
* Druids and Shamans will be using Travel Form/Ghost Wolf if the destination is closer then 60 yards.
* Shaman specs (except Resto) have been reworked.

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.
Click to expand...

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

Honorbuddy doesn't support 64bit WoW client!

Download Here: Honorbuddy 2.0.0.5800 - Downloads - WOW Bot for PVP Leveling Gathering - Gatherbuddy & Honorbuddy Forums
 

Attachments

Last edited by a moderator:
moved to support...
 
Last edited:
Yay some BGbuddy fixes. Next we get IB2 right raphus? :D Atleast I hope so. :P
 
Thanks for the ghost wolf addition, looks a lot more natural!
 
awsome. !!! when i got on and it said i needed to update i was like wooo! db2! but noooo lol im so excited for it to come out soon
 
awsome update...but gatherbuddy really needs some love again:<
 
From the previous build I noticed that HB (GB2 actually) wasn't properly detecting stucks (sometimes it does, sometimes it doesn't).
Today I started leveling a new batch of accounts and the problem became even more apparent when every now and then I find toons running into walls using profiles that were always smooth as baby's bottoms...

I'd post a log but there's absolutely nothing unusual, except the toon is running into a wall and HB is not executing the unstuck routine.
Anyway, has anyone else had the same problem?
 
Toney001 said:
From the previous build I noticed that HB (GB2 actually) wasn't properly detecting stucks (sometimes it does, sometimes it doesn't).
Today I started leveling a new batch of accounts and the problem became even more apparent when every now and then I find toons running into walls using profiles that were always smooth as baby's bottoms...

I'd post a log but there's absolutely nothing unusual, except the toon is running into a wall and HB is not executing the unstuck routine.
Anyway, has anyone else had the same problem?
Click to expand...

I expierenced the same issue. Again, nothing useable in the log file.
 
fpsware said:
I expierenced the same issue. Again, nothing useable in the log file.
Click to expand...

Good thing it's not just me... bad thing, it's not just me... lol...
I forgot to add: If I manually unstuck it (without stopping the bot), it goes it's merry way.
 
Status
Not open for further replies.
Back
Top