Honorbuddy doesn't chase mobs?

[ghettofleck]

Ever since I've used HonorBuddy, it has never chased mobs. It isn't my custom class either as I've used 3 different rogue classes including default of which none of them have chased running mobs.

It looks soo obvious that I am botting from a PvP viewpoint, and just plain annoying from a leveling viewpoint.

HB2 beta 10 does this to me, as does the questing version, as does version 1.333. My log shows nothing abnormal when a mob gets out of attack range.

Is it possible to fix this?

 

[ski]

Once you're in combat, the CC controls movement until you drop out of combat. Its possible that all the CC's you've tried don't have code to move closer to the target if they move out of range but I can't tell without seeing the code.

 

[ghettofleck]

Well, I used the default Rogue CCs, in HB1 and HB2.

I used Mut Mut, versions 1 and 2 (version 2 was supplied by a member on page 28 I believe)

and I also used Stabby.

If you need me to upload the versions, then just ask.

 

[ski]

        private bool combatChecks
        {
            get
            {

                if (!Me.GotTarget)
                {
                    slog("No target.");
                    return false;
                }

                if (Me.Dead)
                {
                    slog("I died.");
                    return false;
                }

                if (Me.GotTarget && !Me.IsAutoAttacking)
                {
                    Lua.DoString("StartAttack()");
                }

                if (targetDistance > 50)
                {
                    if (Me.CurrentTarget.IsPlayer)
                    {
                        slog("Out of range: Level " + Me.CurrentTarget.Level.ToString() + " " + Me.CurrentTarget.Race.ToString() + " is yards away.");
                    }
                    else
                    {

                        slog("Out of range: Level " + Me.CurrentTarget.Name + " is " + System.Math.Round(targetDistance).ToString() + " is yards away.");
                    }

                    return false;
                }

                double meleeRange = 5;

                if (targetDistance > meleeRange)
                {
                    // get within range
                    Navigator.MoveTo(attackPoint);
                }

                WoWMovement.Face();

                return true;
            }
        }

(From the default CC in the questing test)

This is called quite a few times while in combat, so it seems like it should be moving properly (or at least trying to move within range). Can you post a log and I'll forward it to Hawker?

 

[ghettofleck]

Yeah, no problem.

I think the issues occur when it says "Can't cast Sinister Strike". It says this because it's out of range I believe.