Question - Question about /echo return values on an {IF[...True,False]} test

[rokn2day]

Iv'e been trying to wrap my head around the new conditionals in Kiss 10.x. To learn a bit about what can be done I've been doing a lot of testing and using /echo ${something here} to understand what values should be expected. To test for the presence of an existing disc I am using:

!${If[${Me.ActiveDisc.ID},TRUE,FALSE]}

This returns !FALSE or !TRUE depending on a disc being active.

My question is, does the ! in front of the TRUE or FALSE need to be stripped so that the return value is evaluated correctly, and if so how would I go about doing that?

Thank you.

 

[exocet]

Here take a look at this "DPSCond11=${Me.XTarget}>2 && !${Me.CombatAbilityReady[Rallying Roar]}" ok so I have very very limited knowledge about condi's however from what I know the ! is needed to compare operand values I believe I am assuming it would need to be in place.

 

[Rooster]

Well the ! is simply to say NOT -what ever is evaluated- ie NOT TRUE, or NOT FALSE.

So if you want something to fire because you have no disc running, !FALSE = TRUE (it will fire). and !TRUE=FALSE (it won't fire) as you have in your code above. Using an ${If[,TRUE,FALSE]} you can simply reverse the TRUE/FALSE if you like, or you could replace the TRUE/FALSE with a command/another ${If[,TRUE,FALSE]} etc.

 

[eqmule]

Don't over complicate conditions. They are simple.
Just do

DPSCondition1=!${Me.ActiveDisc.ID}

That means if there is no active disk running then cast DPS1

Embedding [If[blah blah] in a condition is a abomination and should never be needed, I have yet to come across a scenario when you would have to use it. On that note don't use any of the cast ready or ability ready etc either, that is redundant since kiss checks if stuff is ready before it moves on.

 

[ctaylor22]

Don't over complicate conditions. They are simple.
Just do

DPSCondition1=!${Me.ActiveDisc.ID}

That means if there is no active disk running then cast DPS1

Embedding [If[blah blah] in a condition is a abomination and should never be needed, I have yet to come across a scenario when you would have to use it. On that note don't use any of the cast ready or ability ready etc either, that is redundant since kiss checks if stuff is ready before it moves on.

Well I have. Anytime you want a true condition to return a false and a !True condition Just won't work.

But you shouldn't have to use the ${If[]} in a condition for kiss.

 

[rokn2day]

I want to thank you all for the thoughtful responses and taking the time to help improve my understanding of conditionals and how to use them with Kiss. EQMule, it's time I donated to you again sir. I have in the past contributed to you directly as well as the MQ2 dev's and others involved in MQ2. I appreciated your direct and easy to read suggestions. CTaylor22, I think our minds work somewhat alike. It's easier for me to understand !${...True,False} returning false for some reason, but I'm going to try to be a better macro'er and follow EQMule's suggestions of keep it simple stupid. Exocet and Rooster, I want to thank you both as well for taking the time to reply and while no one answered my question which I obviously asked badly, I have figured it out through trial and error.

If you do a /echo !${...True,False} in game it will return either "!TRUE" or "!FALSE" Kiss and associated plugin's strip the proceeding "!" and only evaluate TRUE (1) OR FALSE (0). You do not need to worry about doing a $Left[... to strip the "!" within conditionals.

 

[ctaylor22]

Your most welcome.. That's what we are here for.. I don't expect everyone to agree with me and I never take offence, because I know everyone has their own way of skinning a cat... I just try to reflect a little light on what I do and why. I never take the position that my way is the only way.. EQMule is correct and I agree with him, in his trying to advise you in NOT using ${If[]} statements in your Conditions in kissassist.

I advise everyone on thinking twice on using the ${If[]} statement in a condition, but there could always be that one instance where the ${If[]} statement, may be the only way to get the conditions to work, So only use it if you have to, but our suggestion is try not to use it..