What's the purpose of "Guarded by..." triggers?

[Fire-Fox]

I did some experiments with it but could not see a logic behind it yet. Could anyone who knows explain how to put a some use to this option?

Thanks!

[Burn]

If you give a unit a guard waypoint, the unit will guard those areas (patrol or sumthing :-\). That ofcourse only if you specified the right side for the unit...

[Fire-Fox]

If I put a "Guarded by" trigger somewhere and give a unit a guard waypoint the unit will just move to the waypoint, then move to the trigger and stay there. :/

[Burn]

I'm not shure, but in another thread someone said that the unit given the guardWaypoint will guard ( really ;D) the assigned triggerArea...
I don't know exactly how it works because I've never used it myself...
but try it and you'll see for yourself exactly how it works

[Hawkins]

I just had a quick test. For what I learned, the units wont patrol the trigger area. Would be cool if they did. Would be nice to combine some behaviour scripts with this to make the guards hunt down the intruders.

Hawkins

[max_killer_payne]

I think the guard WP makes them stay there and if they see or hear any action they go to the source of it.

[LCD]

da guard WP is da coolest WP in da game

dere was TUT bout using it around here somwere lots of taam ago

cant find it now - but u can read dis thread ;D

http://www.ofpec.com/yabbse/index.php?board=10;action=display;threadid=133;start=0

da guard triger just give da trigered area higher priority so da unit wil go dere b4 nywere else

LCD OUT

[Fire-Fox]

Thank you all, now I've also become interested in the guard WPs.  ;D LCD, thanks for the link, but it does not say much about using the guard WP, and I couldn't find any tutorial either. Could maybe somebody post a small tut here (what happens if I place the guard WP in range of a trigger, what if I synch it to something,etc....)? Think it would be great not only for me

But my question was about the TRIGGER TYPE (you know, where you select "None", "Switch", etc.). You can select "Guarded by West" for example in this field of a trigger description. Does anyone know what triggers of this type are good for and how to use them?


Thx!

[Chris Death]

Well, i'd suggest you to try it out by yourself FireFox.

Just place a few west present/guarded by east triggers
(let's say 5 triggers) - then create 10 eastern groups and
give 'em a guard waypoint (only a guard wp - nuffin more).

Then create two western groups, both waiting for you to radio
call 'em to go into the area (use two radio triggers, so you
will be able to let them go seperated).

Make yourself a resistance guy and add one loony to your
group, so you can use the commander's view.

Then give it a go and see what happens in what case  

No codes or scripting abilities required here, just the pure
click-clack-editor_stuff_action.

IMHO this is always the best way to figure things out, rather
than reading something what somebody has written in his
way of thinking.

~S~ CD

[Fire-Fox]

Think so too, Chris! But the experiments I had made totally confused me, thanks for your hint!

So far I figure that a "Guarded by ..." trigger marks a point that is vital for this side to defend. And if the guarding group is taken out, another guard-WP-group comes up to the point and tries to defend it.

I can think of nice fiddlings you can do with these triggers. For example, detect if the first guard group is dead or fleeing, then the corresponding "guarded by" trigger is setposed to another strongpoint, and the replacing guard group moves there to defend.

Thx everybody!


PS: Anyway, I leave this topic unsolved if you don't mind because anyone knows about tricks with the guard WPs please post them here, thx!  

[ACF]

The Prima guide said that groups at Guard WPs remain there until their SIDE has a contact (anywhere on the map is implied).  Supposedly, the AI then chooses one of the several 'guarding' groups (based on strength and proximity to the contact) and orders it to engage.  If it wins, the guarding group returns to its Guard WP.

The stated advantage of this is a bit of randomness in the AIs response - the alternative of triggering groups to move to a Destroy or Seek and Destroy WP when the enemy are detected is a bit linear.

As for the 'Guarded By' triggers, it suggested that they make guarding groups prioritise the trigger areas, but I don't think it said how.

Maybe that helps make a bit more sense of your experiments?

[revellion]

lets take a example

put 1 group or 2 with Guard WPs

then put 1 guy with Sentry WP on him

 if guy with Sentry WP see's enemy Contact it report and call the closest group or groups depending on how large the ENEMY CONTACT is

if its a large Enemy contact very much Guard WP groups are called

AIs without Sentry WP dont call Guard(s) WP AIs

i hope this clear things out

[Chris Death]

AIs without Sentry WP dont call Guard(s) WP AIs

hmm strange then that even AI's without waypoints do
call guard ones.

The sentry waypoint (i know the tutorial from red-hammer
said what you mean), is just like a move waypoint syncronized
with a side detected by side trigger (also possible by knowsabout).

The sentry waypoint is finished, once the unit/group has
detected enemies by themselves - after that, the unit/group
will procceed to it's next waypoint.

Anyway - what does this have to do with the guarded by triggers?

OK, here's an example of what you can do with the g/b triggers:

as i said above:

5 west present - guarded by east triggers

10 eastern groups

Now 5 of the 10 groups will start moving, each of them into
one of the 5 trigger's areas.

They will now stand there and do nuffin, unless west enters
the scene.

The 5 remaining groups, which didn't move to the trigger areas,
will join the scenery, wherever it is.

The 5 groups who have gone to the triggers, will just stay
in their trigger's area.

Now once one of the 5 trigger guarding groups gets eliminated,
their job will be taken over by one of the 5 remaining groups.

This means: the 5 guarded by triggers will always have an
eastern guard group in their area, as long as enough groups
are left to refill the trigger zones.
Remaining groups will do their usual guard job, and will reinforce empty trigger areas.

~S~ CD

[Tomb]

Heya, d00ds, just some short notes here on guard WP's and GuardedBy triggers.  


With the guard waypoint you you can set soldiers / groups in a support mode,
 so when some troops are attacked the groups in guard mode will come to support.

When the enemy is defeated & if the guards survive, these guards will return to the
guard WP and stay there. If another attack is coming in, they'll respond...


If you place "guarded by"  triggers the troops in the gaurd mode will come regulary to invest
 in the area that is in the "guarded by" trigger if there are enemy forces...

  Guarded by _x:  

This trigger is used with the GUARD waypoint and works as shown in the following example.
First, let's say you have 3 groups (West) that each have reached a GUARD waypoint.
As you've probably seen, that'll make them hang around a bit, and come to the rescue of other nearby units if needed
(after which they'll return to their GUARD location).  
Second, put down 2 triggers, and change their type to "Guarded by West". No other changes really needed.  
Now the interesting part; two of the groups will move to these triggers' locations, each group to its closest trigger,
to guard it (that is, any nearby friendlies under attack). The third group, the one farthest away from the two
"Guarded by"-triggers, will stay put.  
Let's say that one of the two groups at the "Guarded by"-triggers is killed. The two remaining groups will reorganize,
each moving to its closest "Guarded by"-trigger. That could even mean that a group will leave its current location at a
"Guarded by"-trigger to move to another "Guarded by"-trigger, it this group is closest to the second trigger than
any other group.  
As you see, "Guarded by"-triggers are a convenient way to set up terrain objectives for AI squads, without having to do
a lot of work. They can also be used to heavily randomize a mission.  
AFAIK, "Guarded by"-triggers will never go off, and only their type is important. Everything else seem to be ignored,
unfortunately including radius. Note that you can group a "Guarded by"-trigger with a unit, with expected results.

so!