Problem - Puller not targetting mob that has been selected for pull

[gawker]

Version of KissAssist.mac?

10.2.6

When did your problem start?

I just noticed very recently but may have been there a while.

Character Role?

1. Tank
2. Puller

What class is having this issue?

1. Monk

How often does this issue occur?

Often

Can you reproduce the issue?

The only variable that I believe triggers this behavior is large maxradius and perhaps hilly zones where LOS may play a role.

When I set my puller to go after mobs in a large maxradius, the script will announce Pulling-> mobsoandso <-ID 99999 etc and take off towards the mob. Upon reaching the mob it just sits there without targeting and within a few seconds return to camp. In some cases the mob has walked off some distance, but is still in target range. In other cases the mob is right where he stops and if he does not get proximity aggro, he just returns to camp.

I noticed this in hilly Lceanium, but I have my maxzrange = 200

I can't figure what setting I might not have set correctly.

 

[ChatWithThisName]

What is your PullWith=
A known issue with 10.2.6 is discs are not friendly. That has been corrected in the KA11 and it's recommended that you switch to KA11 and see if the issue persists.
The expected issue here is that PullWith=SomeDisc that is ready. But you currently have an active disc up and running (Such as Stalwart Defense or some such) and because you currently have an active Disc up, it won't fire the disc for the Pull. Again, if this is the case the simple fix it to upgrade to KA11.

Currently released with Very Vanilla to make converting your INI's to KA11 style conditions a lot easier, is to

/plugin mq2KissTemplate

and then /maketemplate

