Hello,

I've ran into a little problem.

Here is the situation

A town held by blufor is being attacked by opfor, once blufor detects opfor the alarm goes off in the town and once the opfor have been defeated by blufor the alarm turns off and everyone goes back to their positions.

Problem

I have a trigger that is set to activate on opfor, detected by blufor, this will turn on the alarm.

When the attackers (that blufor knows about) are defeated the alarm turns off.

Now when the 2nd opfor wave comes the alarm is not turned on because the trigger hasn't been reset, it goes off only once and that's it.

Solution ?

How to make the trigger reset when the attackers have been defeated ?

The enemy count will be random, also there is a enemy recon team near by the town.

Please help.

Thanks!

you could just create two triggers aand group the triggers to the leader of each wave.
When grouped you'll notice the trigger is now activated by VEHICLE i.e the unit grouped.
So that you have each trigger as vehicle, detected by blufor

also check out

http://www.armaholic.com/forums.php?m=posts&p=106632

I still can't get it to work. I made small demo mission showing what I need to happen.

http://www.mediafire.com/?7x7v6475fvcz4dg

In the demo mission you will see enemy rifleman attacking then another one attacking when the previous one is defeated.

I want the detection trigger to reset once the first attack has been defeated.

Please take a look, Thanks!

Have you set the trigger to repeatidly?
Have you tested to make sure the trigger is activated the second time, maybe it is triggered but maybe your alarm just does not sound for whatever reason? (add a hint to display when the trigger is activated)
Have you tried adding 2 triggers grouped to each different enemy unit which you want the blufor to "detect"?

Have you tried setting the knowsabout to 0? Maybe somehow they already know the other enemy unit is there.

I have tried all that without any luck

# Kenwort : I have tried all that without any luck

So, you mean that the trigger does not show a hint when activated? Or only the first time it activates and not the second time?
The trigger is set to repeatidly but still only activates once, meaning you only see the hint 1x? Or do you see the hint 2x but hear the alarm only in 1 case?

Please help us readers out and be specific in your answers than its easier to troubleshoot and think of other ways.


I am at work so I opened your mission.sqm in notepad and I saw you are using variables for the alarm (true/flase). The most logic thing to think is that the variable is not reset correctly. To troubleshoot you should show the state of the variable in the sidechat so you can see if its set to flase again when it needs to be false.

Note:
I am not writing this thinking you know nothing about mission editing, I know better!
Its just important to know what you did already to see where the error is and make sure the most logic things are tested and confirmed

You could just delete the trigger and create a new one.

http://community.bistudio.com/wiki/createTrigger

You could use create trigger but in this case he's also using a couple of switch triggers as well which are linked to the alarm variable, I think it's easier to just reduce some of the current triggers and variables.

None of the triggers were set to repeating so it would never have worked more than once anyway.
I also had a problem with the second assault where the group wouldn't continue on their patrol but it seems ok now.

Simple example
alarmtest2.utes_11978.7z

Thanks F2kSel! Just what I was trying to do! I don't know why I tried to make it so complicated when it turns out it can work with only 2 triggers :D

Thanks everyone for the help!

EDIT:

Hmm it looks like it only countdowns and then turns off the alarm, is there a way to make it turn off only when the attacking enemy has been defeated?

New example: http://www.mediafire.com/?8t6r04qqgzbcfc0

EDIT 2:

Thanks to mike I have it now working. Here is the example mission if anyone else needs it: http://www.mediafire.com/?dfdfplbhzr2m5vt

Solution was to add 2nd trigger condition: (count thisList) == 0

Meaning that when the attacker has been eliminated (that the defender knows about) the alarm goes off.

just one thing do it like this to stop it going off at the start off the mission.

alarmed and (count thisList) == 0

# F2kSel : just one thing do it like this to stop it going off at the start off the mission.

alarmed and (count thisList) == 0

Thanks for this addition! Thank you everyone for helping out!