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

[Stable] Honorbuddy 1.9.5.5 - QuestOrder

Status
Not open for further replies.
"Kill between Hotspots" has no effect in Questing mode. Meaning HB always kill anyone in los.
Also AvoidMob seems not working too or as result from above.
 
Last edited:
is there a code to avoid picking up certain quests?
PHP:
    <QuestBlacklist>
        <Quest Id="QUEST ID" Name="QUEST NAME" />
    </QuestBlacklist>

    <BlacklistedQuestgivers>
        <BlacklistedQuestgiver Name="NPC NAME" Entry="NPC ID" />
    </BlacklistedQuestgivers>
 
Last edited:
Btw, What about RaFQuesting ? It whould be awesome on fiend invite options.
Proper quest profile and both 1-60 in 30 hours! ;)
 
Ok, reading through 17pages would take some time, so Im just going to ask, did the bug in 1.9.5.5 is not turning in quests been fixed yet?
 
All the errors I'm getting are so simple and obvious I don't really know why I need to post a bug tracker or log. I mean, its stuff that is blatantly obvious.

-Targeting mob off and on over and over
-Standing take hits in the face
-Standing to close to mobs
-Running around a mob in a circle because its to close to the center of the hit box.

It seams like it wasn't even tested at all.

Are other people having these issues? Or am I doing something wrong? Can someone convince me not to give up hope on HB?

Using windows 7, enhance shaman with default profile and shamwow both used. farming in schola.
 
Yer its the same in the last build too, sure this is gonna get me banned soon.

Yea, ive seen several people get reported for this tonight already.

I would see team mates doing it, and other team mates would be telling people to report them. I cant bot BGs bc of this. Its a problem thats been going on for weeks now but still hasnt seemed to get fixed.

This is just one of the MANY problems HB has been having. All of which are easily noticeable and im surprised we havnt seen more bans.
 
Bot doesnt work for me on patch 3.3.3a? Anyone know how to fix this?
 
Bot doesnt work for me on patch 3.3.3a? Anyone know how to fix this?

LOG FILE? Dude... are you kidding? You dont think that someone help you witch such an "error message"?
Hundreds of users using HB. There is no HB.exe-fix. Only a User-fix ;-)
So show your log and you get help
 
Code:
[10:28:04:609] Current build of wow is not supported! - [11723]
[10:28:22:531] Current build of wow is not supported! - [11723]
[10:40:24:718] Current build of wow is not supported! - [11723]
[11:16:20:484] Current build of wow is not supported! - [11723]
[11:16:28:546] Current build of wow is not supported! - [11723]
 
Code:
[10:28:04:609] Current build of wow is not supported! - [11723]
[10:28:22:531] Current build of wow is not supported! - [11723]
[10:40:24:718] Current build of wow is not supported! - [11723]
[11:16:20:484] Current build of wow is not supported! - [11723]
[11:16:28:546] Current build of wow is not supported! - [11723]
Dude, we're on 3.3.5, not 3.3.3a, that's why it's not working I guess :)
 
Just made a clean install of windows and now it keeps crashing within a couple seconds and giving the error "An item with the same key has already been added." I looked in the log, and I don't see anything.

Code:
[3:07:17 AM:820] Warning: 'TargetMinLevel' has been moved to 'GrindArea'. Please reflect this change in your profiles.
[3:07:17 AM:821] Warning: 'Factions' has been moved to the 'GrindArea'. Please reflect this change in your profiles.
[3:07:18 AM:484] Warning: 'TargetMinLevel' has been moved to 'GrindArea'. Please reflect this change in your profiles.
[3:07:18 AM:486] Warning: 'Factions' has been moved to the 'GrindArea'. Please reflect this change in your profiles.
[3:07:18 AM:515] Changed POI to: Type: None, Loc: <0, 0, 0>
[03:07:19.4047] [Navigator] Loaded new tiled mesh for map "Northrend".
[03:07:20.8598] [Navigator] Generated path from <5699.099, 615.4934, 646.6757> to <5848.534, 661.4178, 658.4285> in 234 ms (0.23 seconds)
 
Last edited:
Yea, ive seen several people get reported for this tonight already.

I would see team mates doing it, and other team mates would be telling people to report them. I cant bot BGs bc of this. Its a problem thats been going on for weeks now but still hasnt seemed to get fixed.

This is just one of the MANY problems HB has been having. All of which are easily noticeable and im surprised we havnt seen more bans.

Ironic I got a tell informing me "Enjoy your ban seen you AFK over the weekend allot"
 
Just made a clean install of windows and now it keeps crashing within a couple seconds and giving the error "An item with the same key has already been added." I looked in the log, and I don't see anything.

Code:
[3:07:17 AM:820] Warning: 'TargetMinLevel' has been moved to 'GrindArea'. Please reflect this change in your profiles.
[3:07:17 AM:821] Warning: 'Factions' has been moved to the 'GrindArea'. Please reflect this change in your profiles.
[3:07:18 AM:484] Warning: 'TargetMinLevel' has been moved to 'GrindArea'. Please reflect this change in your profiles.
[3:07:18 AM:486] Warning: 'Factions' has been moved to the 'GrindArea'. Please reflect this change in your profiles.
[3:07:18 AM:515] Changed POI to: Type: None, Loc: <0, 0, 0>
[03:07:19.4047] [Navigator] Loaded new tiled mesh for map "Northrend".
[03:07:20.8598] [Navigator] Generated path from <5699.099, 615.4934, 646.6757> to <5848.534, 661.4178, 658.4285> in 234 ms (0.23 seconds)

I think something is wrong with your Profile. We need the full logfile
 
Don?t hurry guys, its "holiday-time". Our problems will be fixed soon. *hope*
 
Ressurect sequence logic is broken. When toon trying to find safe spot to ress he just run around and then run to corpse and ress on them. Funnyyest thing what he run out to safe spot and then run back to corpse to ress.
 
Status
Not open for further replies.
Back
Top