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

[Stable] Honorbuddy 1.9.5.0

Status
Not open for further replies.
It does not let me login with my login, only the test. Is it supposed to work that way?
 
New version wont sell! 3 chars 3 diff accounts.. bags get full and it just keeps looting the same thing over and over
 
Bug report template:
What is your toon's class? [Druid, Paladin, Warlock, etc]
Warlock
What is your toon's race? [Troll, Orc, Human, etc]
Orc
What CC were you using?
SkiWarlock

What profile were you using?
1-60 Horde

List any plugins you were using:
Na

What area did the bug occur in (Please be as specific as possible. Use the minimap's area text for the current area)?
Anywhere

What was your toon's position when the bug occurred (X, Y, Z coordinates)?
Anywhere

What type of bug are you reporting? (Crash, Navigation, quest bug, 'can't make up your mind', etc)
Crash

What was the bot's current action? (Check your logs)
Loading Injection???

Explain the bug in as much detail as you can:
Once logged in I try to open HB 1.9.5.0 and WoW becomes non-reponsive. The HB log is empty. If I try to load HB first and log in, HB never lets me "Login"

Steps to reproduce the above bug:

Attach your log file(s)
Attach any crash report(s) [These may be the WoW crash dump, or simply a .NET exception]
Not sure where to get these log files, but if someone could point me in the right direction I would love to get them posted.

Anything else the dev team should know?

Logs are in C:\Path\To\Honorbuddy\Logs

They are dated, so just fine the correct one. :)
 
Bug report template:
What is your toon's class? [Druid, Paladin, Warlock, etc]
Warlock
What is your toon's race? [Troll, Orc, Human, etc]
Orc
What CC were you using?
SkiWarlock

What profile were you using?
1-60 Horde

List any plugins you were using:
Na

What area did the bug occur in (Please be as specific as possible. Use the minimap's area text for the current area)?
Anywhere

What was your toon's position when the bug occurred (X, Y, Z coordinates)?
Anywhere

What type of bug are you reporting? (Crash, Navigation, quest bug, 'can't make up your mind', etc)
Crash

What was the bot's current action? (Check your logs)
Loading Injection???

Explain the bug in as much detail as you can:
Once logged in I try to open HB 1.9.5.0 and WoW becomes non-reponsive. The HB log is empty. If I try to load HB first and log in, HB never lets me "Login"

Steps to reproduce the above bug:

Attach your log file(s)
Attach any crash report(s) [These may be the WoW crash dump, or simply a .NET exception]
Not sure where to get these log files, but if someone could point me in the right direction I would love to get them posted.

Anything else the dev team should know?

Ok, here is the HB log.
 

Attachments

You just need to load a profile, simple as that. Just load the default EotS BG profile and all should be sweet.

G

WoW becomes non responsive as soon as I open HB. I dont even have a change to login. It only does this on my laptop. Not sure if its a Vista thing or something else completely.
 
New version wont sell! 3 chars 3 diff accounts.. bags get full and it just keeps looting the same thing over and over

Sells fine for me. Need to fill out the bug report template to get some help.
 
What is your toon's class? [Druid, Paladin, Warlock, etc]
Any Class

What is your toon's race? [Troll, Orc, Human, etc]
Dwarf

What CC were you using?
Convalesce 3.3 Beta 3

What profile were you using?
Dwarf 1-60 questing redone

List any plugins you were using:
None

What area did the bug occur in (Please be as specific as possible. Use the minimap's area text for the current area)?
Cold Ridge valley

What was your toon's position when the bug occurred (X, Y, Z coordinates)?
Multiple, pretty much anywhere where there are quests

What type of bug are you reporting? (Crash, Navigation, quest bug, 'can't make up your mind', etc)
quest bug

What was the bot's current action? (Check your logs)
Just finished accepting quest/Or turning in quest

Explain the bug in as much detail as you can:
Well (Sometimes) after accepting quest HB just stalls out, I even made a plugin to restart HB ever min and it works except when it stalls out

Steps to reproduce the above bug:
use questing profiles and wait and watch

Attach your log file(s)
Attach any crash report(s) [These may be the WoW crash dump, or simply a .NET exception]
never crashed

Anything else the dev team should know?
naw
 
What is your toon's class? [Druid, Paladin, Warlock, etc]
Priest
What is your toon's race? [Troll, Orc, Human, etc]
Human
What CC were you using?
Ecliptor2
What profile were you using?
Breakneck
List any plugins you were using:
eRefreshment, KingJumper
What area did the bug occur in (Please be as specific as possible. Use the minimap's area text for the current area)?
All over Elwynn forest
What was your toon's position when the bug occurred (X, Y, Z coordinates)?
Couldn't say.
What type of bug are you reporting? (Crash, Navigation, quest bug, 'can't make up your mind', etc)
Combat
What was the bot's current action? (Check your logs)
Attacking
Explain the bug in as much detail as you can:
Bot tries to smite something in front of it (it can clearly cast, no LoS issues) and wow gives an error "target must be in front of you" even though it clearly is. When I pressed a skill hotkey it just casted it and combat started.

Code:
Activity: Pulling Mangy Wolf now.
Killing Mangy Wolf at distance 26
Casting Smite
Killing Mangy Wolf at distance 22
Casting Smite
Casting Smite
Killing Mangy Wolf at distance 22
Casting Smite
Killing Mangy Wolf at distance 20
Casting Smite
Killing Mangy Wolf at distance 24
Casting Smite
Killing Mangy Wolf at distance 24
Casting Smite
Killing Mangy Wolf at distance 28
Casting Smite
Killing Mangy Wolf at distance 26
Casting Smite
Killing Mangy Wolf at distance 26
Casting Smite
Killing Mangy Wolf at distance 25
Casting Smite
Killing Mangy Wolf at distance 21
Casting Smite
Killing Mangy Wolf at distance 21
Casting Smite
Killing Mangy Wolf at distance 21

Fixed in next release.
 
What is your toon's class? [Druid, Paladin, Warlock, etc]
Any Class

What is your toon's race? [Troll, Orc, Human, etc]
Dwarf

What CC were you using?
Convalesce 3.3 Beta 3

What profile were you using?
Dwarf 1-60 questing redone

List any plugins you were using:
None

What area did the bug occur in (Please be as specific as possible. Use the minimap's area text for the current area)?
Cold Ridge valley

What was your toon's position when the bug occurred (X, Y, Z coordinates)?
Multiple, pretty much anywhere where there are quests

What type of bug are you reporting? (Crash, Navigation, quest bug, 'can't make up your mind', etc)
quest bug

What was the bot's current action? (Check your logs)
Just finished accepting quest/Or turning in quest

Explain the bug in as much detail as you can:
Well (Sometimes) after accepting quest HB just stalls out, I even made a plugin to restart HB ever min and it works except when it stalls out

Steps to reproduce the above bug:
use questing profiles and wait and watch

Attach your log file(s)
Attach any crash report(s) [These may be the WoW crash dump, or simply a .NET exception]
never crashed

Anything else the dev team should know?
naw

Thanks to all who reported this - Nesox has it fixed for next release.
 
Hi everyone, Im quite new to Honorbuddy, so I dont know if this is a bug or me doing something wrong, it's probably the last..

I used this build of Honorbuddy: [Stable] Honorbuddy 1.9.5.0
And this plugin: [Questing] Alliance Outland 58-71 (http://www.buddyforum.de/showthread.php?5621-Questing-Alliance-Outland-58-71)

I had a level 62 (now 63) Draenei Paladin who had done no quests in Outland, and the problems began at once:
I stood at Dark Portal and after setting up Honorbuddy clicked start.
She picked up a quest and stuff, but didnt want to fly to Honor Hold, instead ran through the Elite mobs at Dark Portal, died of course :)
I took her to Honor Hold manually, started Honorbuddy again, and HB started doing all kinds of quests, all it could find in fact.
I didnt think of it until my Paladin stood banging her head at the instance Shattered Halls, as she wanted to go in there.
I stopped HB, deleted all quests, and ran to Zangarmarsh (Telredor), started HB again and she picked up all the quests and then ran off the edge of the mushroom and died. :)
It seemed as if HH didnt stick to the "forced quests" or what it was called in the profile xml file.

I then changed HB to "grinding" and kept the same profile, and she happily grinded in Zangarmarsh, I think it went rather well, though I hope she will run someplace elce as she turned 63 now.

Am I doing something wrong ?

Thanks
 
Ill stick to 1.9.4.5 for now... 1.9.5.0 is much more buggy for me..

Bot doesnt enter BG's. And when JOIN BG MSG appears it frozes and spams the msg in the HB LOG QUEING UP AB., QUEING uP WSG.. and just doest that to infinity without entering battlegrounds and stops grinding.
 
I know we're not supposed to be posting issues relating to vendoring etc. But has anyone noticed that new bot doesnt like emptying bags when full? Had a quick read through and couldnt see anyone else having this issue? I thought it maybe relating to empty space in quiver or something but not sure, will try filling that after dt. But it seems to not vendor when full whether or not the finding of vendors is on or off.

Would just like to reiterate my previous posts, am very impressed with the continued progress and the new features which have been implemented are definately a real bonus so well done to all those who have been working on the project. best ?20 i ever spent!
 
What is your toon's class? [Druid, Paladin, Warlock, etc]

Death Knight

What is your toon's race? [Troll, Orc, Human, etc]

Orc

What CC were you using?

Default Death Knight one that comes with this version

What profile were you using?

"Horde 68-80" with Mixed PVP (Ioc)

List any plugins you were using:

None

What area did the bug occur in (Please be as specific as possible. Use the minimap's area text for the current area)?

It's random. The bot simply goes AFK every 1-2 hours. I have to press STOP then START again to fix this which requires baby sitting. My toon goes AFK and bot sais "moving to hot spot" but its not.. kind of like it loses sync completely but doesn't fix itself.

What was your toon's position when the bug occurred (X, Y, Z coordinates)?

It's random. Happens anywhere after 1-2 hours.

What type of bug are you reporting? (Crash, Navigation, quest bug, 'can't make up your mind', etc)

Bot just goes afk

What was the bot's current action? (Check your logs)

"moving to hot spot"



This bug happened in this version and the last one as well.

Explain the bug in as much detail as you can:


my toon goes afk all the time. more in this version then the last one. simple as that. could be the profile who knows.

Steps to reproduce the above bug:

none It just goes afk.

Attach your log file(s)
Attach any crash report(s) [These may be the WoW crash dump, or simply a .NET exception]

Anything else the dev team should know?

Bot is also not mounting now on top of it going afk every half hour or less.

Completely delete your mesh folder and confirm the problem doesn't recur.
 
Bug report template:
What is your toon's class? [Druid, Paladin, Warlock, etc]
Warrior

What is your toon's race? [Troll, Orc, Human, etc]
Orc

What CC were you using?
Default

What profile were you using?
Thousand 125-175, Badlands 175-230 mining profiles

List any plugins you were using:
none

What area did the bug occur in (Please be as specific as possible. Use the minimap's area text for the current area)? Badlands and in Thousand Needles

What was your toon's position when the bug occurred (X, Y, Z coordinates)? Irrelevant I suspect

What type of bug are you reporting? (Crash, Navigation, quest bug, 'can't make up your mind', etc)
Dismounting bug

What was the bot's current action? (Check your logs)

Explain the bug in as much detail as you can:
The bot is dismounting everytime it gets aggro on it while trying to level up mining. Everytime theres an add the bot dismounts and fights it...instead of just running by. Even when there is no node within range it still does this.

Steps to reproduce the above bug:
Load up a mining profile...

Attach your log file(s)
Attach any crash report(s) [These may be the WoW crash dump, or simply a .NET exception]

Anything else the dev team should know? This is only happening since the 1.9.5 patch

Fixed in next release.
 
I just tried extracting like I always do; I now get:

! C:\Users\Ntsmarkv\Desktop\HB2\hb 1.9.5.0.zip: Cannot create Honorbuddy.exe
! Access is denied.
! C:\Users\Ntsmarkv\Desktop\HB2\hb 1.9.5.0.zip: Cannot create Tripper.XNAMath.dll
! Access is denied.

Restarted PC, same issue. anyone else having this issue?
 
I just tried extracting like I always do; I now get:



Restarted PC, same issue. anyone else having this issue?

Sounds like something is blocking those files on your computer, anti-virus or similar?
 
What is your toon's class? [Druid, Paladin, Warlock, etc]
Paladin

What is your toon's race? [Troll, Orc, Human, etc]
Belf

What CC were you using?
convalesce

What profile were you using?
Horde 71-76 dragonblight

List any plugins you were using:
none

What area did the bug occur in (Please be as specific as possible. Use the minimap's area text for the current area)?

What was your toon's position when the bug occurred (X, Y, Z coordinates)?

What type of bug are you reporting? (Crash, Navigation, quest bug, 'can't make up your mind', etc)
pvp bug in mixed mode
What was the bot's current action? (Check your logs):waiting for spirit heal

Explain the bug in as much detail as you can:
When you que up for BG's in mixed mode,i doesnt enter if the 2ng bg you opted for pops up.and if the first one pops up,it enters it normally,but upon death,the toon spirit moves to the place of death rather than wait for spirit heal.on reaching the place,it just jumps in place(in spirit form!!) till you are afked out of the bg.to get the bot moving again,i have to stop hb and start it again.very irritating bug imo!!
Steps to reproduce the above bug:

Attach your log file(s)
 

Attachments

Status
Not open for further replies.
Back
Top