Mission Editor - what do == and != mean?
 

Hi guys,

This is probably a simple maths/math question - for the triggers for say, damaging a ship by percentage, what do == and ! mean? I have < and > sorted (the crocodile eats the bigger number - thanks primary school!) :ping:

Cheers
Stew

a == b means "is a equivalent to b?" (not to be confused with a signal = which signifies setting a variable's value or state)

5 == 5 returns true, 5 == 4 returns false

a ! b means "is a not b?" So, any two different values will return true, identical values will return false.

Hope that helps.

Thanks Chazly for the helpful and speedy reply.

So, just to clarify, in my trigger - I can set it to damage the 'enemy ship' to an equivalent of 50% (==). Do you know what that means in the context of the what the trigger will do?

Also, what does != mean in the context of damaging a ship in a trigger? Sorry, that was a typo on the original post :03:

Stew

I have thoughts, but rather than guessing, could you post an example of code showing this?

Thanks Chazly, here is a screen cap - you can see the options in the top right of the picture :03:

http://img.photobucket.com/albums/v3...ps225iaqlt.jpg

Using < or > is much safer in DW editor than == because it gives you wider range for success.

Example:

If you want to send message (S.O.S. - my ship is sinking!) when CVG have half or less health with code:
and your opponent hit CVG 16 two times for 36% - trigger sometimes can't be launch because 36+36=72
72 > 50 but not equal exactly 50

So better version of this trigger is:
< or > are also better to time event activation

I concur. :D I think < and > are sufficient for these purposes, == is too specific and is unlikely to be true. You could have, for example, damage != 100 % to say that "if it's not 100% damaged, do this" but you could accomplish that just as easily with damage < 100%.

Thanks for your help, guys - no wonder == and != aren't taught in primary school math/maths...

:Kaleun_Cheers:

I learned something, thank-you. I am having trouble with the Editor, but I will ask in a separate thread.