FightThisWay

[Soeski]

I think I saw what you were talking about, and tweaked it. If you click on an attackable mob, it would start attacking it for you, even if you weren't in combat yet. Is that what you were experiencing? If so, download the latest version, I changed it to not do that.

What I actually meant was; after fighting and leaving combat, the cc starts to pull another mob at least 20 yards away (more like 30-40) and starts attacking that one. Sometimes the cc can go on like that for several 100 yards. Since it's not looting with combat bot (that's normal of course) you leave a trail of dead unlooted mobs. I do not want my cc to keep pulling and aggroing mobs by itself, only to attack when I say so So no, I did not even click the mob; it's fully automatic pulling style! Almost like grinding bot without a pre-set path. The cc keeps killing, you just don't know where it will go or end up

But, maybe you intended it this way. Problem with this for me is; in dungeons (5-mans) it aggro's a mob not even in combat with before the tank pulls, only because it's somewhat in range. Tanks do not like that, and me neither being a Shadow Priest / Clothie

I'll try the update soon, thanks for the reply. I love the way it's customizable and easy to understand for non-coders. Maybe now I get higher DPS numbers than CLU, because of the clipping MF you just said having fixed.

 

[Soeski]

Got another one for ya. And it is most likely not possible.
Disengage for hunters: is it possible to make it only disengage to a safe spot, so you don't disengage into more enemies or over a cliff? This goes way over my coding and I haven't seen another coder being able to implement it

Back in the days Glider could do this; that was awesome to see. Did a quick check for terrain, mobs in the area etc. It even took a longer route to avoid mobs altogether, or did not walk a certain path because it would aggro more mobs than the X number you were already fighting. Ah, those days...

 

[Soeski]

Kamilche, another question.
I do not have performance issues per se, but when using Combat Bot, LazyRaider (with or without Framelock) of Raidbot, I often do have a non-responsive HB window during rest. When in combat, I can press Stop/Start etc.; all buttons react immediately.
When not in combat, the window is often unresponsive or does respond, but only 5-10 seconds or more later. Does this sound familiar to you?

 

[squanto]

Hello Kamilche,
I've got a problem with my framerate. When I start the bot my framerate drops up and down between 9 and 50 frame's. After stopping the bot the frame rate becomes stable around 50. I'm using FTW only for the routine's. So in combination with the combat bot (but then the frame rate loss is the worse) or Lazyraider. Have tried it also with grindbot but no profile loaded at that moment.
I'm using a macbook with windows 7 in bootcamp. So I donn't have the scroll lock key. Also a virtual keyboard with scroll lock key makes no difference in performance.
I like your cc very much. It's a pity with this framerate drop.
I hope you can advice me how to get rid of this framerate drop.

 

[Gnobiwan]

Donated. Worth every dollar you get for it!

I concur, will donate again next payday. Great work!

 

[Brambory]

Great CC! But my game sometimes freezes when using this CC, it freezes and will only unlock when i shutt down the bott. I tested this with a warlock and a hunter and this does not happen when im using Singular. Any ideas on how this might work?

Regards

 

[randomstraw]

Also reporting an issue.

FTW freezes my wow with questbot every now and then. turning hb on/off fixes it, but it will occur again.

do you need a log? (although i dont see suspicious things...)

 

[Kamilche]

Kamilche, another question.
I do not have performance issues per se, but when using Combat Bot, LazyRaider (with or without Framelock) of Raidbot, I often do have a non-responsive HB window during rest. When in combat, I can press Stop/Start etc.; all buttons react immediately.
When not in combat, the window is often unresponsive or does respond, but only 5-10 seconds or more later. Does this sound familiar to you?

OK, yes, I found the source of this bug - I experienced it myself. I did a 'lazy programmer hack' on eating/drinking that bit me in the ass. I've fixed it properly, and it will no longer hang when out of combat.

 

[Kamilche]

Also reporting an issue.

FTW freezes my wow with questbot every now and then. turning hb on/off fixes it, but it will occur again.

do you need a log? (although i dont see suspicious things...)

That should be fixed now - check it out (lazy programmer hack on eating/drinking, fixed now.)

 

[Kamilche]

Hello Kamilche,
I've got a problem with my framerate. When I start the bot my framerate drops up and down between 9 and 50 frame's. After stopping the bot the frame rate becomes stable around 50. I'm using FTW only for the routine's. So in combination with the combat bot (but then the frame rate loss is the worse) or Lazyraider. Have tried it also with grindbot but no profile loaded at that moment.
I'm using a macbook with windows 7 in bootcamp. So I donn't have the scroll lock key. Also a virtual keyboard with scroll lock key makes no difference in performance.
I like your cc very much. It's a pity with this framerate drop.
I hope you can advice me how to get rid of this framerate drop.

Try again - implemented something poorly in eating/drinking, fixed it, should not happen now.

 

[Kamilche]

What I actually meant was; after fighting and leaving combat, the cc starts to pull another mob at least 20 yards away (more like 30-40) and starts attacking that one. Sometimes the cc can go on like that for several 100 yards. Since it's not looting with combat bot (that's normal of course) you leave a trail of dead unlooted mobs. I do not want my cc to keep pulling and aggroing mobs by itself, only to attack when I say so So no, I did not even click the mob; it's fully automatic pulling style! Almost like grinding bot without a pre-set path. The cc keeps killing, you just don't know where it will go or end up

