Trigger = script continue

[max_killer_payne]

What would I put in my script that would make it continue once a trigger was active, would I put something like this? I want the loop to detect if the trigger has been activated and if it has, I want it to go onto the next phase of the script, but if it hasnt I want the script to keep trying to see if the trigger has been activated.

Code: [Select]

Scripting stuff up here
goto "detect"

#detect
nameoftrigger=true : goto "trigtrue"
nameoftrigger=false : goto "detect"

#trigtrue
Script continued down here

[Artak]

Code: [Select]

Scripting stuff up here
goto "detect"

#detect
?mycondition: goto "trigtrue"
~1
goto "detect"

#trigtrue
Script continued down here
in the triggers on activation line you would use mycondition = true

[max_killer_payne]

Thanks Artak!  ;D

[myke13021]

uhm...i always thought @ would make a script wait for a condition

scripting stuff here
goto "detect"

#detect
@myvariable

script continues here


tell me if i'm wrong

[Zombie]

the way I understand it, you are not wrong, but the way artak wrote it will lag less than the way you did, but your method will work also.  I have found loops will cause less lag then the @ does, not sure why tho

[myke13021]

ah...yes..thats it....thx for it

[macguba]

Loops do cause less lag than @ commands.   The reason is that loops only operate as often as you ask them to, say every 0.5s or whatever.   However @ commands are checked every frame.

If it's a small mission, it's not a big deal.  However, if you have  lot going on changing all your @ commands to slower loops can make a difference.

[Artak]

Indeed.