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

Honorbuddy v2.5.7291.636

Status
Not open for further replies.
Boomboom said:
Region: EU
WoW: fully updatedtried to install a fresh HB: Yes
Game Bit: 32
Getting this error:


Is there currently a Way to fix this or should i wait for a new Release?
Click to expand...
bot clearly sees you using 64bit wow
 
There are a lot of wow crashes when a char die ;-(
 
Warlock

Does anyone havea Warlock questing and he's doing the spells correctly if they can tell me how they got the bot to do more than just Corruption.

Thanks


Demon
 
The amount of questing related problems have skyrocketed since last version of HB. The .636 has huge problems running kicks profiles more than 20-30 minutes unattended. This could of course be related to bad quest profiles. But I find kick having high quality and since it's during 68-80 profile it should be fairly stable by now.

This is during the LK phase. I hope it will improve for later levels.

View attachment could not find quest npc7516 2013-07-03 09.15.txt
View attachment unwanted aura3016 2013-07-02 18.34.txt
View attachment Not summoning moodle7516 2013-07-03 09.15.txt

L80 problems
View attachment Died inside instance portal7516 2013-07-03 09.15.txt
 
lol on my win7 pc, HB dont work, but yesterday i created a virtual machine Wirth XP and There worked the login without that auth fail oO

Sent from my GT-I9100 using TheBuddyForum mobile app
 
I noticed that with this build while running QuestBot it is running around the camps to get to the NPC's rather then just running straight to the NPC's. This looks really bad. No player would ever run around a quest hub to get to an NPC rather then just running straight to them. Because of this issue it gets stuck quite often.
 

Attachments

I don't think it has anything to do with the release. This happens on every release. I guess it's just how pathing works. It will choose the shortest path to the NPC it can find.

MrWizard516 said:
I noticed that with this build while running QuestBot it is running around the camps to get to the NPC's rather then just running straight to the NPC's. This looks really bad. No player would ever run around a quest hub to get to an NPC rather then just running straight to them. Because of this issue it gets stuck quite often.
Click to expand...
 
Anyone else having trouble with Singular on a mage, starts ranged attack fine, as mob gets closer just stands around like stale bottle of piss and dies ?

G
 
Just a little opticial thing, you could stop translating "Native flying" with "Ureinwohner fliegen" in the german language file. "Nativ" would be totally OK :s
 
Why is no mod coming into this thread to address issues? I see many issues mentioned but no response.
 
Demondog70 said:
Why is no mod coming into this thread to address issues? I see many issues mentioned but no response.
Click to expand...

Issues should be reported in the Honorbuddy Support forum, it's better so people can use the search feature to find their problems and to help address a single issue at a time.
 
i think there is a lootbug and it never stops it keeps strafing around the mob and never loots til i stop the bot and start

[Singular] BotPOI Skithian Dreadhawk.43BB not valid --- clearing
[Singular] Bot TargetList is empty, no targets available
 
23051602 said:
The amount of questing related problems have skyrocketed since last version of HB. The .636 has huge problems running kicks profiles more than 20-30 minutes unattended. This could of course be related to bad quest profiles. But I find kick having high quality and since it's during 68-80 profile it should be fairly stable by now.

This is during the LK phase. I hope it will improve for later levels.

View attachment 98175
View attachment 98176
View attachment 98179

L80 problems
View attachment 98195
Click to expand...
this. I won't upload the logs, but just want to say the paying is HORRIBLE for WoTLK and TBC after this last update. 100% running into walls, never tries other routes. It's horrible to go to sleep, after watching it run ok for 10 minutes, only to come back after 7 hours to him wall running right next to where I left him, or to find a bot in a infinite loop with a quest giver for 7 hours.
 
Ok, here we go, Bobby didn't want to deal with it in the Singular thread so it is here (and I am fairly sure you are going say it's a singular issue so we will just go around in circles). fresh .636 install, all cache folders removed, deleted singular directory in .636 and replaced it with singular 2687 from the singular thread, updated kicks svn from scratch, now at 2610. Copied over the plugins and Quest Behavior folders into my fresh install.

log in and setup directory structure for mesh, tick tickboxes for my mage's setup, load the Blank QO.xml and make sure it starts, logout. Turn on debug logging and run again, load kicks [A - Quest] 85-86 The Jade Forest [Kick], here is the log. (FWIW the singular packed with .636 exhibits the same behavior)

View attachment mage 2013-07-07.txt

.636 is plain awful, loot bug is worse than ever, my paly stops fighting for no reason all the time, or should I say tries to target a mob constantly but never starts attacking it. I was running botanist pit of saron farm this morning and it missed all the bosses where previously it killed them, both with singular and Vanguard, not sure why.

G
 
why am i getting this message but still cant logging :(
Honorbuddy v2.5.7291.636 started.
Logging in...
Attached to WoW with ID 5228
 
script2013 said:
why am i getting this message but still cant logging :(
Honorbuddy v2.5.7291.636 started.
Logging in...
Attached to WoW with ID 5228
Click to expand...

Make a thread in the Honorbuddy Support section and attach the log with this error.

Risien said:
Fresh install with a lvl 1 getting these errors with BOTH kicks and Cava's profiles
Click to expand...

Make sure it's a true clean install. Guide: Clean Installing. Also make sure you aren't mixing updated Kick's behaviors with Cava's plugin as you may get errors because of the mix-matched versions.
Make a support thread if this doesn't help fix it. Support in this thread is ignored.
 
Status
Not open for further replies.
Back
Top