Question - OR statement in Conditions

[riordan]

Is there any way to do OR as opposed to AND (&&) within a kiss condition? In Holys and Downs this is normally || but I'm guessing that character is reserved in kiss .inis? I was hoping for something like below so that my AE taunts only fire as needed. The only thing I can think of doing this would be making a separate AE call for each mob and checking only 1 xtarget for each (IE Explosion of Spite|2, Explosion of Spite|3, Explosion of Spite|4, Explosion of Spite|5). This would get nasty quick with Explosion of Spite, Explosion of Hatred, and Stream of Hatred.

AE1=Explosion of Spite|2
AECond1=(${Me.XTarget[1].PctAggro} < 99 && ${Me.XTarget[1].ID} > 0 && ${Me.XTarget[1].ID} != ${AggroTargetID}) || (${Me.XTarget[2].PctAggro} < 99 && ${Me.XTarget[2].ID} > 0 && ${Me.XTarget[2].ID} != ${AggroTargetID}) || (${Me.XTarget[3].PctAggro} < 99 && ${Me.XTarget[3].ID} > 0 && ${Me.XTarget[3].ID} != ${AggroTargetID}) || (${Me.XTarget[4].PctAggro} < 99 && ${Me.XTarget[4].ID} > 0 && ${Me.XTarget[4].ID} != ${AggroTargetID}) || ${Me.XTarget[5].ID} > 0

 

[Rooster]

Re: OR statement in Conditionals

Yes, but that condition is redundant if you use ${XTAggroCount}

If you have >1 , use ae hate . If it's only one you just want to use your normal terrors

 

[riordan]

Re: OR statement in Conditionals

Ah nice, so basically ${Me.XTAggroCount[99]} > 0 would cover all my bases. Although it would fire off my AE hate options if I lose aggro on my primary depending on if kiss hits the AE routine before the Aggro routine, right? I was trying to keep AE options 'ready to snap adds' as opposed to popping them whenever the mob count was above 1.

 

[Rooster]

Re: OR statement in Conditionals

It would be a waste for using ae aggro by using >0 , and also 99 means your aggro has to drop to 98% before firing. Just use no parameter or 100

If you're worried about running out of ae hate spells, try setting the spell ae hate to a specific xtar slot being <100 aggro and one aa to another and the second aa as >3 using the xtaggrocount

 

[riordan]

Re: OR statement in Conditionals

Yeah based on the wiki, my first test was just straight ${Me.XTAggroCount} but that is returning 1 minus the total number of targets in the extended window, even when all of them are at the 100 optimal aggro. When i bump it down to 99, I got the expected 0 result. Maybe the actual call returns less than or equal?

My group makeup includes mezing, so the tank isn't losing agro on 'adds' due to damage. So I haven't had to worry about him kicking off AE hate continually. More often adds wander in and take out someone before the tank picks them up.

 

[Rooster]

Re: OR statement in Conditionals

I think you might be getting the 0 while 1 mob exists because of a non-auto hater Xtarget. if i have all auto hater on my cleric i get ${Me.XTAggroCount} = 1 when my bard has a mob on aggro, if i set bard and xtar 1 as main tank i get 0 on cleric with the same mob on aggro

So i guess that can be taken into consideration if you use them setting for this

 

[kaen01]

[AE]
AEOn=1
AECOn=1
AESize=5
AERadius=50
AE1=Loathing|2
AE2=Explosion of Hatred|3
AE3=Explosion of Spite|3
AE4=Scourge Skin|3
AE5=Stubborn Stance|3
AE6=Sholothian Carapace|3
AECond1=${Me.XTAggroCount} > 0
AECond2=${Me.XTAggroCount} > 0
AECond3=${Me.XTAggroCount} > 0
AECond4=TRUE
AECond5=TRUE
AECond6=TRUE

is how i do it.

if you want it to fire when its not the main mob you tanking, then you need to put in a check for the aggro on that mob

i forget what line that is, but that be something like

AECond1=${Me.XTAggroCount} > 0 && ${Me.PctAggro}>99

Aecond1=True if a mob dont have aggro on you, and true if your current target is 100 aggro, so cast ae.
Aecond1=True if a mob dont have aggro on you, and false if your current target dont have 100 aggro, so dont cast ae.

i think.

 

[saar]

couldnt you do

AECond1=${Me.XTAggroCount} > 0 && ${Me.SecondaryPctAggroPlayer}

then it would fire if someone out aggroed you

 

[riordan]

I ended up switching these to MASH in the hopes they would be more snappy. XTAggroCount appears to already ignore your primary target (IE, when I lost aggro on my main target these wouldn't fire). The normal XTAggroCount (default of 100) still continues to count all the mobs on in my extended targets window minus 1 (my main target). So true or not, I'm going with the idea that the function is 'actually less than or equal' not 'less than'. I literally setup a button to test in game (see below) and without fail the default would report non-'optimal' aggro levels for every baddie in camp - 1 when they were all mad at me (100). I also believe if my aggro would go above 100, which did happen sometimes (999 seems to be some type of max), they would not be counted by 'default'. The end result is actually pretty nice, although I sometimes have multiples firing at the same time. They are firing when I want them to fire though, which is more important.

Kiss Conditions Excerpt
DPS18=Explosion of Spite|3|Mash
DPSCond18=${Me.XTAggroCount[99]} > 0
DPS19=Explosion of Hatred|2|Mash
DPSCond19=${Me.XTAggroCount[99]} > 0
DPS20=Stream of Hatred|1|Mash
DPSCond20=${Me.XTAggroCount[99]} > 0

Testing XTAggroCount Hotkey
Page3Button5Name=Count Test
Page3Button5Color=0
Page3Button5Line1=/echo Default = ${Me.XTAggroCount}
Page3Button5Line2=/echo 99 = ${Me.XTAggroCount[99]}
Page3Button5Line3=/echo 100 = ${Me.XTAggroCount[100]}
Page3Button5Line4=/echo XT1 = ${Me.XTarget[1].PctAggro}, XT2 = ${Me.XTarget[2].PctAggro}, XT3 = ${Me.XTarget[3].PctAggro}, XT4 = ${Me.XTarget[4].PctAggro}, XT5 = ${Me.XTarget[5].PctAggro}, XT6 = ${Me.XTarget[6].PctAggro}, XT7 = ${Me.XTarget[7].PctAggro}