Hellos
Today I have been playing around some more with KissAssist, and in particular Conditions.
I had seen this example KA profile here (RNG Lv5)
They key bits of interest are:-
[CODE lang="ini" title="RNG lv 5 KA INI extracts" highlight="6,11"][DPS]
DPSOn=1
DPSSize=20
DPSSkip=20
DPSInterval=2
DPS1=Tangling Weeds|30|cond1
[KConditions]
ConOn=1
CondSize=5
Cond1=!${Target.Snared}[/CODE]
Now I can read that as looking to see if the target is snared, or rather is the target not snared, upon which the condition is true so it will cast the spell.
I was trying this condition out, and a few times - KissAssist (12) blew up....
Unparsable in Calculation: 'S'
(Main): /ini "${IniFileName}" "KissError" "LastCMD:" "${MacroQuest.LastCommand}"
(CombatCast): /call CastWhat "${DPSPart1}" ${DPSTargetID} DPS ${CondNo}
(Combat): /call CombatCast
(CheckForCombat(int SkipCombat, string FromWhere)): /call Combat
(Main): /call CheckForCombat 0 MainLoop2
The current macro has ended.
Accepting that KA normally behaves, and the only thing changed here to the profile is use of the condition, assume it is at fault.
The profile in the KA library is from a while ago, and pre-KA 12. It may have worked historically but doesnt now?
Regardless of possible history and changes etc, I require something that works now, in a profile being used by KA 12.
With some investigation, the output of ${Target.Snared}, is actually the name of the spell with a snared component on the target, or null, if there is not one.
Figuring the conditionals are just going to boil down to Boolean logic; true / false, and dont like strings or nulls.
The Bool object (detail here on MQ2 site) can wrap around another and convert to the desired trues or falses.
With that informaton to hand, amended from:
Cond1=!${Target.Snared}
To:
Cond1=!${Bool[${Target.Snared}]}
... and now the profile hasnt crashed with a while of execution.
Tested with mobs, with and without a "snare" debuff active as they moved from above to below the 30% HP trigger.
( 30%, remember as the DPS detailed 30. DPS1=Tangling Weeds|30|cond1 ).
Hope this information may be of use to others wondering about conditionals in KA.
As extra, the MQ documentation for Target (here), details there are more than just "Snared".
e.g. Maloed, Rooted, Slowed, and Tashed, stand out as things people may consider testing?
Regards and Best Wishes.
Today I have been playing around some more with KissAssist, and in particular Conditions.
I had seen this example KA profile here (RNG Lv5)
They key bits of interest are:-
[CODE lang="ini" title="RNG lv 5 KA INI extracts" highlight="6,11"][DPS]
DPSOn=1
DPSSize=20
DPSSkip=20
DPSInterval=2
DPS1=Tangling Weeds|30|cond1
[KConditions]
ConOn=1
CondSize=5
Cond1=!${Target.Snared}[/CODE]
Now I can read that as looking to see if the target is snared, or rather is the target not snared, upon which the condition is true so it will cast the spell.
I was trying this condition out, and a few times - KissAssist (12) blew up....
Unparsable in Calculation: 'S'
(Main): /ini "${IniFileName}" "KissError" "LastCMD:" "${MacroQuest.LastCommand}"
(CombatCast): /call CastWhat "${DPSPart1}" ${DPSTargetID} DPS ${CondNo}
(Combat): /call CombatCast
(CheckForCombat(int SkipCombat, string FromWhere)): /call Combat
(Main): /call CheckForCombat 0 MainLoop2
The current macro has ended.
Accepting that KA normally behaves, and the only thing changed here to the profile is use of the condition, assume it is at fault.
The profile in the KA library is from a while ago, and pre-KA 12. It may have worked historically but doesnt now?
Regardless of possible history and changes etc, I require something that works now, in a profile being used by KA 12.
With some investigation, the output of ${Target.Snared}, is actually the name of the spell with a snared component on the target, or null, if there is not one.
Figuring the conditionals are just going to boil down to Boolean logic; true / false, and dont like strings or nulls.
The Bool object (detail here on MQ2 site) can wrap around another and convert to the desired trues or falses.
With that informaton to hand, amended from:
Cond1=!${Target.Snared}
To:
Cond1=!${Bool[${Target.Snared}]}
... and now the profile hasnt crashed with a while of execution.
Tested with mobs, with and without a "snare" debuff active as they moved from above to below the 30% HP trigger.
( 30%, remember as the DPS detailed 30. DPS1=Tangling Weeds|30|cond1 ).
Hope this information may be of use to others wondering about conditionals in KA.
As extra, the MQ documentation for Target (here), details there are more than just "Snared".
e.g. Maloed, Rooted, Slowed, and Tashed, stand out as things people may consider testing?
Regards and Best Wishes.