It creates a new file with the output information (and tells you what it's named) which can be found in your Macros folder. then you can use the new conditions system without giving yourself an aneurism trying to do it manually.

Alternately if you have no conditions. just get KA11 and run it and everything should translate over well.

 

[gawker]

PullWith=Distant Strike (Monk AA with quick cooldown)

When it works correctly the script will target the mob once it gets within the set range setting for Distant Strike and target the mob then fire. When this bad behavior happens, it will run all the way and stand on top of the mob and never target.

The problem only happens on far targets (maybe those beyond the range of Distant Strike). There is no problem with short range pulls.

I will try upgrading to KA 11 and see if that may fix the problem.

 

[eqtrader74]

Long pull path and a roaming mob. One thing that can happen is the target mob is inside your PullRadius when selected, but by the time you run to it the mob has moved just outside PullRadius. KA will look for it again, see it's no longer "valid" by pull distance (this is the quick second pause at end of pull), not target it and reset by running back to camp.

PullRadius Vs actual pull path. I believe the "run distance" of the pull is checked during the run, not always the straight line radius used at the start of pull. So you may see mobs inside your map circle, which KA updates to pull-range, that actually won't be pulled because the path is longer. You will sometimes see your puller "Yo-Yo" if there are mobs at long range it wants to pull, but the path is just barely too long, so the puller runs towards target->gives up and returns to camp->targets next mob in room->runs towards it->(repeat until another nearby target spawns or all mobs are temp-ignored)

Line of Sight & pulling. Another related issue, is KA is semi-smart about when it targets a pull mob. It tries to check if a player could target the mob before/during pull. If the mob is close KA will target it right at the start of the run, but if it's farther or may have LoS blocked, it will wait until it ends the run. It's not perfect, but this can also lead to a moving mob not being LoS for a ranged PullWith when puller arrives at end of run.

PullRadiusToUse=90 This setting let's KA know how close to get to a mob when using a PullWith ranged weapons/AA/spell/item. It's the percentage of the range of the PullWith's range. So a spell that can hit at 200 range & PullRadiusToUse=90, will make the KA puller run within 180 units of the mob before casting. If you're hunting in a roamer section, sometimes making this smaller can help.

 

[gawker]

I was able to fix my problem by loading and using MQ2Nav. The following code branches depending on what method is available to get you to the mob you are pulling

|------------------------------------------------------------------------Pull Begin Move-------------------------------------------------------------------------------------------|           
            /if ((${Spawn[${MyTargetID}].Distance3D}>${PullDist} || !${Spawn[${MyTargetID}].LineOfSight}) && ${Math.Distance[${Spawn[${MyTargetID}].Y},${Spawn[${MyTargetID}].X},${Spawn[${MyTargetID}].Z}:${CampYLoc},${CampXLoc},${CampZLoc}]}<${MaxRadius}) {
                :WeThereYet
|------------------------------------------------------------------------MQ2AdvPath-------------------------------------------------------------------------------------------|               
                | Advpath pull does not use max pull radius. It uses pullwith radius
                /if (${PullMoveUse.Equal[advpath]}) {
                    /call PullUsingAdvPath ${MyTargetID} ${PullDist}
                    /if (!${MyTargetID}) /return
|------------------------------------------------------------------------MQ2Nav-------------------------------------------------------------------------------------------|
                } else /if (${PullMoveUse.Equal[nav]}) {
                    /call PullUsingNav ${MyTargetID} ${PullDist}
                    /if (!${MyTargetID}) /return
|------------------------------------------------------------------------LOS-------------------------------------------------------------------------------------------|
                | We are pulling by LOS. 
                } else /if (${Spawn[${MyTargetID}].LineOfSight}) {
                    /if (${Me.FeetWet}) {
                        /if (${X2}==0) /varcalc PullDist ${PullDist}-(${Spawn[${MyTargetID}].Distance3D}-${Spawn[${MyTargetID}].Distance})
                        /moveto id ${MyTargetID} mdist ${PullDist} uw
                    } else {
                        /moveto id ${MyTargetID} mdist ${PullDist}
                    }
                    /delay 10
                    /varset X2 ${Int[${Me.X}]}
                    /varset Y2 ${Int[${Me.Y}]}           
                    /if (${DebugPull}) /echo \atDEBUGPULL Pull LOS ${Spawn[${MyTargetID}].LineOfSight} ${PullDist} \agLine#: ${Macro.CurLine}

The LOS method of getting to the Mob fails to target the mob when you get to it. Since MQ2Nav gets me working, I did not dig too far down the rabbit hole to determine why LOS code gets me to the mob but then fails to target and aggro the mob.

 

[dreamflux]

This definitely happens to me as well in KA11. I think it's with instant abilities only, but I'm not positive. Puller runs to point they have los and then turns around and heads back to camp. Most of the time never targets enemy being pulled. Generally happens around corners and things like that.

 

[ctaylor22]

The target is set in the pull routine after you arrive within pull distance of the mob. The target getting set is not dependant on what pull method you are using. The line in the pull routine that you have to pass/branch into is this one:

        /if (${Spawn[${MyTargetID}].ID} && ${Target.FeetWet}==${Me.FeetWet} && !${PullAggroTargetID} && (${Spawn[${MyTargetID}].Distance3D}<${PullRange} || (${PullWith.Equal[Melee]} && ${Spawn[${MyTargetID}].Distance3D}<${Math.Calc[${PullRange}*2]}))) {

Check out line 3 or 4 below that one. That is the line that /targets the mob you are pulling.

A debug log of this happening would be most helpful.

 

[dreamflux]

Here is a debug log of this one. PullerTank has pullradius set to 800. Runs, literally stands on top of the mob which didn't aggro, then runs back to camp.

[2019/01/22 20:25:06] MQ2Log :: Logging is ON
[2019/01/22 20:25:07] [MQ2] DEBUG MobRadar 75 Enter (CheckForCombat) Line#: 5653
[2019/01/22 20:25:07] [MQ2] DEBUG MobRadar Leave 0 Line#: 5670
[2019/01/22 20:25:08] [MQ2] DEBUG EndMacroIf: Enter Line#: 4826
[2019/01/22 20:25:08] [MQ2] DEBUG EndMacroIf: Leave Line#: 4849
[2019/01/22 20:25:08] [MQ2] DEBUG DoWeMove: Enter Line#: 3105
[2019/01/22 20:25:08] [MQ2] DEBUG DoWeMove: Leave Line#: 3265
[2019/01/22 20:25:08] [MQ2] DEBUG DoMiscStuff Enter Line#: 6616
[2019/01/22 20:25:08] [MQ2] DEBUG DoMiscStuff Leave Line#: 6651
[2019/01/22 20:25:08] [MQ2] DEBUG WriteBuffs: 0-Aura of Devotion Line#: 11384
[2019/01/22 20:25:08] [MQ2] DEBUG WriteBuffs: 1-Voice of Thule Line#: 11384
[2019/01/22 20:25:08] [MQ2] DEBUG WriteBuffs: 2-Cloak of Discord Line#: 11384
[2019/01/22 20:25:08] [MQ2] DEBUG WriteBuffs: 3-Hand of Conviction Line#: 11384
[2019/01/22 20:25:08] [MQ2] DEBUG WriteBuffs: 4-Shroud of Discord Line#: 11384
[2019/01/22 20:25:08] [MQ2] DEBUG WriteBuffs: 5-Selo's Accelerating Chorus Line#: 11384
[2019/01/22 20:25:10] [MQ2] DEBUG DoWeMed Enter Line#: 3385
[2019/01/22 20:25:10] [MQ2] DEBUG DoWeMed Leave Line#: 3553
[2019/01/22 20:25:10] [MQ2] DEBUG MobRadar 75 Enter (FindMobToPull) Line#: 5653
[2019/01/22 20:25:10] [MQ2] DEBUG MobRadar Leave 0 Line#: 5670
[2019/01/22 20:25:10] [MQ2Nav] Navigating to spawn: an_elite_ikaav_firebrander01 (8918)
[2019/01/22 20:25:11] <PULLERTANKNAME>  [20:25:10] PULLING-> an elite ikaav firebrander <- ID:8918 at 572 feet.
[2019/01/22 20:25:19] [MQ2Nav] Reached destination at: 1792.00 752.00 68.59
[2019/01/22 20:25:19] [MQ2Nav] Stopping navigation
[2019/01/22 20:25:19] [MQ2] We have exceeded max pulling radius or timer or lost path to mob. Returning to camp
[2019/01/22 20:25:19] [MQ2] DEBUG EndMacroIf: Enter Line#: 4826
[2019/01/22 20:25:19] [MQ2] DEBUG EndMacroIf: Leave Line#: 4849
[2019/01/22 20:25:19] [MQ2] DEBUG DoWeMove: Enter Line#: 3105
[2019/01/22 20:25:19] [MQ2Nav] Navigating to loc: 1225.00, 2115.00, 21.00
[2019/01/22 20:25:28] [MQ2Nav] Reached destination at: 2115.00 1225.00 21.00
[2019/01/22 20:25:28] [MQ2Nav] Stopping navigation
[2019/01/22 20:25:30] [MQ2] DEBUG DoWeMove: Leave Line#: 3265
[2019/01/22 20:25:30] [MQ2] DEBUG MobRadar 75 Enter (CheckForCombat) Line#: 5653
[2019/01/22 20:25:30] [MQ2] DEBUG MobRadar Leave 0 Line#: 5670
[2019/01/22 20:25:32] [MQ2] DEBUG MobRadar 75 Enter (CheckForCombat) Line#: 5653
[2019/01/22 20:25:32] [MQ2] DEBUG MobRadar Leave 0 Line#: 5670
[2019/01/22 20:25:33] [MQ2] DEBUG EndMacroIf: Enter Line#: 4826
[2019/01/22 20:25:33] [MQ2] DEBUG EndMacroIf: Leave Line#: 4849
[2019/01/22 20:25:33] [MQ2] DEBUG DoWeMove: Enter Line#: 3105
[2019/01/22 20:25:33] [MQ2] DEBUG DoWeMove: Leave Line#: 3265
[2019/01/22 20:25:33] [MQ2] DEBUG DoMiscStuff Enter Line#: 6616
[2019/01/22 20:25:33] [MQ2] DEBUG DoMiscStuff Leave Line#: 6651
[2019/01/22 20:25:33] [MQ2] DEBUG DoWeMed Enter Line#: 3385
[2019/01/22 20:25:33] [MQ2] DEBUG DoWeMed Leave Line#: 3553
[2019/01/22 20:25:33] [MQ2] DEBUG MobRadar 75 Enter (FindMobToPull) Line#: 5653
[2019/01/22 20:25:33] [MQ2] DEBUG MobRadar Leave 0 Line#: 5670
[2019/01/22 20:25:33] [MQ2Nav] Navigating to spawn: an_elite_ikaav_firebrander01 (8918)
[2019/01/22 20:25:33] <PULLERTANKNAME>  [20:25:33] PULLING-> an elite ikaav firebrander <- ID:8918 at 572 feet.
[2019/01/22 20:25:42] [MQ2Nav] Reached destination at: 1792.00 752.00 68.59
[2019/01/22 20:25:42] [MQ2Nav] Stopping navigation
[2019/01/22 20:25:44] [MQ2] DEBUG EndMacroIf: Enter Line#: 4826
[2019/01/22 20:25:44] [MQ2] DEBUG EndMacroIf: Leave Line#: 4849
[2019/01/22 20:25:44] [MQ2] DEBUG DoWeMove: Enter Line#: 3105
[2019/01/22 20:25:44] [MQ2Nav] Navigating to loc: 1225.00, 2115.00, 21.00
[2019/01/22 20:25:53] [MQ2Nav] Reached destination at: 2115.00 1225.00 21.00
[2019/01/22 20:25:53] [MQ2Nav] Stopping navigation
[2019/01/22 20:25:53] [MQ2] I got hit by >>An elite ikaav firebrander<< ID: 0 while waiting for mob.
[2019/01/22 20:25:54] [MQ2] DEBUG DoWeMove: Leave Line#: 3265
[2019/01/22 20:25:54] [MQ2] DEBUG MobRadar 30 Enter (WaitForMob) Line#: 5653
[2019/01/22 20:25:54] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:54] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:54] [MQ2] DEBUG MobRadar 75 Enter (CheckForCombat) Line#: 5653
[2019/01/22 20:25:54] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:54] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:55] [MQ2] DEBUG MobRadar 75 Enter (Assist) Line#: 5653
[2019/01/22 20:25:55] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:55] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:55] [MQ2] DEBUG  CheckForAdds: Enter from CheckForCombat Line#: 2419
[2019/01/22 20:25:55] [MQ2] DEBUG MobRadar 75 Enter (CheckForAdds) Line#: 5653
[2019/01/22 20:25:55] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:55] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:55] [MQ2] DEBUG MobCount:1 Line#: 2421
[2019/01/22 20:25:55] [MQ2] DEBUG MobRadar 75 Enter (CheckForCombat) Line#: 5653
[2019/01/22 20:25:56] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:56] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:56] [MQ2] DEBUGBUFFS Event_Timer Enter Line#: 10343
[2019/01/22 20:25:56] [MQ2] DEBUGBUFFS Event_Timer leave Line#: 10360
[2019/01/22 20:25:56] [MQ2] DEBUG MobRadar 75 Enter (Assist) Line#: 5653
[2019/01/22 20:25:56] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:56] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:57] [MQ2] DEBUG  CheckForAdds: Enter from CheckForCombat Line#: 2419
[2019/01/22 20:25:57] [MQ2] DEBUG MobRadar 75 Enter (CheckForAdds) Line#: 5653
[2019/01/22 20:25:57] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:57] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:57] [MQ2] DEBUG MobCount:1 Line#: 2421
[2019/01/22 20:25:57] [MQ2] DEBUG MobRadar 75 Enter (CheckForCombat) Line#: 5653
[2019/01/22 20:25:57] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:57] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar 75 Enter (Assist) Line#: 5653
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:58] [MQ2] DEBUG  CheckForAdds: Enter from CheckForCombat Line#: 2419
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar 75 Enter (CheckForAdds) Line#: 5653
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670
[2019/01/22 20:25:58] [MQ2] DEBUG MobCount:1 Line#: 2421
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar 75 Enter (CheckForCombat) Line#: 5653
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar MobCount=0 but Mob on Xtarget Setting Mobcount to 1 Line#: 5667
[2019/01/22 20:25:58] [MQ2] DEBUG MobRadar Leave 1 Line#: 5670

 

