Need help making a unit hold until target is destroyed.

[Forest Rat]

So I've got a FAC humvee driving through town.

 

I want him to stop at a target, and hold there until the target is destroyed.

 

Sounds simple, and I'm sure it is simple, but for the life of me I can't figure it out.

 

I read through the GUI manual, and searched. There's just something about this editor that I'm having a hard time grasping. Thanks all. :pilotfly:

[Bahger]

The "Unit Dead" or "Group Dead" conditions are probably the ones to use here. These have to be user-placed objects recognised by the ME as being Red or Blue.

[Druid_]

First click on the waypoint at which you would like the group/unit to hold at. Then in the advanced tab select PERFORM TASK then HOLD.

 

You now have 2 options.

1) In the STOP condition (of PERFORM TASK-HOLD) tick IS USER and select a flag number (e.g. 1 this means he will Stop Holding when flag 1 is true) then in your triggers list add

ONCE , GROUP DEAD targetgroupname SET FLAG 1 .

 

OR

 

2) In your Triggers List Add ONCE , GROUP DEAD targetgroupname, RESUME humveegroupname

 

Option 2 is obviously the easiest but you option 1 is more flexible if you want to add other conditions or you if you have several groups holding on the target destroyed condition.

Edited June 4, 2011 by Druid_

[Forest Rat]

Druid> Worked like a charm. Thanks! Rep+

[Forest Rat]

Well, I've got a new problem now.

While he holds he stops functioning as a FAC and won't give me any targets until the "hold" is released.

 

Anyone know a workaround?

[Bahger]

Are you sure he has LOS to the target from his stationary position?

[Forest Rat]

Yes, he does.

I've confirmed this by making the same waypoint that he holds at the final waypoint ... so naturally, he stops without the hold command reports Type-2 in effect as opposed to no tasking available.

[nomdeplume]

How are you setting the FAC task? I think you'd need to use an enroute task, and make sure it's started prior to the unit reaching the hold point. Any 'Perform Task' task will stop processing of further tasks for that waypoint until it is completed (or stopped due to a 'stop condition'). Enroute tasks are done in the background, so to speak, and once started the logic immediately moves to the next task for that waypoint.

[Druid_]

Nomdeplume is correct but just in case it doesn't work, there is another workaround but involves a small amount of lua & utilising what I consider to be a bug in 1.1.0.7. I havent tried this in 0.8 so can't guarantee it will work. It utilises AI OFF on the FAC. In 0.7. he stops moving but continues to act as a FAC.

 

At the hold waypoint, take out HOLD and instead add RUN SCRIPT. In the script box add the following code

trigger.setUserFlag(999,true)

In your triggers add ONCE description, FLAG 999 SET, AI OFF FacGroupName

 

When you want him to start moving again then AI ON FacGroupName.

 

Try it out & let me know, it worked in 1.1.0.7 & I'll be surprised if they changed it.

 

EDIT: Just a thought but if you have 'FAC engage group' at that waypoint is it before or after the HOLD command?

Edited June 6, 2011 by Druid_

[Forest Rat]

I've tried every possible configuration and this is the only one that worked for me...

 

At my "holding" waypoint I have:

1. Run Script (trigger.setUserFlag(999,true))

2. FAC - Assign Group ("T-55")

 

It wouldn't work with the script unless I put the FAC task after the script. Odd. :)

 

On a side note, even when I set the FAC - Engage Group as an en-route task he still stopped all FAC function during a "hold".

 

Thanks again.