darkeros
Member
- Joined
- Sep 12, 2004
- RedCents
- 35¢
TL;DR: If you are pulling with KA in a situation where you often get debuffed/snared and you want to only pull when you have no debuffs, this will wait until after the combat cooldown period to make sure you have no debuffs. It is slower than normal pulling because it waits until after the cooldown period of every kill to pull, but at least I'm not dying to stupid debuffs.
GroupWatchOn=1
GroupWatchCheck=cond1
In your condition section, make a line for:
Cond1=(${Me.CombatState.Equal[COOLDOWN]} || ${Me.CombatState.Equal[DEBUFFED]})
Longer version:
Admittedly, I'm a newb to KA and it's been years since I've been knowledgeable about MQ2 TLO's (just coming back to the game), but I wanted to share this since I've seen it asked here on RG several times and I never saw a good answer that specifically used KA built-ins to make it work. I did lots of searching, reading, and attempting different things in-game to finally land on this simple answer.
In @Maskoi KA guide, it says for a GroupWatchCheck you can add ${Me.Snared}, except when I am snared and that GroupWatchCheck runs, KA errors saying "unparsable in calculation: 'V'". I was searching for an alternative. I ran across {Me.CombatState[DEBUFFED]}, but it was still pulling. I tried modifying the actual kissassist.mac in the FindMobToPull section as mentioned in a few posts from 2019 on this topic, but ${Me.Snared} caused the macro to die again and {Me.CombatState[DEBUFFED]} still didn't seem to be kicking in. Finally, the light bulb... DEBUFFED combat state isn't kicking in before my next pull because the COOLDOWN combat state is still in effect for 30 seconds after mob death. ${Me.CombatState[DEBUFFED]} doesn't return TRUE until after the {Me.CombatState[COOLDOWN]} that occurs after you kill a mob ends. This resulted in being debuffed and still pulling, so I added both of these combat states to a condition and BAM it worked. It waits until after the cooldown period and if there are any debuffs it will wait until they run out. At least it is successful in my limited testing so far. If you try it and get a failure, please post and let me know the situation.
GroupWatchOn=1
GroupWatchCheck=cond1
In your condition section, make a line for:
Cond1=(${Me.CombatState.Equal[COOLDOWN]} || ${Me.CombatState.Equal[DEBUFFED]})
Longer version:
Admittedly, I'm a newb to KA and it's been years since I've been knowledgeable about MQ2 TLO's (just coming back to the game), but I wanted to share this since I've seen it asked here on RG several times and I never saw a good answer that specifically used KA built-ins to make it work. I did lots of searching, reading, and attempting different things in-game to finally land on this simple answer.
In @Maskoi KA guide, it says for a GroupWatchCheck you can add ${Me.Snared}, except when I am snared and that GroupWatchCheck runs, KA errors saying "unparsable in calculation: 'V'". I was searching for an alternative. I ran across {Me.CombatState[DEBUFFED]}, but it was still pulling. I tried modifying the actual kissassist.mac in the FindMobToPull section as mentioned in a few posts from 2019 on this topic, but ${Me.Snared} caused the macro to die again and {Me.CombatState[DEBUFFED]} still didn't seem to be kicking in. Finally, the light bulb... DEBUFFED combat state isn't kicking in before my next pull because the COOLDOWN combat state is still in effect for 30 seconds after mob death. ${Me.CombatState[DEBUFFED]} doesn't return TRUE until after the {Me.CombatState[COOLDOWN]} that occurs after you kill a mob ends. This resulted in being debuffed and still pulling, so I added both of these combat states to a condition and BAM it worked. It waits until after the cooldown period and if there are any debuffs it will wait until they run out. At least it is successful in my limited testing so far. If you try it and get a failure, please post and let me know the situation.
Last edited:
