Could the option "respawn enemy check" in Multispawn module include checking for enemies from the close vicinity when Respawn type: "Spawn in building" is used? Or should it already work like that? If it should then for some reason I'm able to spawn inside a building that has enemy close by.

I'd like to create a mission where if enemy captures a zone from the player team they won't be able to spawn in the building that happens to be in the now lost zone (because there's enemy in the close vicinity of the multispawn point).

Or might there be any other "simple" way to have a respawn disabled should enemy capture the zone where the respawn resides?

Hi Savage.

I was unable to test how it would behave when spawning on squad using Multispawn because I couldn't get the functionality itself to work correctly.

Following the ALiVE Wiki about Multispawn and its somewhat conflicting information (might be more about things left unmentioned) I went to test some combinations because to begin with I couldn't understand out of the Wiki page what combination would give the wanted behaviour:

1. (playable character NOT set as part of the AI group)
placing a marker with the name ALiVE_SUP_MULTISPAWN_RESPAWNGROUP_%GROUPID% and setting group ID with setGroupId for an AI squad and depending if Respawn type: "Spawn on squad" was used or not respawning throws the player character to spawn somewhere over the (in this case) Stratis ocean with or without a message "There are no units in your group 0 Alpha 1-2".

2. (playable character SET as part of the AI group)
placing a marker with the name ALiVE_SUP_MULTISPAWN_RESPAWNGROUP_%GROUPID% and setting group ID with setGroupId for an AI squad OR setting Respawn type: "Spawn on squad" WITHOUT a marker and without setting GroupId returned the same outcome:
the player apparently spawned in but the view got locked behind the character (3rd person) without any possibility to do anything. Respawning again only returned the same state.

I don't have the slightest idea if that was just me doing every single thing wrong or if the module is bugged because of the latest Arma version. I'm using Arma 1.56, CBA 2.2.0.151130 and ALiVE 1.0

@highhead Hi!

Theres no enemy check for building respawn, as some players want(ed) to do garrison towerdefend style missions. You can however just place the buildingspawn-marker elsewhere on any condition you want (f.e. enemies near players) and the unit will spawn there or will even fall back to the default method if there is no building at all (like f.e. [0,0,0]).

Plus, I will take a look at that groupID issue, may well be due to latest changes in A3, havent touched Group Multispawn module since some time! Thanks!

Hi!

highhead, could I ask you to kindly elaborate, I got lost between the lines of which I apologize.

or, I guess I understand that I could place the spawn in building marker anywhere and get what you suggest would happen but that doesn't give me what I was looking for: that the building spawn would be disabled when there's enemy nearby.

Could the ALiVE team consider adding the enemy near check also to other spawn types? (If players require to be able to create those tower defense styled missions maybe have an additional option to disable the enemy check for spawn in building type).

Why can't the world end the endless measurement struggle and we all agree to just Measure with bananas.

Well I'm from Texas, and everything's bigger in Texas. So My American banana > Your American banana ;)

Dear OP "ALiVE_SUP_MULTISPAWN_RESPAWNGRPUP_%BANANA%"

Banana for scale! Now the human race will set out to search for the most perfect banana in the universe that will set the standards to all measures in the future!

Back to the topic! :)

I found a nice way to "dynamically" disable/enable player respawns by SYNCing a trigger to BIS Respawn position (Modules -> Multiplayer -> Respawn position).

Using the code snippet
((count ([getposATL thisTrigger, 300, ["GUER","entity"]] call ALIVE_fnc_getNearProfiles)) == 0);
I first saw here Best way to "end mission" in large scale assault?, has proved to be very useful in many scenarios :)

Here's but one way to create multiplayer respawns that get disabled/enabled according to the enemy presence near a respawn:

create a trigger that is Repeatable and in the Condition field add the code snippet

((count ([getposATL thisTrigger, 300, ["GUER","entity"]] call ALIVE_fnc_getNearProfiles)) == 0);

• 300 is the radius or area where, if enemy is present, the respawn should be disabled
• change GUER to represent the enemy faction (eg. EAST, GUER, NATO) or anything that is supposed to represent an entity that should enable/disable the player respawn
• use == 0 for call ALIVE_fnc_getNearProfiles (in short: when eg. GUER profiles is 0 inside the trigger area respawn will be available, when GUER profiles is more than 0 respawn will be disabled)

Then place one BIS Respawn position as close as possible the trigger you just created and sync it to the trigger and you're done!

This method has so far worked flawlessly for disabling player respawns when there's enemy profiles (virtualized or spawned) inside the trigger area. Naturally when there's no more enemy profiles inside the trigger area the player respawn will once again become available.