Limited code in triggers ?

[laggy]

Can anyone tell me why some variable conditions are possible in scripts but not triggers ?

For example, I have allways wondered why this works as trigger condition:

Code: [Select]

myVar1 AND myVar2 AND myVar3 AND myVar4 AND myVar5 etc.
Also.

Code: [Select]

myVar1 OR myVar2 OR myVar3 OR myVar4 OR myVar5 etc.
But not this:

Code: [Select]

myVar1 AND myVar2 AND (myVar3 OR myVar4 OR myVar5)
Another thing that works in scripts is:

Code: [Select]

_greeters =  nearestObjects [vehicle player, ["MAN"], 50];

sleep1;

while {true} do
 {
      {
        if (_x distance vehicle player < 5 AND side _x == west) then
        {
            hint "hello";
            sleep 1;
        };
      } forEach _greeters;
sleep 1;
 };


But in a trigger this doesn't work:

Code: [Select]

Condition: {_x distance player < 5} forEach greeters
onActivation: hint "hello"

Variable greeters initialized of course 

In fact the editor doesn't even accept the condition code 

Weird   

Laggy

[Spooner]

The former case definitely should work. Any problems with it are due to logical rather than syntactic errors (that is, it is acting as it should, but you are expecting it to act differently).

The issue with the latter case is that forEach always returns nil, so it isn't appropriate to be used directly in a condition. Instead, try:

Code: (Condition) [Select]

({_x distance player < 5} count (nearestObjects [vehicle player, ["MAN"], 50])) > 0
What this does is count how many men are close to the player, and the condition is true if one or more of them are. However, it is a lot simpler once you get more complex scripts, just to run them in files, not in triggers themselves, since they are designed for simple functionality.

Your script is also different to the action of a trigger, since it will say "hello" once for each person near the player and once every second in this case. A trigger version would say "hello" when someone approached, but not say it again until the player was on his own again and then someone new approached.

[laggy]

Thanks a lot again Spooner 

Had no idea that nil was returned if in a trigger, wish they'd tell you 

The former case definitely should work

Should yes, but I'm pretty sure it doesn't and I have had this editing problem since OFP, causing a need for additional triggers. My logic can't be THAT bad or... Will return after more extensive testing 

Laggy

[Spooner]

Well, anything that doesn't specifically return something returns nil. Mostly that isn't an issue, since the value is ignored when just one of the statements in a script. Unfortunatly, SQF does not follow accepted conventions of what does and what does not return a value, which doesn't help you even if you are experienced in such things elsewhere Just something you have to learn...

Yes, I think you need to give an actual example of where that and/or statement wasn't working. I still think you are mistaken, but...