Problem - Melee Chars "hang" Constantly

[Tovin]

I've been using Kiss for about a year and a half now and I've finally "cracked" on my ranger (and at times, bard). I have an incredibly frequent problem in that my ranger will not "Chase" when using KissAssist. I think the issue is more complicated in that the character hangs and will move in a number of situations. In particular:

1) After zoning my ranger, and sometimes bard, will just sit on the other side of the zone in.
2) When activating Kiss it will launch appropriately but stop at the bard where it is supposed to bring up the Blocked Spells window.
3) Sometimes after killing a mob the ranger will stop chasing.

The only way for my ranger to resume is typically to run around for 15 seconds. At this point the Chase will kick in and he will head towards the MA.

Looking for some advice on how to solve the issue or at least debug it. Happy to provide more info to the extent you can tell me how to access it. The problem has persisted for more than a year (i always use the latest version of Kiss) and only happens on melee characters, primarily the ranger.

Thanks folks.

 

[ctaylor22]

Make sure you toons are not invised when starting kiss. That's what they do when they are invised is hang at buffs, when you would see your blocked buffs being read.

 

[Tovin]

Make sure you toons are not invised when starting kiss. That's what they do when they are invised is hang at buffs, when you would see your blocked buffs being read.

Thanks for the thoughts. Unfortunately it is significantly more than this. It occurs frequently after killing mobs or zoning when I'm not invis. It also only occurs on my melee characters, but never on my casters!

 

[ctaylor22]

what I would do is try and capture a debug log of them when it happens, this will let you review the log file and see what they are doing when you think they should be doing something else.

http://www.redguides.com/community/showthread.php/38744-How-Do-I-create-a-Debug-Log-for-KissAssist

 

[Tovin]

Re: Melee Chars "hang" Constantly

Thanks for the guidance again ctaylor. I ran the debugger and here is what the output was. Not really sure how to interpret it. Nothing looks wrong but I'm not entirely sure what it is supposed to look like. Any thoughts on how to check whether or not Chase is activated while the ranger is hanging like this?

[2016/05/07 18:09:48] [MQ2] DebugAll

[2016/05/07 18:09:51] [MQ2] Debug ALL On

[2016/05/07 18:09:51] [MQ2] CheckForCombat: Assist/Combat End Normal

[2016/05/07 18:09:51] [MQ2] DEBUG CheckForAdds: Enter from CheckForCombat

[2016/05/07 18:09:51] [MQ2] DEBUG MobRadar 200 Enter (CheckForAdds)

[2016/05/07 18:09:51] [MQ2] DEBUG MobRadar Leave 3

[2016/05/07 18:09:51] [MQ2] DEBUG MobCount:3

[2016/05/07 18:09:51] [MQ2] Sub CheckHealth Enter

[2016/05/07 18:09:51] [MQ2] DEBUGHEALS CheckHealth: Tank OOG: 100 28667 TRUE

[2016/05/07 18:09:51] [MQ2] DEBUGHEALS CheckHealth: -- Most Hurt:0 0 0 100

[2016/05/07 18:09:51] [MQ2] DEBUGHEALS CheckHealth: -- Most Hurt:1 0 0 100

[2016/05/07 18:09:51] [MQ2] DEBUGHEALS CheckHealth: -- Most Hurt:2 0 0 100

[2016/05/07 18:09:51] [MQ2] DEBUGHEALS CheckHealth: -- Most Hurt:3 0 0 100

[2016/05/07 18:09:51] [MQ2] DEBUGHEALS CheckHealth: -- Most Hurt:4 0 0 100

[2016/05/07 18:09:51] [MQ2] DEBUGHEALS CheckHealth: -- Most Hurt:5 0 0 100

[2016/05/07 18:09:51] [MQ2] DEBUGHEALS CheckHealth: (100 < 100) /call SingleHeal "" "" 100 0

[2016/05/07 18:09:51] [MQ2] Sub CheckHealth leave

[2016/05/07 18:09:51] [MQ2] DEBUG CheckForAdds: Leave

[2016/05/07 18:09:51] [MQ2] CheckForCombat MobCount: 3 AggroTargetID: 0 ChainPull: 1

[2016/05/07 18:09:52] [MQ2] CheckForCombat: Assist/Combat Begin Normal

[2016/05/07 18:09:52] [MQ2] DEBUGCOMBAT Assist Enter

[2016/05/07 18:09:52] [MQ2] DEBUG MobRadar 200 Enter (Assist)

[2016/05/07 18:09:52] [MQ2] DEBUG MobRadar Leave 3

[2016/05/07 18:09:52] [MQ2] DEBUGCOMBAT Assist0: Ranger ShadowKnight 34.88 3 0 12318 12318 TRUE FALSE 0 WAITING

[2016/05/07 18:09:52] [MQ2] DEBUGCOMBAT Assist1: Ranger ShadowKnight 34.88 3 0 0 0

[2016/05/07 18:09:53] [MQ2] DEBUGCOMBAT Assist: validatetarget ID:12318

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT ValidateTarge Enter Target Name:Alchemist Gille ID:12318 Spawn Name: NULL ID:NULL

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT ValidateTarge Validate 1

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT ValidateTarge Validate 2

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT ValidateTarge Validate 3

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT ValidateTarge Validate 4

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT ValidateTarget Leave

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT Assist Target:Alchemist Gille ValidTarget:1 Marco Return:1

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT Assist MyTargetName:Alchemist Gille ID:12318

[2016/05/07 18:09:56] [MQ2] DEBUGCOMBAT Assist Leave

- - - Updated - - -

Okay, just ran the debugger for the point in time where it "corrects" the issue. This is what fixes it. Seems like DoWeMove just isn't getting called until I run far enough away from the main assist???

[2016/05/07 18:34:14] [MQ2] DEBUG DoWeMove: Enter
[2016/05/07 18:34:14] [MQ2] DEBUG ChaseAssist
[2016/05/07 18:34:14] [MQ2] DEBUG DoWeMoveChaseAssist) My distance from (Shadowknight) is: (153.46).
[2016/05/07 18:34:14] [MQ2] DEBUG ChaseAssist MA distance check
[2016/05/07 18:34:16] [MQ2] DebugAll
[2016/05/07 18:34:17] [MQ2] DEBUG DoWeMove: Leave
[2016/05/07 18:34:17] [MQ2] DEBUG DoMiscStuff Enter
[2016/05/07 18:34:17] [MQ2] DEBUG DoMiscStuff Leave
[2016/05/07 18:34:17] [MQ2] DEBUG CanIDoStuff Enter

 

[ctaylor22]

Try making your MeleeDistance something smaller than 200 something more like 75.

 

[Meistro]

Not sure on bard, but with the ranger, when he "hangs" is he meaning/waiting to cast a spell possibly?. My best will do this as I have a pet buff with a long refresh that needs recast after every fight if it procs. So busy will member spell, and wait till it can cast spell, then cast, then "chase".
Just something to look at...might (I said might) be a possible for bard as well, but wouldn't know.