"Target Needs to Be In Front of You!", "You are Facing the Wrong way!"

[Bammeh]

idk if this is a CC error, I used fpsware Rogue, so I dont think it is....
but whenever the bot attacks something, im usually facing the wrong way, and it will not turn around to kill it.
Using Kicks 1-68 Horde quest profile with sub profiles.


Log attached.
Latest HB, Latest SVN of Kick's profiles and Fpsware Rogue
View attachment 7-25-2011_12_05 PM 4872 Log.txt

 

[chinajade]

idk if this is a CC error, I used fpsware Rogue, so I dont think it is....
but whenever the bot attacks something, im usually facing the wrong way, and it will not turn around to kill it.
Using Kicks 1-68 Horde quest profile with sub profiles.]

All of FPSware's CCs are suffering from this at the moment.

It appears HBcore broke one of the several Face() or Is*Facing() methods. FPSware is out with family concerns at the moment, and won't be able to look at a workaround for this for a while.

Our only hope is the bug in the HBcore can be found sometime soon. I've looked at logs, and they don't show anything. Makes sense, as the CC is probably doing things correctly, but its directives aren't being respected.

cheers,
chinajade

 

[Bammeh]

Ah, makes sense. Okay Well, I guess I'll have to babysit it more carefully. or just BGbot.

Thanks, do you have any working alternatives?

 

[Bammeh]

Any idea on which update this was broken? So I can go back to the one before it?

The last update before the newest one doesn't work.

Also, where can I find all old HB versions?

 

[Zeewolf]

Just to point out that you may have made the same slip up that I did, in that i enabled the LazyRaider option in the CC for doing a 5man and then forgot to turn it off.

LazyRaider setting in the CC only applies when the bot starts using the pull/combat behavior in the CC and hands movement control over to the CC. Out of combat movement is not handled by the CC therefore it can run around questing and look normal but then only seem to have trouble turning when it gets in combat

 

[chinajade]

Just to point out that you may have made the same slip up that I did, in that i enabled the LazyRaider option in the CC for doing a 5man and then forgot to turn it off.

LazyRaider setting in the CC only applies when the bot starts using the pull/combat behavior in the CC and hands movement control over to the CC. Out of combat movement is not handled by the CC therefore it can run around questing and look normal but then only seem to have trouble turning when it gets in combat

That's a great point. Singular, and Amplify also have options to 'disable movement', and will exhibit these exact same symptoms if movement is disabled.

However, FPSware's CCs do not have this capability, and several of them that I've used are exhibiting this behavior. It started somewhere in the HB-2.0.0.5xxx family as I recall, and FPSware was 'out' at the time when I started noticing the problem. Even his "Default Warrior" which hasn't been updated in quite a while exhibits this problem.

I don't use LazyRaider or any similar plugins, so that's not the cause of the problem.

So, I'm 99% certain its nothing user-caused or FPSware has done to cause the breakage.

cheers,
chinajade

 

[Bammeh]

In the "advanced" tab of the CC right?

 

[Zeewolf]

Yep and the rogue CC definately has it