[ctaylor22]

Ok. The first time you run out to pull, the mob wonders out of MaxRadius.

[2019/01/22 20:25:10] [MQ2Nav] Navigating to spawn: an_elite_ikaav_firebrander01 (8918)
[2019/01/22 20:25:11] <PULLERTANKNAME>  [20:25:10] PULLING-> an elite ikaav firebrander <- ID:8918 at 572 feet.
[2019/01/22 20:25:19] [MQ2Nav] Reached destination at: 1792.00 752.00 68.59
[2019/01/22 20:25:19] [MQ2Nav] Stopping navigation
[COLOR=rgb(209, 72, 65)][2019/01/22 20:25:19] [MQ2] We have exceeded max pulling radius or timer or lost path to mob. Returning to camp[/COLOR]
[2019/01/22 20:25:19] [MQ2] DEBUG EndMacroIf: Enter Line#: 4826
[2019/01/22 20:25:19] [MQ2] DEBUG EndMacroIf: Leave Line#: 4849
[2019/01/22 20:25:19] [MQ2] DEBUG DoWeMove: Enter Line#: 3105
[2019/01/22 20:25:19] [MQ2Nav] Navigating to loc: 1225.00, 2115.00, 21.00
[2019/01/22 20:25:28] [MQ2Nav] Reached destination at: 2115.00 1225.00 21.00
[2019/01/22 20:25:28] [MQ2Nav] Stopping navigation

See the. We have exceeded max pulling radius or timer or lost path to mob. Returning to camp. line?

The next time he goes and pulls he returns to camp and gets hit by a mob.

[2019/01/22 20:25:53] [MQ2] I got hit by >>An elite ikaav firebrander<< ID: 0 while waiting for mob.


So I am not seeing the issue.

 

[dreamflux]

No. It's a static mob standing at 572 feet while the pullradius is set to 800. It's NOT out of range.

I definitely see the issue, but it's erroneous.

 

[ctaylor22]

OK first things first, did you turn on DebugAll? I just noticed a lot of the debug code in the pullusingnav routine is NOT in the log.

 

[dreamflux]

I tried and it told me it wasn't a valid command. I redid my aliases and it said the same thing.

 

[ctaylor22]

your using /debugall? debugall is now a bind not an aliase. Just make sure you don't have an /debugall aliase in your macroquest.ini file, and /debugall will only work while kiss is running.