HB ARCHIVES: Processed Issues from Honorbuddy Beta thread

I think it's getting closer! Still testing! You have to update singular!

Casters still generating too much threat and keeps running into new mobs

 

Raphus, before you make a release, did you fix this?

http://www.thebuddyforum.com/releases/123044-honorbuddy-beta-builds-11.html#post1223376

 

Yup, release bug is now fixed. For those that experience the Quest Behavior crash after latest update just copy/paste the Quest Behavior folder from previous HB update and it should work.

 

I have reported the same issue in the singular thread with the Mage just being stupid standing there dieing. Seems to happen only on certain mobs. There is a log in the singular thread. Also reported in the support forum a while ago.

 

299...same mage combat issues

Edit: things are ALOT better! just need to help fix some of the threat and multiple mob pulling

Still testing...

 

v299 - Issue with repair to vendor with GatherBuddy bot base. Related to this thread http://www.thebuddyforum.com/honorb...port/127289-hb-not-repairing.html#post1225763

 

Is it just me or are the Betas giving anyone else low fps spikes? My HB is using an awful lot of CPU 20-30% spikes using normal questing.

 

i havent noticed any fps spikes...

i dont use gatherbuddy with all that risk.

so far i've been on 299 and it seems almost as good as before...possible release candidate?

 

If the quest is to kill yellow mobs, bot just runs from hotstop to hotspot without attacking anything. If a red mob aggros, bot won't fight back.

Completely fresh install. Nothing but the HB packaged stuff plus a fresh SVN checkout of Kick's profiles.

Horde quest The Fanciest Water. Need to kill <Vendor Name="Curious Water Sprite" Entry="57673" Type="Repair" X="-712.7651" Y="1236.996" Z="135.872" /> to loot Spiritwater Essence. Behavior is afres described above. Not sure if a profile issue or an HB issue but seemed to be working ok with Cava until I outleveled the profile but there have been several HB updates since then and I can't pinpoint whether it started after an HB update or after I switched back to the Kick profiles.

 

or the correct thing to do would be put up a correct release with the correct behaviours so people don't get more pissed with the devs than they are now. And whoever releases it should actually stay online for an hour or two to see if there is any major problems reported, not just release and go to bed.

G

 

How badly does it suck to be a mage with .299, run into mobs like a tank and get killed, start casting and stop 3/4 way thru and run away and run into other mobs and get gangbanged and killed, a very frustrating day watching my mage do the simplest of tasks. Golden lotus dailies are hilarious to watch. Singular is the problem here, use king-wow and it runs like a dream (the casting bit, still thinks it's a tank), fix it.

 

Haven't used HB for almost a week now cause of all the issues,Just wondering any ETA on when HB will be fixed and updated?

 

Tried king wow... Still doesn't fix combat

 

No update, the devs are beavering away on a new release, expect 10 or 20 buggy betas before a final release that will be full of bugs anyway. The old girl ain't what she used to be.

G

 

Same here now, just standing around like a stale bottle of piss being owned.

G

 

i stopped using my mage and made an enhance shaman was sick of what u describe there and i tried every available routine for mage and many others but all seem to have problems at min.

 

my HB (.299) also uses lots of cpu related to previous releases/betas. always around 15%+ while it's been below 10% before.

 

My paly is at i520, so I felt like getting the ilevel up on my my mage for something different, won't be doing that with any great confidence for a while.

The bot is foobar, so many basic things are wrong with it, let alone the complex ones. They should fix the basic stuff and halt all future development. Until they can catalog what is broken, who broke it and who allowed for further releases and betas to be pushed out still broken and not let them near the source tree for a while, someone clearly isn't doing rudimentary checking that needs to be done. It hasn't been this badly handled for a long time and the way foobar beta after foobar beta is being pushed out I have no hope for AFK botting for the next month.

G

 

Agreed, something quite cpu intense going on in the background for sure, wonder if any dev that is left has the brains to fix it ?

G

 

It seems like CPU utilization went up a few releases back when the Devs talked about blizz upping their detection schemes.

It got much worse for VM users even before this though. We either needed to added a core or up the process priority. I used to be able to run 4-5 lean botting VMs on one machine (dungeon group) - no longer the case.

Crossing my fingers and toes next week brings something good.