Problem - Main tank doesn't engage if puller brings back an add

[Incognito]

I should retitle this to Adventures in learning how to multi-box'.

Ok, hoping the veterans will chime here. My Mnk puller is smart enough that if he gets an add enroute to the mob he planned to pull, he brings it back to camp. Now maybe his target is still on the mob he intended to bring and that is why the tank wont engage.

How do I get him to target the added mob he actually brought back? He's waiting to assist the tank, who is waiting for him I dunno what, hand the tank a valid in camp aggro'd TargetID? Now that I think about it, that's prolly it! They all standing around waiting for him to pass a vaild TargetID while the healer dies!

Often I have watched an add in camp, either by wandering by, or the puller bringing it back when it wasn't his intended target, and everyone in grp doesn't engage because the targeted mob is either too far out (never got aggro'd) or since no one is attacking it his HP doesn't trigger assist. I have the tank to assist at 100 to try and reduce this, but it doesn't always work. The down-side to 100% is that occasionally, the tank will run 500 meters out to engage the mob the puller is bring. I tried setting the tank's camp size small (20), and campradius to 50, still does it.

Now I know most issues of this kind relate to launching KA with the wrong grp member targeted. Here is how I have it set up, please correct me if I am wrong.

The MA is also the Tank, assists at 100%, and targets the puller at launch. Me, the SHM, targets the Tank at launch, assists at 100%. The Mnk, puller, targets Tank at launch, assists at 95% to let aggro shift to the tank. That seems perfectly reasonable to me, what am I missing?

The tank does not engage mobs in the extended target window that the puller/monk doesn't target. I left it to see if anyone will eventually attack it and watched the merc healer die. Gotta love heal aggro.

Now, when I intervene, most of the time, all I have to do is take control of the tank and target the uncontested mob. I don't know why it wont do it on its own. I have a J5 tank merc that I keep on passive until an emergency erupts (we are both 10 lvls higher than the grp). That tank merc always knows what to do, always goes after the uncontested mob. I can't put it away until I know the grp functions well on its own...

Hell I've even seen the puller go out and pull again when there is a mob beating on the healer uncontested. They just don't seem to be aware of camp aggro or the extended target window.

Now any time this happens, oddly enough, NinjaLoot stops managing the loot so I have to stop and go through all the crap drops. How does it know that something went wrong, and know to try to make it worse is beyond me...

As I was writing this, my SHM had some mob targeted that was not in camp and not being killed. The toons get a TargetID stuck in their heads and wont let go. I'll bet ya anything that NinjaLoot was waiting for the ID stuck in my head to die before kicking in...

There is definitely some logistic acrobatics you have to manage to multi-box. One time, I sent a /bcg //command and the eqbc chatwnd sent the command to everyone but the tank, saying that no such name exists. I raised my eyebrows; clear as day, Ima lookin at it, its right there! I disband the tank, re-invite, re-accept, try again, and same msg. Ima scratchin my head, lookin right at the tank, in grp, until I realized I had not logged the tank into EQBC...

Anyway, any help is appreciated,

~ Incognito

- - - Updated - - -

I reset everything, this time the tank targeting itself, and things seem to be better.. Ima watch a bit and see if it's smooth sailin now...

Well gawdamit, that seemed to be the issue. I should prolly delete this post, or start a poll to see if I should. No, wait, Ima spend redcents and change my title to DumbAzz for one week!

 

[Randyleo]

I'm having the same issue, even tried a different tank. The tank doesn't pick up that there is a mob in camp. The mob can be in xtarget 1 (autohater) and unless I click on xtarget 1 he just stands there.

 

[Incognito]

Well for me, having the tank target itself at launch seems to have solved my problem. I will watch it awhile to be sure, but so far...

 

[Randyleo]

I have always had the tank target themselves at KA startup.

Additional info: If you don't set the main assist in group it no long automatically sets it in KA. Before last night it would. Setting group roles does not help.

 

[Meistro]

Iff tank and pulller are separate toons, tank must target self so he will then attack any mob in his camp radius, no matter how it gets there.
If tank targets puller, tank is waiting to assist the puller and everyone else to assist the tank. This leads to the tank waiting for the mob the puller targeted (if it gets to camp before a wipe) and the tank waiting for the puller to target the add while the puller waits for the tank to do it.
So in conclusion, All toons should generally target the denoted MA/MT.

 

[wowfool]

Check your camp radius, any chance its too small? Try bumping it up a bit on your tank and see if he is a little more responsive. I've noticed that when my puller was not the tank he would tend to stop a little too far for the camp radius and the tank/CC would not take care of business until the inevitable healer aggro after the puller gets a heal and the mob finally gets to camp. So try making the radius smaller on the puller and larger on the tank and see if that helps. The tank should pick a mob from the hate list, and then everyone else assist at the proper hp %.

 

[Randyleo]

My issue went away when I changed to another zone this morning. I made no changes besides moving out of The Grounds.

 

[ctaylor22]

My issue went away when I changed to another zone this morning. I made no changes besides moving out of The Grounds.

This sounds like an issue with what is in your KissAssist_info.ini file. I would check the section for the grounds and see if you have a mob that is setup for ignore.

 

[Meistro]

This sounds like an issue with what is in your KissAssist_info.ini file. I would check the section for the grounds and see if you have a mob that is setup for ignore.

While doing this, look for a duplicate entry for the grounds (have had it happen).
Also note: If you put names in the "mobs to pull" section, it seems to ignore all mobs other than those designated.

 

[Rustycat]

While everyone has posted good things to check on this, I would ask that you post your tanks ini file to review. I've seen a tremendous amount of posts regarding tanks not engaging when mobs are pulled into camp. 90% of them the issue has been the tank has some form of buffs, self or otherwise depending on class that is not set up correct with typo(although the spell check has caught most of this) or lack of DUAL tag etc. They hit the loop to do the buff and are hung because it's not right and thus ignores the rest of the world unless you manually have them target and attack the mob in camp.

Also, another trick you can do if your puller is capable as a back up, is use pullertank instead of puller. On a previous revision of KISS, there were some hang ups that I think were sense resolved. This was my work around at the time and I still use it to this day having all my other toons assisting off the pullertank rather than the primary tank.

 

[Randyleo]

I'm at work right now, so I'll post his ini when I get home. Wouldn't an error in the ini show up in all zones, not just Grounds?

 

[Incognito]

*** Update *** Meistro has it right, that's exactly what it was doing, tank looping thru waiting for the puller to engage while the puller was waiting for the tank to engage, at least in my particular situation. I ran this all night with the only hiccup being I found the mnk puller dead... I have it now where everyone targets tank at launch, and tank targets itself, and I see no anomalies. I believe this should be true for Hunter and Pullertank as well.

~ DumbAzz

 

[Randyleo]

I found several error in my Kissassist_info.ini, fixed those, now it is working fine.