But, maybe you intended it this way. Problem with this for me is; in dungeons (5-mans) it aggro's a mob not even in combat with before the tank pulls, only because it's somewhat in range. Tanks do not like that, and me neither being a Shadow Priest / Clothie

I'll try the update soon, thanks for the reply. I love the way it's customizable and easy to understand for non-coders. Maybe now I get higher DPS numbers than CLU, because of the clipping MF you just said having fixed.

I was experiencing that today as well, while grinding with 2 bots in the same party. I changed the empty grind profile to be even smaller, and it seems to have fixed it. Look at the 'readme.html' file for what should go in the grinding profile, let me know if you still have issues.

 

[Kamilche]

Is there any way you can add an option to override the scroll-lock combat function?

I always run 2-3 toons at a time (saves doing dailys on each toon over and over) and I don't want my master moving, or targeting, but at the same time allowing my other instance to function as normal.

I suppose I can reverse the true/false on the scroll lock function, but I am sure you could do something a bit better then me.

Yes - I added a user interface to the program today. Click 'Class Config', and uncheck the single checkbox you see, then click 'Save' and close the window. That way the followers will ignore the state of the scroll lock, but the primary won't.

Thanks for the suggestion!

 

[Kamilche]

Got another one for ya. And it is most likely not possible.
Disengage for hunters: is it possible to make it only disengage to a safe spot, so you don't disengage into more enemies or over a cliff? This goes way over my coding and I haven't seen another coder being able to implement it

Ok, I put that in there today, experimented with it a while, tried it a few different ways, and finally YANKED IT OUT. Disengage is just a bad idea for a bot to use - it's not smart enough to use it properly. So - that feature will not be implemented.

 

[Kamilche]

OK, I have a few changes for you all today.

• Disengage for hunters has been removed - the bot just can't use that intelligently enough.
• Added a user interface to the product, with a single checkbox - 'Use scroll lock to control movement.' Unchecking that, then clicking 'Save', then closing the window, will result in that HonorBuddy session ignoring the state of the scroll lock key, and moving the character itself. This is useful if you want to run multiple HonorBuddies at once, all in the same party. All the followers should uncheck the 'Use scroll lock to control movement' checkbox, and the leader should set their role to 'Tank.' If you can't set the leader's role to 'Tank', because you're a warlock for instance, all the followers should set the 'Focus' to the leader instead. To do this, from the follower, right click the leader, and choose 'Set Focus.' This is also useful when raiding, if you have to heal someone other than the main tank. Whoever is the 'Focus' will be the tank, in FTW's eyes.
• Fixed bug in eating/drinking that would cause the bot to hang until it was done eating/drinking.
• Changed sample empty grindbot file to be even smaller - this seems to have fixed problems where the mobs were being pulled.

I appreciate the bug reports, keep 'em coming! First week of release is always 'late beta', as every programmer knows.

 

[jchiera]

Bro, this CC is awesome! I had 5 mobs on me and I didn't die. Love how it popped Shield wall and Shield Barrier and even used Victory rush for my self heals. Best CC I've used by far!

 

[dagg|e]

That should be fixed now - check it out (lazy programmer hack on eating/drinking, fixed now.)

FTW also freezes my wow with bgbot in your new version update today

 

[Kamilche]

Bro, this CC is awesome! I had 5 mobs on me and I didn't die. Love how it popped Shield wall and Shield Barrier and even used Victory rush for my self heals. Best CC I've used by far!

Glad you like it! I enjoyed making it, though hoo boy, did it take a while.

 

[Kamilche]

Did you get caught in the buggy "eating/drinking hangs the screen" version? Try downloading the latest one.

I checked out a battleground just to see, and didn't notice any hangs. People laughed at the beginning, and yelled 'BOTS! I NEED MOAR BOTS', as we all were standing on exactly the same spot. After 6 of us grabbed the flag, and 10 of us were standing around at the flag, someone cried 'What's happening?' Someone else said 'Bots. Thousands of bots.' I slunk away from the battleground in shame, I couldn't stand to see any more.

Just don't use it until they fix it, my GOD we stand out like a sore thumb! :-D

 

[CrunchCaptain]

Warlocks cast create soulstone in combat if they use the last charge during a fight.

I notice the bag framerate when the honorbuddy window is in the foreground but if you put it in the background it runs fine..

All I've noticed so far...may be back with more.

 

[Kamilche]

Did you get caught in the buggy "eating/drinking hangs the screen" version? Try downloading the latest one.

Just in case you didn't, I put up one more version of the file tonight - this time I took a couple of framelocks off. They're hard to judge - they're a good idea, up until the point they're not, and finding that point is a matter of trial and error. Let me know if you continue to have performance issues.

I examined the timings it dumps every minute, and I'm satisfied with the speed, even after removing the framelocks. Hopefully this resolves the issue and you experience no further problems.

There is one last thing to check - make sure your max background fps in WoW is set to 1/3 of the way up or higher. If you leave it set low, it will make HonorBuddy go so slow things start failing. More info can be found in the help file.