Problem - Kiss12 beta keeps changing my target.

[B_I_G__D_A_D_D_Y]

Version of KissAssist.mac?

12.001 Beta

When did your problem start?

I think since the beginning?

Character Role?

1. Assist

What class is having this issue?

1. Bard
2. Cleric
3. Enchanter
4. Magician
5. Shaman

How often does this issue occur?

Often

Can you reproduce the issue?

After killing a few mobs.

6 member group. 5 chars assisting my SK. SK is running in "Tank" mode. All other characters are running in "Assist" Mode.

With no mobs currently on aggro or showing on Xtarget (shouldn't be in combat mode at this point!).

Attempting to mez a clump of mobs. I "break" follow on my Chanter so I can move freely and get line of sight on a mob. I target a mob. My target instantly changes back to whatever my Main Assist (the Shadowknight running in Tank mode) has on target.

If I clear the target on the Main Assist then my Chanter instantly clears their target. This will not stop unless I pause KISS on the enchanter!

With the macro paused I can freely target anything I want.

But I don't really want to pause the macro because once I cast an AE mez all the unmezzable or resistant mobs are going to jump on the chanter. I want to be able to move quickly back to the tank and have every character doing their thing so that the chanter lives through the pull.

I have attached an mlog from the chanter while /debugall was enabled.

This issue has been going on for a long time but I just today reviewed how to grab a log capture for analysis. So I'm finally dropping that log. I have replaced each character name with their class in the log. The log represents just a few seconds of time while I was on the enchanter and trying to target a mob for casting an AE mez spell.

 

[kaen01]

this is normal behavior, when you have him on assist mode, technically you could run him on tank mode i suppose that way you can freely pick and when mobs come to camp he will engage them as normal with mezzes and what not. i think.

however many of us who take control of a character just pause and unpause, literally all my toons has a pause/unpause toggle button on hotkey 3.

 

[B_I_G__D_A_D_D_Y]

this is normal behavior, when you have him on assist mode, technically you could run him on tank mode i suppose that way you can freely pick and when mobs come to camp he will engage them as normal with mezzes and what not. i think.

however many of us who take control of a character just pause and unpause, literally all my toons has a pause/unpause toggle button on hotkey 3.

That's fine, but this is not the same behavior as Kiss 11 or 10. If you're not in Combat or not actively buffing then why shouldn't you be able to target whatever you want manually?

 

[Many_Whelps]

Actually, Kiss11 does this as well.

 

[kaen01]

i know if you have healing set up it does it more frequently for sure

 

[ctaylor22]

Kiss, by default will try and kill your target you have when assisting off the MA. Kiss will persist on that target until the mob is dead. This is by design. I do have a note to add this functionality in the future, but here is the biggest problem. When you switch your target on the Mezzer, that target now becomes the mezzers new persistent target. What is the mezzer suppose to do kill it, debuff it, or mezz it? Lets say he mezzes it, after mezzing what target is he to switch back too? Oh wait he is not suppose to switch targets, so now you have to manually switch the mezzer back to the tanks current target.

Do you see how this is going to complicate things and KISS stands for?

 

[B_I_G__D_A_D_D_Y]

Kiss, by default will try and kill your target you have when assisting off the MA. Kiss will persist on that target until the mob is dead. This is by design. I do have a note to add this functionality in the future, but here is the biggest problem. When you switch your target on the Mezzer, that target now becomes the mezzers new persistent target. What is the mezzer suppose to do kill it, debuff it, or mezz it? Lets say he mezzes it, after mezzing what target is he to switch back too? Oh wait he is not suppose to switch targets, so now you have to manually switch the mezzer back to the tanks current target.

Do you see how this is going to complicate things and KISS stands for?

I agree with you when the group is in combat mode. My complaint is that the macro keeps changing my target when I'm not in combat and have absolutely zero mobs on Xtarget and I have zero mobs with anyone in the group on their hate list. For example I could be trying to do a quest turn-in. If the MA has themselves targeted because they just did a self-buff then everyone else in the group running KISS will have the MA targeted and you will be unable to target the quest monkey.

Sure, I can hit the group MQP button I've made but do you know how many times I've wiped because I forget to turn off the MQP button?

I'll admit, I want to have my cake and eat it too! I run my group with KA running on every character but then I drag them around manually and do quests and stuff. And another thing I like to do is position the group, then switch to the shaman or the enchanter and use their AE abilities to pull a clump of mobs. I hate having to pause the macro for the fraction of a second it takes to jump on the chanter, target a mob, and manually cast AE mez. If the macro is still running then all the characters do their thing automatically when that clump of mobs comes running for when Mez is resisted or shaman AE root. Again, this is BEFORE combat begins.

 

[ctaylor22]

If the shaman and the enchanter are in the same group, then the second one of them casts on a mob, and Xtargets get populated, Kiss now thinks it needs to be in combat. I will make a note to look at the the Assist code and see why the target gets cleared when the MA has no target and see if it can be altered without causing a problem.

 

[B_I_G__D_A_D_D_Y]

If the shaman and the enchanter are in the same group, then the second one of them casts on a mob, and Xtargets get populated, Kiss now thinks it needs to be in combat. I will make a note to look at the the Assist code and see why the target gets cleared when the MA has no target and see if it can be altered without causing a problem.

The target gets cleared BEFORE I aggro anything. I've said this at least 3 times now. The macro forces everyone to match the MA's target OR HIS LACK OF TARGET! IF the MA has a blank target then everyone assisting will be forced to a blank target and it's almost instantaneous. I can't manually target something long enough to cast on it! And this happens when the group is invis with nothing on aggro and nothing on Xtarget!

 

[Rooster]

I use a broadcast key that will unpause my macro/plugin if it's not running, i also have a habit of simply stopping all macros/plugins during non killing quest stuff.

Things start up pretty quick these days to simply startup upon aggro,and hell if I know what buffs half my characters use so I don't know if any are missing :-P

I created alias' so I can broadcast them or simply type them easy also

 

[ctaylor22]

@B_I_G__D_A_D_D_Y , I am on my group trying to duplicate this issue, and I am not able to even get my toons to target the same mob the MA is targeting, if there are no targets in the XTarget window. Now all my toons are in the same group. When I clear the MA target the casters don't clear there targets. When I target a mob with my Enchanter the mob stays targeted and his target is not getting cleared.

 

[B_I_G__D_A_D_D_Y]

@B_I_G__D_A_D_D_Y , I am on my group trying to duplicate this issue, and I am not able to even get my toons to target the same mob the MA is targeting, if there are no targets in the XTarget window. Now all my toons are in the same group. When I clear the MA target the casters don't clear there targets. When I target a mob with my Enchanter the mob stays targeted and his target is not getting cleared.

The behavior usually manifests after a period of time playing. Lately I haven't had time to log in. I will try and do a better job of documenting the circumstances once I get back to playing.

 

[ctaylor22]

@B_I_G__D_A_D_D_Y NP.

 

[wymranar]

@B_I_G__D_A_D_D_Y and @ctaylor22 i have also noticed this issue.