Question - SOLVED: Puller breaking leash and never returning to camp

[fuzzymelon]

I finally quit being lazy and read the Kissassist code to solve a problem I've been having with kissassist + MQ2Navigation whereby if my pullertank pulls a pathing mob past his PullRadius, he breaks his leash and never returns to camp. It's a very easy fix:

In the CheckRoles function, remove/comment the lines

/varset CampRadiusExceed ${MaxRadius}

Then make sure your CampRadiusExceed var in your INI file is large enough.

I doubt this will be changed in Kiss itself as I'm sure Maskoi had his reasons for this line of code as it is obviously intentional, but for those like me in zones with Pathers, this is a lifesaver, literally.

-Brian

 

[Maskoi]

That line sets your Campexceed to you Max pull radius so and you should never go beyond it. sounds like you have your camp radius set to large it should be between 30 and 50

 

[Hanlons Razor]

That line sets your Campexceed to you Max pull radius so and you should never go beyond it. sounds like you have your camp radius set to large it should be between 30 and 50

I have my camp radius set to 30 and if my puller chases a pather outside of the pull radius (say the mob runs out to 330 and my puller is only set to 310), the puller will stop, kill the mob on the spot (if he can), then never returns to camp.

 

[fuzzymelon]

Correct Kutsuu - this fixes that. As Maskoi said, he's intentionally overriding the campexceed for pullers so that they never go beyond their pull radius. However, as you and I have seen, with pathers, this isn't always the case and our puller gets stuck in limbo land.

 

[Maskoi]

That is something i will have to add to my list to fix in KA7 puller needs to be more aware at all times if he is near camp exceed or puller can never turn off return to camp while pulling