Honorbuddy 2.5.7022.563

Honorbuddy 2.5.7022.563

Changelog

General
----------------
* Added GetObjectsOfTypeFast<T> to the ObjectManager. Allows faster lookups for those who know what they're doing.
* SpellManager.FindSpellByID now works properly with overrides
* Added a Console to the Dev Tools
* Added WoWGroupInfo.ClearWorldMarker. Allows you to clear a marker placed on the ground while in a raid.
* API throws exceptions when passed invalid parameters.
* Added WoWGroupInfo.PlaceWorldMarker. Allows you to place the ground-markers while in a raid. (Not in party, or solo!)
* Flightor will no longer mount if UseMount is False
* Removed dailies and Weeklys from the quest cache so you no longer have to delete it




BGBuddy
----------------
* BGBuddy no longer tries to move to the start location over and over, it will move there once, face where it needs to face, then wait until the start


Questing
----------------
* Completly Rewrote Quest Pickup and TurnIn
* No longer has to close the menu after accepting or turning in if it has to accept or turn in again from the same npc
* Improved the pickup and turnin quest status




AutoEquip
----------------
* Rewrote every weight set
* Rewrote how weapons where handled


Behaviors
----------------
* Many behavior changes

Requirements

.NET 4.0
Download: Microsoft Visual C++ 2010 Redistributable Package (x86) - Microsoft Download Center - Download Details
32 Bit version of wow, If you start it from the launcher make sure you go into the game preferences and select "Launch 32-bit client" otherwise just start "Wow.exe" file not the "Wow-64.exe" file


Problems
If you are having issues after installing Honorbuddy please run this tool to verify that you installed everything correctly.
Problems with a new installation of a buddy product?

Download : Honorbuddy


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.

 

good work

 

i wil try this the beta has problems with quest turning in etc. it keeps using the same npc that already had turned in

 

always autoequip problems. he equips green. but i have better blue weapons.
why my posts are completely ignored in the beta forum

 

Hmm, yeah... Autoequip was really buggy in beta, i hope you fixed it. Will try tomorrow. And questing was far from being stable...

 

I need your log of the auto equip.

 

wait 5 minutes you get much logs. in beta forum are logs from me too

View attachment 2720 2013-05-13 07.40.txt this is an old log

Here you can see all very good:
at the end i made experimental weapeon changing by active combat bot.
View attachment 4484 2013-05-16 22.16.txt

have fun


p.s. the best waepon from this, is the (Jinyugro?schwert) it's blue and has better abilities as the other 2 weapons. but it get scoring 0

 

have I offered geuptetet today and since the update is no longer profile of kickaaz lied down
can someone as old offered to give? Until it is repaired...

 

Keep crashing.. Access denied.

My key works for the previous build.

 

Thanks looking into it now.

 

Logging in...
Error - Endscene hook failed: The type initializer for 'MainDev.RemoteASM.RemoteAsm' threw an exception.

 

Telling me that it does not have a valid digital signature which is making my security in windows 7 freak out...

 

OK it is still doing the same as the last update i loge in and the bot loads then it fails. I tried 3 different attack routines with my Shaman and the same thing happened on all 3. Here is the log from when i tried to log in.

View attachment 91983

 

+1 hope autoequip gets fixed

 

I had the same issue, and this fix worked for me. HB is running perfectly now.

http://www.thebuddyforum.com/honorbuddy-forum/honorbuddy-support/119363-endscene-hook-failed.html

 

if there is more than one quest available from an npc, your character will endlessly talk to the npc and never accept the quest.

 

Can we revert to the old version for the time being ?

When questing, if the npc offers multiple quests the bot gets stuck and just opens/closes conversation in a loop

 

This is why you always wait a while before upgrading ^^

 

Its not like they put up a warning "There is a good chance this new update that is not needed will fuck everything up, please refrain from updating"
If it isn't broken, Don't fix it

 

this version seems to be pretty good i didnt notice one bugged quest npc guy yet that it keeps using the same quest npc guy.