[SOLVED] if not....

Anonynn
20 Feb 2016, 22:50So I'm having a little problem and I'm wondering how I'd go about fixing it. I have a "Script" that has this scenario in it...
{if not player.orientation=asexual:Blah blah!}{if player.orientation=asexual:Blah blah...} --- but the "not" seems to be malfunctioning and always appearing in the player text during the game.
Logically, to me, it makes sense but the text processor in Quest seems to have trouble recognizing it.
What's strange is...it works fine in actual "if scripts"
If expression not (player.orientation=asexual) {
then ..
}
Anyone have any ideas how I could fix this?
{if not player.orientation=asexual:Blah blah!}{if player.orientation=asexual:Blah blah...} --- but the "not" seems to be malfunctioning and always appearing in the player text during the game.
Logically, to me, it makes sense but the text processor in Quest seems to have trouble recognizing it.
What's strange is...it works fine in actual "if scripts"
If expression not (player.orientation=asexual) {
then ..
}
Anyone have any ideas how I could fix this?

Anonynn
20 Feb 2016, 23:14Nevermind! I figured out the problem. If you do...
{if player.orientation_as_int>asexual}{if player.orientation=asexual} then it still covers all the bases! Sorry I didn't think of that before.
{if player.orientation_as_int>asexual}{if player.orientation=asexual} then it still covers all the bases! Sorry I didn't think of that before.

jaynabonne
21 Feb 2016, 09:28You can also use "<>" for "not equals". (And =, >=, <=, <, > for the others).
I can understand why people use "not x = y" instead of "x <> y" given the pain of having to CDATA scripts that have those symbols, but it's easy for that latter form to disappear from community consciousness, which would be a shame.
I can understand why people use "not x = y" instead of "x <> y" given the pain of having to CDATA scripts that have those symbols, but it's easy for that latter form to disappear from community consciousness, which would be a shame.