Utility - Warrior Puller locks on NPC

[Pannone]

I'm running Kissassist Very Vanilla and when my warrior pulls he eventually gets to an NPC and stands there locked on the NPC until the mobs start popping and kills my group. He doesn't know enough to come back if my other players are under attack. Being a newbie at this, what do I need to adjust to get that to stop? I would like him to give up on a mob after 5 seconds and go to another mob if its not reacting. Also is there a script for him to guard other players in the group if they get agro?

 

[Sic]

if you have your tank to pull - you will want to ensure you have a /camphere on with your tank so he knows to return back

There's a vid in my signature that might help you

 

[wymranar]

Set him up as a pullertank, set return to camp to 1 in the .ini file, make sure Assist at is set at 100 (standard is 95).

when he gets stuck on a mob like that you can make a hotkey with /backoff

 

[Pannone]

I have him set to tank puller and he does a fine job until he locks on an npc and when it doesn't
aggro him he just locks up and stands there. Will the return to camp command fix that?

sic that's an awesome video thanks for that. I like how your war pulls with a ranged item, mine doesnt.

 

[MrPatate]

If the NPC is a quest giver or a non kill mob, you can just /addignore it so your puller won't try to pull it anymore

 

[Armyboxer99]

Ive seen this a few times on my Pullertank. An example of what happens in zones where mob pathing is poor (GMM!!) is that puller tags a mob and then runs back to camp with several mobs on Xtarg. The mob that he initially targeted gets stuck or paths far away and drops off aggro, but the pullertank remains fixated on the original mob whilst the other mobs that have made it back to camp continue attacking. Normally I have to pause macro and then kill manually and then have to restart Kiss, even when no aggro in Xtarget window Pullertank remains fixated on that original mob after macro is unpaused.

 

[earthsnemesis]

+1 this happens to me too; Particularly if it is a named mob. The tank blows all its CDs and then waits for something that will never come while adds rip apart the group. I usually have to restart the tank macro to get it to unfixate and work again.

 

[Maskoi]

If the NPC is a quest giver or a non kill mob, you can just /addignore it so your puller won't try to pull it anymore

This is the correct answer.

 

[Pannone]

Thanks. Is there a timer that I can set for pulls that he will ignore a mob or npc if it doesn’t Afgo him within a certain time period and maybe he will switch targets?

 

[ctaylor22]

Nope. There is a list of mobs to ignore, in the kissassist_info.ini file. You can add mob names to the list and the puller will ignore those mobs.

 

[Pannone]

Sic, I used your summons arrow line but my guy makes the arrows after every pull how do I stop that?

 

[Pannone]

BTW I uses a different warr Macro and he doesnt target any NPCs anymore I did use the ignore command on the old macro and it worked it was just a pain having to open it up constantly Thanks for the advise.

 

[Sic]

Sic, I used your summons arrow line but my guy makes the arrows after every pull how do I stop that?

he should only check when it goes to check buffs, since I have it set to 100, it will summon 100 (one click) and then summon another one next time it goes to buffs check --- you could just change it to 101, and it would click it twice to 200, and then not summon again until you are down low

 

[Pannone]

Hey SIC my arrows keep filling my bags i cast the spell prior to every pull I tried setting it to 101, tried 10, tried >10, >100, i tried everything just fills my bags and then when there is no room i stop pulling. I have the line in my buffs 7 line just like you

 

[Sic]

Hey SIC my arrows keep filling my bags i cast the spell prior to every pull I tried setting it to 101, tried 10, tried >10, >100, i tried everything just fills my bags and then when there is no room i stop pulling. I have the line in my buffs 7 line just like you

are you sure you don't have some duplicate entries in mq2melee settings or something?

It really sounds like it does not have a summon value - outside of that i've never heard of something just chain summoning until you're full bagg'd

 

[ctaylor22]

I have seen this happen before if the name of the summoned item is wrong.