Variable Q's (basic)

[Burn]

Ok I'm going to start with something I read on another thread...
Is this true?:

You have to define the variables in init.sqs otherwise:  if OFP finds a variable that has not previously been defined it assumes that the whole expression is false.

My problem is that I hawe a trigger that sets a variable true:on activation: Alarm = true
and another trigger that has that variable in its condition field.
The first trigger activates fine but the other one won't...

If the abowe quote is true qould someone give me some pointers, on how to create a init.sqs file and predefining your variables in it... is it somewhat similar to creating a description.ext

All help is greatly appreciated!!!... Thanx in advance

[dmakatra]

Hmmm... this would shoot. Have you tried another word such as "TheAlarm=true"?
When I have trouble launching triggers I put in a titletext in the effect section in the trigger just to see if itÂ's the triggers on act field who is f00kin or if it is the triggers cond field, try that too!

[Sui]

Is that true?

Well... sort of.

All your variables have to be initialized (eg set to true, false, 0, 1 or whatever). However it doesn't have to be in the init.sqs

For your situation you could just put:

Alarm = false

in the init line of any unit. It will have the same effect as having it in the init.sqs would

[Burn]

@ The real Armstrong:

When I have trouble launching triggers I put in a titletext in the effect section in the trigger just to see if itÂ's the triggers on act field who is f00kin or if it is the triggers cond field, try that too!

I've allready tryed that but I'll try to change the name as you suggested...
thanx.

@ Sui

For your situation you could just put:

Alarm = false

in the init line of any unit. It will have the same effect as having it in the init.sqs would

Thanx alot Sui

Thanx alot for your replys guys

[Burn]

Oohh crap ... didn't seem to work, could the parameters of the triggers hawe anything to do with it ...
the first trigger activated fine... but the second for some reason din't.
Any ideas?

[Burn]

This is what I hawe in my mission:

TRIGGER#1[/b]

Axis a: 500
Axis b: 500
ellipse
Activation: Resistance
Repeatedly
Detected by east
Countdown: 0, 0, 0.
Type: none
Condition: this
On activation: alarm=true

TRIGGER#2

Axis a:0
Axis b:0
ellipse
Activation: None
Repeatedly
Detected by east
Countdown: 0, 0, 0.
Condition: alarm=true

I've tryed to change the variable name to v1, and I allso set the variable to false in a units init. field... both triggers where tested with various effects to see if they work... only the first trigger was activated. If you are out of suggestions, do you recall any mission that might use something similar... so I could unPBO it and check what I'm doing wrong here ... BTW I'm using version 1.90

Thanx in advance

[dmakatra]

Hmmm... WhatÂ'll happen if you change repeatedly to once on both triggas?

[Burn]

Yuppee ... I figured it out, u can't type alarm=true. the correct syntax is: alarm... so it would't activate the trigger because u only hawe to put the, variablename in the condition field. SO i skipped the: =true, in the second triggers condition field and BAM it worked ;D...

Thousands of thanx to you two for all the help ...I couldn't hawe done it without your advice

-----------------------------Bizon OUT :-X------------------------------------------------