Name a Group

[lightspeed_aust 681]

In the editor you can create groups quickly, however, you can't name these groups.

How would i name the group, Group_a so that I could then later delete this group?

cheers.

[W0lle 1049]

Of course you can name these groups in the editor, where else?

In init line of groupleader:

Group_a=group this

[lightspeed_aust 681]

lol thanx Wolle - they're not paying you enuff ;)

[mikey74 169]

Wolle/anybody lol is there any way to use the group name in a script and it be recognized? Basically I have two groups that if they are killed Im going to offer reinforcments for each group thats killed.

in the init field I did Grp1 = group this; and then tried the above, but doesnt seem to work.

Example in the editor Ive named two groups: Grp1 and Grp2 Ive placed a trigger with anybody notpresent that calls a script and here is my code:

hint format ["testing now"];

sleep 3;

waitUntil
{
{alive _X && !(fleeing _X)} count "Grp1" == 0 or {alive _X && !(fleeing _X)} count "Grp2" == 0;

};

hint format ["should have infantry support"];

helo = True

publicVariable "helo";

exit;

Yes The public Varible works with my other scripts ;) Dont think thats my issue. :D

thanx :)

Edited August 12, 2010 by Mikey74

[Benny. 15]

Try:

hint format ["testing now"];

sleep 3;

waitUntil
{
({alive _X && !(fleeing _X)} count (units Grp1) == 0) or ({alive _X && !(fleeing _X)} count (units Grp2) == 0);

};
hint format ["should have infantry support"];
helo = True
publicVariable "helo";

Btw, if that's SQF, you don't need to use 'exit'.

[mikey74 169]

ahh thanks was wondering about the exit thing. :)

It had the same results. Maybe its how Im calling the script?

Thanks for your reply. :)

I know I can make it work by writing a script to spawn them in. Just seems like I should be able to do this without doing that.

Edited August 12, 2010 by Mikey74
An Idea :(

[Benny. 15]

Little typo in the script, there's a missing ";" near helo = True

Also try without a trigger.

Quick Checkup aswell:

- A member of the group #1 has a Grp1 = group this in it's init field

- A member of the group #2 has a Grp2 = group this in it's initfield.

- create a file init.sqf in your mission root and call your script from there, like ExecVM "myscript.sqf"

hint format ["testing now"];
sleep 3;

waitUntil {
({alive _X && !(fleeing _X)} count (units Grp1) == 0) or ({alive _X && !(fleeing _X)} count (units Grp2) == 0);
};
hint format ["should have infantry support"];
helo = True;
publicVariable "helo";

Edited August 12, 2010 by Benny.

[mikey74 169]

ha haaaa that worked great!!!! Thanks!!!!

Edited August 12, 2010 by Mikey74
re read and figured it out ;) ie typo

[Taysiir 10]

how do I actually verify an entire group is dead?

Here's my situation:

The PC will attack a group of enemy (3 men, group name RU1). So for each men, I have the line ... RU1 = group this; ... in their init.

My trigger is set to condition ... !alive RU1;

And it's getting activated whenever a single of those souls are dying.

And yes, I'm a complete noob in scripting (just started today ... )

[kylania 568]

{alive _x} count units RU1 == 0

[Taysiir 10]

{alive _x} count units RU1 == 0

Thanks mate, that helped a lot. Been on that for the past hours. I just noticed though, it takes forever for the trigger to process that condition.

A good minute passed before it did the "On Activation" section. Any idea what's happening here?

[kylania 568]

It takes a while for a group to realize it's units are gone.

If you wanted it to be faster, then do something like this:

!alive ru1_unit1 && !alive ru1_unit2 && !alive ru1_unit3

and so on, with a !alive unit for each specific unit you wanted to check for. Where ru1_unit1 is the Name given to a unit in the Editor.

[Taysiir 10]

It takes a while for a group to realize it's units are gone.

If you wanted it to be faster, then do something like this:

!alive ru1_unit1 && !alive ru1_unit2 && !alive ru1_unit3

and so on, with a !alive unit for each specific unit you wanted to check for.

If that's the only alternative, I guess I'll just stick with the previous code you gave me.

Thank you again for the information.

[shuko 59]

It takes a while for a group to realize it's units are gone.

That is true. However, when you add {alive _x} or {!alive _x} check it will bypass the group member status update, because it directly checks for the members status. Using the condition the group units is used just as an array.

In other words, {alive _x} checks if the unit is alive, not if his group leader thinks he's alive. :)

[kylania 568]

Wonder why it was delayed for him in that case? Odd.