Honorbuddy 2.0.0.3895 Discussion Thread

Pet classes (such as my mage) are still acting retarded when the pet pulls agro. It's like "oh cool you have agro, lets ignore the target and body pull the nearest one nearby"

but only sometimes

Using Amplify

 

I have been unable to run the last few versions of HB/GB. Whenever I go to start it the first time I get the installing components message box and hit okay to let it, then get an error. The error thing wouldn't let me send it in, so I just downloaded the report and will upload it here.

NOTE: It was originally a ".saencryptedeport" file, but I changed it to a text file to upload here.

 

Thank you! This fixed the Mage pet problem too already tested.. I just modified the DefaultMage.Combat.cs and it works great.

 

2 wows running I am at 22% cpu usage, 2 wows running with 2 HB running I am at 100% cpu usage. I used to be able to run 3 wows and 3 HBs at the same time and hover around 66% cpu usage.

Any ideas what happened with this latest version? I tested it just to see whats going on and as soon as I load up even 1 HB my cpu usage goes to 100%. I have a core 2 duo 3.16ghz with 8gb ram. Ram usage is nothing special and doesnt really change when I load HB but dang the cpu usage is sky high.

Using GB2 btw inside of HB, not sure if that helps.

 

Minor Issue

Thanks for the new version everything seems to work well, using Archbuddy also.

there is one issue however, when selecting a specific flying mount to use. you can not put in Flying Machine to use the engineering helo, as it will default to the blue wind rider for horde and not use the flying machine. All other flying mounts my character has seem to be working fine.

the character also seems to sit down occasionally when landing to survey; but I believe that is a Archbuddy issue and not a HB.

Thanks again for the update.

 

This release take like 2x 3 x more cpu usage.....i prefered it take a tad more memory, now the cpu usage is totaly insane, it cap to 90-100 my dual core E8600 lol and same with my E9200 , fix this plz, its lagging bad right now.

Still the movement with experimental is far from what it was, now i get stuck ALOTS while questing and it still run and circle from time to time mostly when it try to reach a mine/herb while questing, it often try to dig a hole through a montain with his horse.......HB used to know what path to reach them...... reaching a mob in a LoS is a total pain right now as well giving violent sharp turn while moving.

That new movement came in so smooth and perfect ( broking the loot tough ) now while your updating, this same movement becoming a total breakneck, it go wrong and more wrong.

Blacklisting doesnt seem to work, unless i made it wrong. ( GB2)

Zuruss

 

kind of a noob question, and maybe not in the right thread, but is it best to use the same mesh folder for all new releases? Is the mesh like the mapping of the wow world and does not change and therefore does not get updated with the modified code?

Thanks.
And thanks for the update.

 

Warlock CC if completely BROKEN up when dealing with adds. I guess just like Hunter class and Unholy DK. You are very busy with GB2 BUT don't forget that wee have normal GB for flying which is light and not using all resources like HB+GB2.. And HB if for GRINDING which we con not do be cos you cant spend 1 hour to fix CC's. I bet Hawker or Nesox can fix CC's in 10 minutes but for some reason you spend all of you time on HB2 which i personally like majority of botters don't need be cos we have normal GB...No offense, just facts.

 

Running 1 HB with grinding mode, 2 HB with GB2 mode.
HB with Grinding mode is at 5% CPU usage, the GB2 mode HB clients are both at around 45% - seems to run but can't do much else on the machine, even typing is slow as hell.

EDIT:
Had to turn the GB2 mode farmers off, cpu usage got so high wow didn't react anymore.

 

Not trying to flame here, I'm trying to help. What you are using here is a TEST version, if you look in the releases section of the forum, you will find there is a STABLE version, (2.0.0.3804). No offence, just facts.

 

Also planning to hotfix the "Don't ninja nodes" option (it seems to ignore the fact that there is someone standing right on top of a node | gb2 will descend down and try to gather it) and the stuttering movement (will pause for 0,2 - 0,5 seconds on every reached hotspot)?

 

And the funny bug that it will never dismount when you get attacked before you reached the ground?

 

Could you squeeze the pet combat fixes in as well? It's affecting multiple classes and it looks really dumb

 

Haven't seen that so i guess you're right

 

help

[11:07:23 AM:671] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.Logic.Targeting.Pulse()
[11:07:23 AM:671] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.Logic.Targeting.Pulse()
at Styx.WoWPulsator.Pulse(PulseFlags flags)
at Styx.Logic.BehaviorTree.TreeRoot.b()
at Styx.Logic.BehaviorTree.TreeRoot.a()
[11:07:23 AM:671] System.Threading.ThreadAbortException: Thread was being aborted.
at Styx.Logic.BehaviorTree.TreeRoot.a()



getting this in my debug log and my guy doesnt move, i am in random BG's at the moment, WSG. any idea why? it just keeps spamming it.

Edit: When a player gets near me for combat it stops spamming it and fights, but once they die it starts up again and i dont move.

Edit again: Im in EoTS and its running fine again, maybe something wrong with WSG?

 

Yup I'm burning 3 times the CPU per HB as well. I cannot use this version.

 

i was using kaz's 1-60 questing profile on my hunter and was dead for multiple hours this morning while i was asleep. He continually ran back and forth in the graveyard for hours while dead in Westfall. Switched back to .3804 this morning and now its working like a charm. There is also nav issues during the quests and combat is completely screwed up...pet would go in then my hunter would run the other way and agro four mobs then die instead of shooting target. Not sure but when I went back to .3804 none of this is happening and its working like a charm.

 

The way i see it atm, is like HB doesnt care if anything in the way while it go toward mine/herb ( questing mode at least ), while it go pull, there is 30 tree no problem the bot think he can go through them all..... did you broke the navigator or something or forgot to still apply the mesh while these action are being done ? if i recall well my bot always used to find the right path to go at the mob or mine/herb, now its like he doesnt care anymore which path he gonna use as long he reach it.....which mean getting in about everything on the way.


Zuruss

 

would it be possible to corpse run to your body instead of spirit rezzing using the gatherbuddy2 bot on honor buddy? not sure if that was a profile restriction or a gatherbuddy restriction as far as not being able to run back to a body to rez

edit: finally died lol. unchecked rez at gy and it rezzed at my body hurray!