- Joined
- Sep 12, 2004
- RedCents
- 720¢
As per our own documentation:
KissAssist 8 Instructions & Settings Info
And I Quote:
"Role=Tank - Sets up tanking feature which has 2 modes, assist and stand alone.
Assist Mode will target the puller's/MA's mob and attack when mob comes into defined melee range.
Usage: Set Role=Tank and select MA normally
Stand Alone will target and attack any aggressive mob that comes into defined melee range.
Usage: Set Role=Tank and select yourself as MA"
An issue has been reported over and over and over at various stages of the KissAssist evolution... but the devs could never quite pinpoint the issue at hand based upon the reported feedback/conditions provided.
The issue is as such:
Scenario ---
6 member group bot team... 1 Tank (sk), 1 puller (rng), 4 assisting toons (Clr,Rog,Brd,Mag).
Assisting toons all started with normal assist parameters from Social Hotkey:
Social Hotkey---
Label: KissAssist
Line1: /squelch /target clear
Line2: /squelch /target [Tank Name] pc
Line3: /macro KissAssist assist [Tank Name] 98
Puller started with normal puller parameter from social hotkey, assisting the tank:
Social Hotkey---
Label: KissAssist
Line1: /squelch /target clear
Line2: /squelch /target [Tank Name] pc
Line3: /macro KissAssist puller [Tank Name] 98
Tank started with tank parameter setting puller to MainAssist in order to pick up and get his pulled mob when in MeleeDistance:
Social Hotkey---
Label: KissAssist
Line1: /squelch /target clear
Line2: /squelch /target [Puller Name] pc
Line3: /macro KissAssist tank
Everything works fine and dandy if there are no adds on the pull, or nothing wanders into CampRadius during combat and gets mezzed by the bard.
However, if the puller pulls adds.. or adds wander through camp... and get mezzed ny the bard.. (Single or AOE mezz song) we run into a scenario where the tank sits there with his thumb up his arse and never attacks and breaks mez on the mezzed mobs in camp.
WHY????
1) The tank is assisting the puller (rng) who has the corpse of the first mob targeted... the tank doesn't move out of his stuck loop of not correctly getting addsincamp / mobcount set correctly because the ranger still has the corpse targeted.. The looter (rog) is not looting the corpse because he detects mobs in camp and will not loot while in combat state/xtarget adds detected...
2)If the ranger or tank target one of the mezzed mobs manually... or the rogue manually loots the corpse..... all progresses normal.. tank picks up correct adds in camp/mobcount value.. and cycles through mobs normally....
The quick down and dirty solution is to not have the tank have the puller as MainAssist and just play pure tank role.. attacking anything in the CampRadius/MeleeRadius... but this totally defeats the goal of us wanting KA to work with tank asssiting the puller.
I have brought the proposed coding solution to Maskoi's attention.. and its a quick fix... just awaiting feedback on how to progress.. and I will patch/notify the community of the KA revision with the perm solution.
I AM NOT BACK FOR GOOD... just stir crazy atm.. and noticed this issue myself.. and debugged everything to identify the issue with my debugger.
more to come...
THD
KissAssist 8 Instructions & Settings Info
And I Quote:
"Role=Tank - Sets up tanking feature which has 2 modes, assist and stand alone.
Assist Mode will target the puller's/MA's mob and attack when mob comes into defined melee range.
Usage: Set Role=Tank and select MA normally
Stand Alone will target and attack any aggressive mob that comes into defined melee range.
Usage: Set Role=Tank and select yourself as MA"
An issue has been reported over and over and over at various stages of the KissAssist evolution... but the devs could never quite pinpoint the issue at hand based upon the reported feedback/conditions provided.
The issue is as such:
Scenario ---
6 member group bot team... 1 Tank (sk), 1 puller (rng), 4 assisting toons (Clr,Rog,Brd,Mag).
Assisting toons all started with normal assist parameters from Social Hotkey:
Social Hotkey---
Label: KissAssist
Line1: /squelch /target clear
Line2: /squelch /target [Tank Name] pc
Line3: /macro KissAssist assist [Tank Name] 98
Puller started with normal puller parameter from social hotkey, assisting the tank:
Social Hotkey---
Label: KissAssist
Line1: /squelch /target clear
Line2: /squelch /target [Tank Name] pc
Line3: /macro KissAssist puller [Tank Name] 98
Tank started with tank parameter setting puller to MainAssist in order to pick up and get his pulled mob when in MeleeDistance:
Social Hotkey---
Label: KissAssist
Line1: /squelch /target clear
Line2: /squelch /target [Puller Name] pc
Line3: /macro KissAssist tank
Everything works fine and dandy if there are no adds on the pull, or nothing wanders into CampRadius during combat and gets mezzed by the bard.
However, if the puller pulls adds.. or adds wander through camp... and get mezzed ny the bard.. (Single or AOE mezz song) we run into a scenario where the tank sits there with his thumb up his arse and never attacks and breaks mez on the mezzed mobs in camp.
WHY????
1) The tank is assisting the puller (rng) who has the corpse of the first mob targeted... the tank doesn't move out of his stuck loop of not correctly getting addsincamp / mobcount set correctly because the ranger still has the corpse targeted.. The looter (rog) is not looting the corpse because he detects mobs in camp and will not loot while in combat state/xtarget adds detected...
2)If the ranger or tank target one of the mezzed mobs manually... or the rogue manually loots the corpse..... all progresses normal.. tank picks up correct adds in camp/mobcount value.. and cycles through mobs normally....
The quick down and dirty solution is to not have the tank have the puller as MainAssist and just play pure tank role.. attacking anything in the CampRadius/MeleeRadius... but this totally defeats the goal of us wanting KA to work with tank asssiting the puller.
I have brought the proposed coding solution to Maskoi's attention.. and its a quick fix... just awaiting feedback on how to progress.. and I will patch/notify the community of the KA revision with the perm solution.
I AM NOT BACK FOR GOOD... just stir crazy atm.. and noticed this issue myself.. and debugged everything to identify the issue with my debugger.
more to come...
THD
