Subscribe to download
MGI ADVANCED MODULES

1. And in this way, you can create similar cycles for other teams.
2. In each Spawn Group modules remember to choose the team side, and in the Condition field, you need to write custom names for teams:
chosenGroup_BLUFOR \ OPFOR (or custom) == N
3. Now yo need to write code in the same Game Logic object (logical element)
// For BLUFOR\Team1
[] spawn {
while {true} do {
chosenGroup_BLUFOR = floor (random 3); // 0,1,2 for BLUFOR\Team1
publicVariable "chosenGroup_BLUFOR";
sleep 30;
};
};

// For OPFOR\Team2 — another side
[] spawn {
while {true} do {
chosenGroup_OPFOR = floor (random 3); // 0,1,2 for OPFOR\Team2
publicVariable "chosenGroup_OPFOR";
sleep 30;
};
};
4. Now it's done.

@PierreMGI
Thanks for the reply, it made me want to tinker with this thing.
I think I managed to create a completely random spawn with this mod.
1. I created 3 custom groups and 3 Spawn Group modules for each of them - choose spawn time 30 seconds.
2. In each module, in the Condition field, I wrote:
For the first: chosenGroup == 0
For the second: chosenGroup == 1
For the third: chosenGroup == 2
3. I created a Game Logic object (logical element) (you can also use a trigger, but I didn't do that) and in the init of this object I wrote:
[] spawn {
while {true} do {
chosenGroup = floor (random 3); // random number 0, 1 or 2
publicVariable “chosenGroup”; // if in MP
sleep 30; // cycle every 30 seconds
};
};
4. This method truly spawns randomly. Even more so, at the beginning it spawns only one of the three groups, not all 3 at once, which is very good. Then it spawns them randomly, groups can even repeat, and that's good.

@Armist
Understood. At this time, I can't say when you could work on Arma for that. anyway, you could try to place 3 modules and add a common condition with exclusive effect for spawnng on one module but not the two others. For example, use arma variable time or diag_ticktime with a modulo (mod function) which can trigger a different time for the three modules. I hope this is clear: an extra condition for each module (your usual condition + mine), repeatable (modulo, this way condition is on/off with time), exclusive (not the same cond: ex: (time ... + 1... +2) mod 3)

Hello, I need some help.
I have 3 custom groups (with customized gear, vehicles, etc.).
The task is to create a cyclic spawn of a random group chosen only from these three custom groups (for my infinite battle).
I connected all three groups to the Spawn Group module at the same time, but each time only one specific group kept spawning (only a tank, or only a BMP\IFV, etc.), meaning that no random switching between the groups occurred in the spawn cycle.
I don’t plan to use individual Spawn Group modules for each group, since I want to reduce system load and combat intensity, and also to introduce randomness — but with custom units and vehicles.
How can this be created using this mod?

P.S. The Spawn Group module is amazing, and I use it constantly. I’m very thankful for its creation. Overall, this mod is the best thing that could happen to Arma 3.

Please, when you refer to a module, take time to mention the exact name of it.
About "AIs can respawn" module:
I created this module for respawning non-playable AIs (playable ones are set by editor). The former intention was to allow enemy/friendly waves, infantry not in vehicles (because this case is supposed to be treated by the "Respawn vehicles" module.
So, respawning multiple AIs can be resource demanding. I focused on type /side /loadout, which is not so bad.

One asked me for carrying over name /voice /face... This is the case but for a reason I don't know, that takes several seconds... If a unit is re-killed at once, that could affect the next respawn (perhaps).
The name is the same as in editor (the full name), and not to be confused with the variable name of the unit (nor carried over). The pitch of the voice is neither carried over. The insignia is not carried over.
Scripted traits are not treated (as any other scripted behavior). But I'm rather sure that native traits (like medic or engineer) are carried over by types of dead/respawning AIs.
Everything is possible but I had to make some choices. That's a balance between general purpose and demanding specific features.
Furthermore, it seems to me Bohemia forums are dead. Arma 3 is no more maintained by devs, Reforger is not my taste. In other words, I spend less time on Arma.

Hey pierreMGI in no way is this a criticism I think you're a talented scripter and we are lucky to have you in this community. This is just an observation and a wish list.

MGI AI module

Triggers will only carry over one time after the initial spawning any trigger connected to the group or units are lost I believe because individual variable names do not carry over like in JEBUS.

Traits assigned like medic engineer ect will only carry over on the first use after they initial respwans they lose the ability that was a sign to them.

Voice changes will carry over for all respawns.
Faces changed will carry over for all respawns.
Any information but into a unit init will be lost after the first respawn for example forcing a specific ammunition to be used in a weapon ect.
Sincerely Avibird

Spawn groups attack module allows code on groups, full customized groups, and ways for spawning conditions. Advanced patrols module is more a quick and dirty way for spawning enemies when mission makers have no skill about coding. I don't have time for rebuilding or even modifying these modules. Anyway, thanks for your suggestions. I keep note for that.

Continue....

I don't know if you're done modifying this but if you ever do can you look into those functions. As of now I need to use both to get the mission design that I desire. Avibird. The other possible modification would be to different AI module to spawn different sides at different intervals. Right now whatever the module set for will affect all four sides. This is not a criticism love your scripts and mods just a wish list Avibird

Hello pierreMGI I know you have stated multiple times there's a difference methods for spawning AI. My method of choice of spawning AI groups is using JEBUS and your AI spawn module
JEBUS has a few really cool features that yours does not and vice versa.

JEBUS allows unit group spawn if a opposing unit is at a certain distance from the initial spawn site the group will not spawn. The other feature is
Unit individual variable names carry over as well as unit init box codes carryover. For example I'm able to use codes like dostop and disabled pathway. These codes only work on the initial setup of MGI after respawn the codes do not carry over.