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

[Broken] Questing Bot

Status
Not open for further replies.
go into your wow keybindings and set them to default, also in your wow settings there should be one called "interact on right click" (or something) make sure that is checked.
 
I've done this and it didn't make a difference, bot is still trying to get completed quests and doesn't want to do anything else.
 
Bumping to get back on first page - anyone have any ideas. I've tried everything listed above. I really want to get this working. The bot insists that it is going to pick up "Journey to Thrallmar" which is already completed. I have also completed several other quests by hand in an attempt to try to get it to come out of the derptastic state it is in but that didn't work either.
 
Yes, it then would not complete it just kept opening the flight window even after a fresh extract clearing WTF/cache in wow and restarting both. I completed that section. Then it wouldn't fly to thrallmar. Now it wants to restart the quest that is totally complete now.
 
I just tried this from another computer - fresh SVN of kicks, all items discussed previously cleared (cache, wtf, keybinds, even deleted macros). Fresh extract of HB and same results. Bot repaired in Thrallmar then busted across the desert of Hellfire Peninsula, straight into a bunch of 70 elite packs at the stairs to the dark portal trying to pick up "Journey to Thrallmar" which is already complete.

Anyone else got any ideas? This is getting old.
 
So today, i tried this on another machine that i haven't ever used HB from again. This behavior is being exhibited on a fresh (downloaded and installed last night) install of WoW with no addons at all, completely dumped the keybinds as well. I downloaded the latest Beta version of HB as well. This is occuring on mutliple characters now. 2 Characters in Jade Forest try to re-accept quests that were completed by HB dozens of quests back in the chain the last time HB was running on them and the Warlock continues to try to accept Journey to Thrallmar.

PLEASE HELP!
 
r4p3 said:
So today, i tried this on another machine that i haven't ever used HB from again. This behavior is being exhibited on a fresh (downloaded and installed last night) install of WoW with no addons at all, completely dumped the keybinds as well. I downloaded the latest Beta version of HB as well. This is occuring on mutliple characters now. 2 Characters in Jade Forest try to re-accept quests that were completed by HB dozens of quests back in the chain the last time HB was running on them and the Warlock continues to try to accept Journey to Thrallmar.
Click to expand...

Hi, R4p3,

There is a known bug in the Honorbuddy .520 drop. The problem has these characteristics:

  • You need to talk to a Questgiver that might offer more than one quest
  • From the Honorbuddy log, it appears as if you are trying to pick up a quest you've already completed
  • Clearing the HB and WoW caches does not fix the problem.

More info, here.

HBdev is aware of the issue, and working on it, it seems.

Your choices are to run the quests from multiple-quest givers manually, or wait for the next Honorbuddy drop.

cheers,
chinajade
 
chinajade said:
Hi, R4p3,

There is a known bug in the Honorbuddy .520 drop. The problem has these characteristics:

  • You need to talk to a Questgiver that might offer more than one quest
  • From the Honorbuddy log, it appears as if you are trying to pick up a quest you've already completed
  • Clearing the HB and WoW caches does not fix the problem.

More info, here.

HBdev is aware of the issue, and working on it, it seems.

Your choices are to run the quests from multiple-quest givers manually, or wait for the next Honorbuddy drop.

cheers,
chinajade
Click to expand...

Thanks chinajade. The new HB didn't fix the problem. It is still trying to repeatedly pick up completed quests after clearing the cache on wow and HB. I also closed wow again cleared cache, did a fresh extract of HB and it is still doing this.
 
Anyone else having this problem? I am still seeing this on multiple characters on multiple machines even after clearing the cache no both HB and Wow and a fresh download of HB as well.
 
CodenameG said:
make sure your running the latest version from here. since build 520 is old now. and hopefully the new one will resolve the issues your having .
http://updates.buddyauth.com/GetNewest?filter=Honorbuddy
Click to expand...
I have .521 now and it is still exhibiting this behavior. It also is unable to determine completed quests in other areas such as the new MOP areas. It trys to re-accept the first quest in MOP for horde on the ship even though it is at the hozen village. I also have a death knight that is now trying to accept the first quest for outlands and it is half way through zangarmarsh.

Either I'm completely retarded (i sincerely hope not since i work on servers for a healthcare organization by day) or something's still broken. HALP! :P
 
I am seeing this behavior on an increasing number of characters. I just purchased additional keys and this happened at level 8. I deleted the character created another one and it did the same thing at level 14. I then deleted that character and created another new one and it did the same at level 38. I can't figure out what is going on from the log. All I can tell you is that it doesn't even try to figure out which quest it is actually on, it just starts spamming on the quest giver. It appears to do this for a new "area" and to the first quest giver in the new "area" every time. Is this a problem with kicks? I would really like to get this figured out as I can't see why others wouldn't be seeing this problem.
 
So, more information and I found something in one of the Kicks threads about this. It looks like this is bouncing back to the first quest in an area and repeatedly trying to complete after a restart. So far I can report that before I learned that this is a bug that needs to be reported to the developers, it has happened on 5 of the paladins I have going right now as well as my Warlock and two other characters. It has failed to recognize quest progress and reverted to the first quest in outlands on 3 characters, and on has done this at the beginning of EPL quests and bugged out as well. Does this ring some bells for anyone or does anyone know how to stop this from happening.

Edit: Removed some information about another problem that I have now fixed. :)
 
r4p3 said:
So, more information and I found something in one of the Kicks threads about this. It looks like this is bouncing back to the first quest in an area and repeatedly trying to complete after a restart. So far I can report that before I learned that this is a bug that needs to be reported to the developers, it has happened on 5 of the paladins I have going right now as well as my Warlock and two other characters. It has failed to recognize quest progress and reverted to the first quest in outlands on 3 characters, and on has done this at the beginning of EPL quests and bugged out as well. Does this ring some bells for anyone or does anyone know how to stop this from happening.
Click to expand...

Hi, R4p3, and very sorry we haven't solved this for you.

Yes, something you said does ring a bell. "5 paladins going right now." Does each of your toons have their separate Honorbuddy directory? If they don't, then the cached information from each of the toons is mashed together into the same Cache, and Honorbuddy may get confused about the current state of the toons.

I'm not 100% certain on this, but creating a unique Honorbuddy directory for each running session is not that hard (or disk-expensive) to do. Just something to try.

cheers,
chinajade
 
When I get this problem (Which is pretty common). I usually prune the script file from after checkpoint and the setting the next files lines. Down to the quest that is giving the problems. So that HB don't try to do that quest again. I know it's absolutely not the way it should be. But that is the only way to make it work.
 
23051602 said:
When I get this problem (Which is pretty common). I usually prune the script file from after checkpoint and the setting the next files lines. Down to the quest that is giving the problems. So that HB don't try to do that quest again. I know it's absolutely not the way it should be. But that is the only way to make it work.
Click to expand...
if all else fails this is definitely something to try.
 
CodenameG said:
if all else fails this is definitely something to try.
Click to expand...

Thanks, I do have all of them running from separate directories and each actually has a separate copy of the WoW files. I had thought about hacking that up like that, but didn't know if it would break anything -- I am fluent in C#, Java, VB, and pretty much any script language, so I won't hesitate next time. Thanks for the information all.
 
Status
Not open for further replies.
Back
Top