Question about mage and puller

[virtuoso65]

Ok getting what I was getting before in other builds. bard is puller played by me with ka running as manual, mage is flagged as ma and starts ka with bard targeted, rest of group have mage targeted when they start ka. Bard goes out for pull and lull's/punts a mob and tags/pulls a mob to camp. The mage will have targeted the punted mob and the group will just stand there while the mob beats on the bard. MQ reports via ${Target.Distance} that the closest mob to the mage is 45 from her spot to its spawn spot.

CampRadius=30
CampRadiusExceed=400

MeleeDistance=40

Another question, is there a way to make the group kill something that wanders into camp without the bard targeting the mob to get the mage to target it? There are roamers and twice now a roamer has walked into camp and killed 1-2 toons before I could get the bard back in camp.

/edit well another one just happened, pulled a mob to camp, mage didnt target anything instead the whole group spit out this error. "There are no spawns matching: (0-200) any ID: 25756" I tried cycling my backoff/switchnow/backoff key but nada, I ended up just running everyone manually for that fight.

 

[Maskoi]

I moved this because its not really an Kiss11 bug report.

On your mage don't target the bard. Target the mage and use pettank role

The mage will tank mobs with pet as they run into camp

 

[virtuoso65]

Fair enough.

Ok been giving this method a shot and I have one question, what actuallly defines the fight engagement distance? It is not meleedistance as the mage is sending the pet at mobs 60+ away from her and the rest of the group is just standing around picking their nose. I blocked all movement speed buffs on the pet and it helps a bit but I would like the mob to actually get to camp before the rest attack as I am getting a ton of line of sight issues as is.

I am not trying to be a pain in the ass here, I am just at a loss as to how this is supposed to function as the expected is not matching reality.

 

[eqtrader74]

If you are using "pettank" mode, it is the mage's CampRadius distance, that is where KA would decide a mob is close enough for a "tank" to engage. Also, I think that CampRadius is based on the mage's location at any time, not the pet itself. I tried pet tanking at long range (like 150) a mob with large ae and noticed the pet would ignore the mob until it got closer to the mage.

If that looks OK and 30 seems fine, check your mage's MQ2melee plugin settings in their mq2 ini file (Release folder usually.) MQ2Melee can have a longer pet engage range and that can override KA.

 

[virtuoso65]

The mages file showed petrange=75, I set it to 20, did a /melee save, and tried again, mage is still sending pet mobs 50+ from where the KA macro and where she is standing. I tried plugin=0, saved and tried again, still attacking at 50+. What more decides when an npc engages other than those 3 things?

 

[eqtrader74]

I'm stumped, MeleeDistance was the other thing I was going to suggest, but it looks like you tried that. MeleeDist is definitely used in the MobRadar subroutine to see if there is anything close that needs to get attacked.

You could try eqmule's version of KA and see if it has the same issues. If that version is also doing it, you could check in with TreeHugginDruid who wrote the pettank part of KA.

 

[Maskoi]

UseMQ2Melee=0

will turn of any mq2melee settings

 

[ctaylor22]

PetAttackRange is what is used for sending in the pet when pet tanking. The default for PetAttackRange is 115. Just do a search in the macro for PetAttackRange and you will find where it is being set.