{"name":"Arma 3: MP End Game","title":"Arma 3: MP End Game","type":"topic","url":"https://community.bistudio.com/wiki/Arma_3:_MP_End_Game","revid":364250,"updated":"2024-05-06T09:38:19Z","aliases":["Arma 3 MP End Game","MP End Game"],"markdown":"Arma 3 v1.42\n\n## End Game - Scenario Guideline\n\n> [!NOTE]\n> Here you can find information on how to create your own **[End Game](http://dev.arma3.com/post/oprep-end-game)** scenarios.\n> Be introduced to the individual system components, how they work together, and finally learn how to set up the **End Game** scenario.\n\n> [!IMPORTANT]\n> The current issues and limitations are:\n>\n> - **West vs East vs Resistance**\n>   - Currently, the only supported playable sides are *west* (BLUFOR) and *east* (OPFOR), and the common enemy is *resistance* (Independent)*,* which is AI controlled.\n>   - The plan is to re-factor the related code to support all kinds of side combinations.\n\nA sample is available in Arma 3 Tools.\n\n### How to access modules and logics\n\n#### Modules\n\nWhen inside the Editor, navigate to **Modules (F7)** and double click on the map. The modules selection window will appear.\nSet the *Category* to **Objectives,** and here you can see all **End Game Modules** listed.\n\n#### Logics\n\nWhen inside the Editor, navigate to **Units (F1)** and double click on the map. The unit selection window will appear.\nSet the *side* to **Game Logic** (note this is only possible after placing a player unit) and the *class* to **Objects**. Here you will find **End Game** specific **Game Logics.**\n\n### Objectives Instance\n\n#### Objectives Instance\n\nThe **End Game Objectives Instance** is what controls the flow of the whole End Game scenario. It decides when and which objectives should be visible and handles changes in their state.\n\nThe **Objectives Instance** is also responsible for the stage progression / selection, and only one instance may be placed per scenario, otherwise an error will be triggered.\n\n### Objective Types\n\n#### Start Game Objective\n\nThe *Start Game Objective* handles the initial phase of the **End Game** by requiring players to **Establish FOB**.\nThe succeed radius tells the objective the distance from its location that no enemy is within, so the objective can succeed. So, when attacking the enemy location to establish the FOB, players are required to eliminate all the enemies within the given radius.\n\n#### Middle Game Objective\n\nThe *Middle Game Objective* is part of the second phase of **End Game** and requires players to move to a location and download Intel from an electronic device.\n\n#### End Game Objective\n\nThe *End Game Objective* handles the last phase of **End Game** by requiring players to pick up important schematics from a location and upload them to their HQ.\nThe team which is able to complete the upload will win the match.\n\n### Game Logic Types\n\n#### Objective Randomizer\n\nThe **Randomizer Game Logic** allows for objective randomization. If two or more objectives are synced to a **Randomizer** that in turn is synced with the **End Game Objectives Instance** module, one of those objectives will be selected at random on mission start.\n\nThe objectives that are not selected, are cleared and all related objects are deleted.\n\nIn the example on the right, both **Objective 1** and **Objective 2** have a **50%** chance to be selected. The one which is not selected at mission start, will be **deleted** along with its related objects.\n\n### Scenario Configuration\n\n#### Intel\n\nWhen inside the **Editor**, enter the **Intel** properties. Here you are able to set mission parameters such as the mission **Name**, mission **Description**, the initial **Time of Day** and **Weather**.\n\nAdd a mission **name** and **description**. Also, make sure **Independent** is friendly to **Nobody**. This will make the Independent side the common enemy for players.\n\n#### Revive and Respawn\n\n**End Game** was made with group respawn in mind, and although you are free to try different respawn types, the following configuration is the suggested one. You will need to add a few lines to your **description.ext**.\n\n**Description.ext**\n\n```\nrespawn = 3;\nrespawnDelay = 30;\nrespawnVehicleDelay = 0;\nrespawnTemplates[] = {\"Revive\", \"MenuPosition\"}; // Enable Revive and Respawn Menu\nrespawnOnStart = -1;\nrespawnDialog = 1;\ndisabledAI = 1;\n```\n\n#### Shared Objectives\n\nTo enable the **Shared Objectives** you'll need to add a few lines to your **description.ext**.\n\n**Description.ext**\n\n```cpp\nclass CfgTaskEnhancements\n{\n    enable        = 1;        // 0: disable new task features (default), 1: enable new task features & add new task markers and task widgets into the map\n    3d            = 1;        // 0: do not use new 3D markers (default), 1: replace task waypoints with new 3D markers\n    3dDrawDist    = 10000;    // 3D marker draw distance (default: 2000)\n    share        = 1;        // 0: do not count assigned players (default), 1: count how many players have the task assigned\n    propagate    = 1;        // 0: do not propagate (default), 1: propagate shared tasks to subordinates\n};\n```\n\n#### Garbage Manager\n\nIn order to keep the game from slowing down because of dozens of destroyed vehicles and hundreds of bodies, you may enable and configure the **Garbage Manager** within your **description.ext**.\n\n**Description.ext**\n\n```\ncorpseManagerMode = 1; //Type of removed bodies: 0 - none, 1 - all, 2 - only respawnable, 3 - only non-respawnable\ncorpseLimit = 10; //Max number of bodies which can be available at the same time. When exceeded, start deleting immediately.\ncorpseRemovalMinTime = 120; //Minimal time in seconds a body stays in the scene (can't be removed sooner).\ncorpseRemovalMaxTime = 240; //Maximal time in seconds after which a dead body is removed (can't stay longer)\n\nwreckManagerMode = 1; //Type of removed wrecks: 0 - none, 1 - all, 2 - only respawnable, 3 - only non-respawnable\nwreckLimit = 5; //Max number of wrecks which can be available at the same time. When exceeded, start deleting immediately.\nwreckRemovalMinTime = 120; //Minimal time in seconds a wreck stays in the scene (can't be removed sooner).\nwreckRemovalMaxTime = 240; //Maximal time in seconds after which a wreck is removed (can't stay longer)\n```\n\n#### Header and Missions Parameters\n\nTo wrap up the description.ext configuration, you may set a few parameters such as scenario author, how many players the scenario supports, and even what parameters will be available in the lobby.\n\n**Description.ext**\n\n```\nauthor = \"Author\";\nonLoadName = \"On Load Name\";\nbriefingName = \"Briefing Name\";\nonLoadMission = \"On Load Mission\";\noverviewText = \"Overview Text\";\noverviewPicture = \"\\a3\\Missions_F_MP_Mark\\Data\\Marksmen_scenario01_overview_CA.paa\";\nclass Header\n{\n    gameType = CTF;\n    minPlayers = 1;\n    maxPlayers = 16;\n};\nclass Params\n{\n    #define DAYTIMEHOUR_DEFAULT 12\n    #define WEATHER_DEFAULT  25\n    #define DEBUGCONSOLE_DEFAULT   0\n\n    #define TIMEACCELERATION_DEFAULT  10\n    #include \"\\a3\\functions_f\\Params\\paramDaytimeHour.hpp\"\n    #include \"\\a3\\functions_f\\Params\\paramWeather.hpp\"\n    #include \"\\a3\\functions_f\\Params\\paramDebugConsole.hpp\"\n\n    #include \"\\a3\\Functions_F_MP_Mark\\Params\\paramTimeAcceleration.hpp\"\n};\n```\n\nPlease note that Param templates currently don't work with PBO missions manually copied to MPMissions folder.\nUnpacked missions, Steam missions and missions which are part of an addon work correctly.\nSee Mission Parameters for more info.\n\n### Scenario Setup\n\n#### Placing Player Slots\n\nPlace your playable units for both **BLUFOR** and **OPFOR**. Again, please note the current limitations, only BLUFOR and OPFOR can be player-controlled.\n\n#### Respawn Markers\n\nPlace a **Marker** at the players' initial position that will assign the initial respawn position.\nThen make sure to call it **respawn_west** and **respawn_east** depending whether for **WEST** (BLUFOR) or **EAST** (OPFOR).\n\n#### Headquarters Entity\n\nThe **Headquarters Entity** serves as the speaker for the side.\nThis entity is the HQ which gives players hints on how or what they have to do during the mission.\nMake sure to place a **Headquarters Entity** by selecting **Modules (F7)** and navigating to the **Intel** category.\nAlso, **make sure to name this module**. Its name will be used later so we can reference this entity.\nFor the *west* entity name it **BIS_west_speaker** and for the *east* entity name it **BIS_east_speaker**. Make sure to set the correct side of the HQ entity within the module.\n\n#### Objectives Instance\n\nSelect **Modules (F7)** and navigate to the **Objectives** category. Place the **End Game Objectives Instance** module.\nThis will tell the game to initialize the End Game systems on mission start.\nThe module has one property, the **End Game Threshold**, which tells the system how many Intel packages a side must download for the last phase to start, during the middle game stage, or **Stage 2**.\n\n**End Game Threshold** - The amount of retrieve intel tasks a side must complete in order to succeed the 2nd stage and move to the 3th and final stage.\n**Warmup Delay** - The amount of time in seconds players are locked in the warmup phase at the start of the scenario.\n\n#### Start Game Objectives\n\nSo now, let's place our our first objectives. These will be the **Start Game Objective**, and each playable side must have their own unique one.\nSo select **Modules (F7)** and double click on the map. After the modules selection window appears, navigate to the **Objectives** category and, for each side, place a **EndGame Start Game Objective** where you want the side to Establish their FOB.\nWithin the module itself, you **must** set the side which will be tasked with this objective.\nEvery Start Game Objective modules must be synchronized with the Objectives Instance module.\n\n> [!NOTE]\n> Do not forget to add at least one for each of the playable sides.\n\n- **Attacking Side** - The side which will be tasked to this objective\n- **Succeed Radius** - The radius in which at least one player of the side doing this objective must be and the radius in which no enemy units can be\n- **Restriction Radius** - The radius in which players are confined until they complete this objective\n\n#### Middle Game Objective\n\nA **Middle Game Objective (MGO)** is what could be called a **Retrieve Intel** objective.\nThese are the objectives which require players to move to their location and *download some intel* from the object connected to the *objective module*.\n\nTo place a Middle Game Objective select **Modules (F7)** and double click on the map. Once the modules window appears, navigate to the **Objectives** category and select the **EndGame Simple Objective**.\nEach **MGO** requires an object which is used to download Intel from, for example a car, UAV or a computer.\nGo ahead and place any object you would like, then name it, for example, *BIS_downloadPoint_1* and put this exact name in the module's **\"Downloadable Object\"** field.\nEvery Middle Game Objective modules must be synchronized with the Objectives Instance module.\n\nAny **triggers** connected to the module defines the mission objects' relation with the connected objective.\nFor example, if you have a trigger connected to the module, any mission objects inside it will be set as **owned by the objective** and will be hidden / deleted when the object is.\n\n**Note that the object to be downloaded from will be indestructible until one of the competing sides downloads intel from it.**\nIt is also good practice to lock vehicles (if used as download object) so players can't board and drive it away.\n\n- **Downloadable Object** - The name of the object to use as download source\n- **Download Radius** - The radius in which download will be available (Non-Functional)\n- **Task Description** - The description of this objective, for example, \"Download intel from UAV\"\n- **Instant Download** - Whether the download should be instant, if so, download is succeeded after interaction with object\n\n#### Randomizer Logic\n\n**Randomizer** logics can be used to randomize **Middle Game Objectives**, so if more then one objective is connected to a randomizer, one at random will be selected at **mission start**.\nThe objectives not selected **will be deleted**, along with their **owned objects**.\n\n#### End Game Objective\n\nThe **End Game Objective** is the objective which handles the last phase of the game mode. It defines the possible **pickup / upload** locations and how long the match can take when in the last phase.\n\nSo start by selecting **Modules (F7)**, navigate to the **Objectives** category and place a **EndGame End Game Objective**.\nAfter placing our module, let's place one **Pickup** and at least two **Upload** objects.\nA pickup object is the object that is referred to as **Schematics**, and it is the object players need to pick up and use to upload the data.\nThe upload objects are the objects used to upload the **Schematics** to HQ.\nEvery End Game Objective modules must be synchronized with the Objectives Instance module.\n\n> [!NOTE]\n> One Pickup object and at least two upload objects are needed, if more are provided, these will be randomized.\n\n- **Time Limit** - The time limit for the 3th phase, if time limit is reached before one of the sides winning, the mission will end as a draw\n- **Pickup Objects** - List of all available pickup objects\n- **Upload Objects** - List of all upload objects (At least 2 are required, one per side or more)\n- **Note that the objects used as Schematics will be indestructible.**\n\n#### Resulting Layout\n\nYou should get something similar to the picture on the right.\n\n#### Respawn Points\n\nYou can add positions which are turned into respawn points after an event. For example, a player of a side entering an objective area will unlock any respawn points available for that objective.\nThe system handles 3 kinds of respawn points:\n\n- **Respawn Point logic** connected to the **Start Game Objective**\n  - It is unlocked when the owner side establishes their FOB.\n- **BLUFOR / OPFOR game logics** connected to a **Simple Objective**\n  - These are unlocked when a player of a side enters an objective area.\n- **Respawn Point logic** connected to an Upload object which is used by the **End Game Objective**\n  - It is unlocked when the last phase starts and serves as a position for the upload defenders to respawn at.\n\nWhere to find the logics?\n\n- **BLUFOR / OPFOR game logics** can be found under **Units (F1) > Game Logics > Sides**.\n- **Respawn Point logics** can be found under **Units (F1) > Game Logics > Positions**.\n\n#### Vehicle Respawn Modules\n\nFor any placed vehicles in the scenario, you may add a respawn module synchronized to them, making them respawn after being destroyed, damaged and/or abandoned.\nSuch module can be found under **Modules (F7) > Multiplayer > Vehicle Respawn**.\n\n#### Final Notes\n\n> [!IMPORTANT]\n> If one of the competing sides has no players at the moment when the third and last phase starts, the match will end with the side with players being the winner.","sections":[{"heading":null,"level":1,"markdown":"Arma 3 v1.42"},{"heading":"End Game - Scenario Guideline","level":2,"markdown":"> [!NOTE]\n> Here you can find information on how to create your own **[End Game](http://dev.arma3.com/post/oprep-end-game)** scenarios.\n> Be introduced to the individual system components, how they work together, and finally learn how to set up the **End Game** scenario.\n\n> [!IMPORTANT]\n> The current issues and limitations are:\n>\n> - **West vs East vs Resistance**\n>   - Currently, the only supported playable sides are *west* (BLUFOR) and *east* (OPFOR), and the common enemy is *resistance* (Independent)*,* which is AI controlled.\n>   - The plan is to re-factor the related code to support all kinds of side combinations.\n\nA sample is available in Arma 3 Tools."},{"heading":"How to access modules and logics","level":3,"markdown":""},{"heading":"Modules","level":4,"markdown":"When inside the Editor, navigate to **Modules (F7)** and double click on the map. The modules selection window will appear.\nSet the *Category* to **Objectives,** and here you can see all **End Game Modules** listed."},{"heading":"Logics","level":4,"markdown":"When inside the Editor, navigate to **Units (F1)** and double click on the map. The unit selection window will appear.\nSet the *side* to **Game Logic** (note this is only possible after placing a player unit) and the *class* to **Objects**. Here you will find **End Game** specific **Game Logics.**"},{"heading":"Objectives Instance","level":3,"markdown":""},{"heading":"Objectives Instance","level":4,"markdown":"The **End Game Objectives Instance** is what controls the flow of the whole End Game scenario. It decides when and which objectives should be visible and handles changes in their state.\n\nThe **Objectives Instance** is also responsible for the stage progression / selection, and only one instance may be placed per scenario, otherwise an error will be triggered."},{"heading":"Objective Types","level":3,"markdown":""},{"heading":"Start Game Objective","level":4,"markdown":"The *Start Game Objective* handles the initial phase of the **End Game** by requiring players to **Establish FOB**.\nThe succeed radius tells the objective the distance from its location that no enemy is within, so the objective can succeed. So, when attacking the enemy location to establish the FOB, players are required to eliminate all the enemies within the given radius."},{"heading":"Middle Game Objective","level":4,"markdown":"The *Middle Game Objective* is part of the second phase of **End Game** and requires players to move to a location and download Intel from an electronic device."},{"heading":"End Game Objective","level":4,"markdown":"The *End Game Objective* handles the last phase of **End Game** by requiring players to pick up important schematics from a location and upload them to their HQ.\nThe team which is able to complete the upload will win the match."},{"heading":"Game Logic Types","level":3,"markdown":""},{"heading":"Objective Randomizer","level":4,"markdown":"The **Randomizer Game Logic** allows for objective randomization. If two or more objectives are synced to a **Randomizer** that in turn is synced with the **End Game Objectives Instance** module, one of those objectives will be selected at random on mission start.\n\nThe objectives that are not selected, are cleared and all related objects are deleted.\n\nIn the example on the right, both **Objective 1** and **Objective 2** have a **50%** chance to be selected. The one which is not selected at mission start, will be **deleted** along with its related objects."},{"heading":"Scenario Configuration","level":3,"markdown":""},{"heading":"Intel","level":4,"markdown":"When inside the **Editor**, enter the **Intel** properties. Here you are able to set mission parameters such as the mission **Name**, mission **Description**, the initial **Time of Day** and **Weather**.\n\nAdd a mission **name** and **description**. Also, make sure **Independent** is friendly to **Nobody**. This will make the Independent side the common enemy for players."},{"heading":"Revive and Respawn","level":4,"markdown":"**End Game** was made with group respawn in mind, and although you are free to try different respawn types, the following configuration is the suggested one. You will need to add a few lines to your **description.ext**.\n\n**Description.ext**\n\n```\nrespawn = 3;\nrespawnDelay = 30;\nrespawnVehicleDelay = 0;\nrespawnTemplates[] = {\"Revive\", \"MenuPosition\"}; // Enable Revive and Respawn Menu\nrespawnOnStart = -1;\nrespawnDialog = 1;\ndisabledAI = 1;\n```"},{"heading":"Shared Objectives","level":4,"markdown":"To enable the **Shared Objectives** you'll need to add a few lines to your **description.ext**.\n\n**Description.ext**\n\n```cpp\nclass CfgTaskEnhancements\n{\n    enable        = 1;        // 0: disable new task features (default), 1: enable new task features & add new task markers and task widgets into the map\n    3d            = 1;        // 0: do not use new 3D markers (default), 1: replace task waypoints with new 3D markers\n    3dDrawDist    = 10000;    // 3D marker draw distance (default: 2000)\n    share        = 1;        // 0: do not count assigned players (default), 1: count how many players have the task assigned\n    propagate    = 1;        // 0: do not propagate (default), 1: propagate shared tasks to subordinates\n};\n```"},{"heading":"Garbage Manager","level":4,"markdown":"In order to keep the game from slowing down because of dozens of destroyed vehicles and hundreds of bodies, you may enable and configure the **Garbage Manager** within your **description.ext**.\n\n**Description.ext**\n\n```\ncorpseManagerMode = 1; //Type of removed bodies: 0 - none, 1 - all, 2 - only respawnable, 3 - only non-respawnable\ncorpseLimit = 10; //Max number of bodies which can be available at the same time. When exceeded, start deleting immediately.\ncorpseRemovalMinTime = 120; //Minimal time in seconds a body stays in the scene (can't be removed sooner).\ncorpseRemovalMaxTime = 240; //Maximal time in seconds after which a dead body is removed (can't stay longer)\n\nwreckManagerMode = 1; //Type of removed wrecks: 0 - none, 1 - all, 2 - only respawnable, 3 - only non-respawnable\nwreckLimit = 5; //Max number of wrecks which can be available at the same time. When exceeded, start deleting immediately.\nwreckRemovalMinTime = 120; //Minimal time in seconds a wreck stays in the scene (can't be removed sooner).\nwreckRemovalMaxTime = 240; //Maximal time in seconds after which a wreck is removed (can't stay longer)\n```"},{"heading":"Header and Missions Parameters","level":4,"markdown":"To wrap up the description.ext configuration, you may set a few parameters such as scenario author, how many players the scenario supports, and even what parameters will be available in the lobby.\n\n**Description.ext**\n\n```\nauthor = \"Author\";\nonLoadName = \"On Load Name\";\nbriefingName = \"Briefing Name\";\nonLoadMission = \"On Load Mission\";\noverviewText = \"Overview Text\";\noverviewPicture = \"\\a3\\Missions_F_MP_Mark\\Data\\Marksmen_scenario01_overview_CA.paa\";\nclass Header\n{\n    gameType = CTF;\n    minPlayers = 1;\n    maxPlayers = 16;\n};\nclass Params\n{\n    #define DAYTIMEHOUR_DEFAULT 12\n    #define WEATHER_DEFAULT  25\n    #define DEBUGCONSOLE_DEFAULT   0\n\n    #define TIMEACCELERATION_DEFAULT  10\n    #include \"\\a3\\functions_f\\Params\\paramDaytimeHour.hpp\"\n    #include \"\\a3\\functions_f\\Params\\paramWeather.hpp\"\n    #include \"\\a3\\functions_f\\Params\\paramDebugConsole.hpp\"\n\n    #include \"\\a3\\Functions_F_MP_Mark\\Params\\paramTimeAcceleration.hpp\"\n};\n```\n\nPlease note that Param templates currently don't work with PBO missions manually copied to MPMissions folder.\nUnpacked missions, Steam missions and missions which are part of an addon work correctly.\nSee Mission Parameters for more info."},{"heading":"Scenario Setup","level":3,"markdown":""},{"heading":"Placing Player Slots","level":4,"markdown":"Place your playable units for both **BLUFOR** and **OPFOR**. Again, please note the current limitations, only BLUFOR and OPFOR can be player-controlled."},{"heading":"Respawn Markers","level":4,"markdown":"Place a **Marker** at the players' initial position that will assign the initial respawn position.\nThen make sure to call it **respawn_west** and **respawn_east** depending whether for **WEST** (BLUFOR) or **EAST** (OPFOR)."},{"heading":"Headquarters Entity","level":4,"markdown":"The **Headquarters Entity** serves as the speaker for the side.\nThis entity is the HQ which gives players hints on how or what they have to do during the mission.\nMake sure to place a **Headquarters Entity** by selecting **Modules (F7)** and navigating to the **Intel** category.\nAlso, **make sure to name this module**. Its name will be used later so we can reference this entity.\nFor the *west* entity name it **BIS_west_speaker** and for the *east* entity name it **BIS_east_speaker**. Make sure to set the correct side of the HQ entity within the module."},{"heading":"Objectives Instance","level":4,"markdown":"Select **Modules (F7)** and navigate to the **Objectives** category. Place the **End Game Objectives Instance** module.\nThis will tell the game to initialize the End Game systems on mission start.\nThe module has one property, the **End Game Threshold**, which tells the system how many Intel packages a side must download for the last phase to start, during the middle game stage, or **Stage 2**.\n\n**End Game Threshold** - The amount of retrieve intel tasks a side must complete in order to succeed the 2nd stage and move to the 3th and final stage.\n**Warmup Delay** - The amount of time in seconds players are locked in the warmup phase at the start of the scenario."},{"heading":"Start Game Objectives","level":4,"markdown":"So now, let's place our our first objectives. These will be the **Start Game Objective**, and each playable side must have their own unique one.\nSo select **Modules (F7)** and double click on the map. After the modules selection window appears, navigate to the **Objectives** category and, for each side, place a **EndGame Start Game Objective** where you want the side to Establish their FOB.\nWithin the module itself, you **must** set the side which will be tasked with this objective.\nEvery Start Game Objective modules must be synchronized with the Objectives Instance module.\n\n> [!NOTE]\n> Do not forget to add at least one for each of the playable sides.\n\n- **Attacking Side** - The side which will be tasked to this objective\n- **Succeed Radius** - The radius in which at least one player of the side doing this objective must be and the radius in which no enemy units can be\n- **Restriction Radius** - The radius in which players are confined until they complete this objective"},{"heading":"Middle Game Objective","level":4,"markdown":"A **Middle Game Objective (MGO)** is what could be called a **Retrieve Intel** objective.\nThese are the objectives which require players to move to their location and *download some intel* from the object connected to the *objective module*.\n\nTo place a Middle Game Objective select **Modules (F7)** and double click on the map. Once the modules window appears, navigate to the **Objectives** category and select the **EndGame Simple Objective**.\nEach **MGO** requires an object which is used to download Intel from, for example a car, UAV or a computer.\nGo ahead and place any object you would like, then name it, for example, *BIS_downloadPoint_1* and put this exact name in the module's **\"Downloadable Object\"** field.\nEvery Middle Game Objective modules must be synchronized with the Objectives Instance module.\n\nAny **triggers** connected to the module defines the mission objects' relation with the connected objective.\nFor example, if you have a trigger connected to the module, any mission objects inside it will be set as **owned by the objective** and will be hidden / deleted when the object is.\n\n**Note that the object to be downloaded from will be indestructible until one of the competing sides downloads intel from it.**\nIt is also good practice to lock vehicles (if used as download object) so players can't board and drive it away.\n\n- **Downloadable Object** - The name of the object to use as download source\n- **Download Radius** - The radius in which download will be available (Non-Functional)\n- **Task Description** - The description of this objective, for example, \"Download intel from UAV\"\n- **Instant Download** - Whether the download should be instant, if so, download is succeeded after interaction with object"},{"heading":"Randomizer Logic","level":4,"markdown":"**Randomizer** logics can be used to randomize **Middle Game Objectives**, so if more then one objective is connected to a randomizer, one at random will be selected at **mission start**.\nThe objectives not selected **will be deleted**, along with their **owned objects**."},{"heading":"End Game Objective","level":4,"markdown":"The **End Game Objective** is the objective which handles the last phase of the game mode. It defines the possible **pickup / upload** locations and how long the match can take when in the last phase.\n\nSo start by selecting **Modules (F7)**, navigate to the **Objectives** category and place a **EndGame End Game Objective**.\nAfter placing our module, let's place one **Pickup** and at least two **Upload** objects.\nA pickup object is the object that is referred to as **Schematics**, and it is the object players need to pick up and use to upload the data.\nThe upload objects are the objects used to upload the **Schematics** to HQ.\nEvery End Game Objective modules must be synchronized with the Objectives Instance module.\n\n> [!NOTE]\n> One Pickup object and at least two upload objects are needed, if more are provided, these will be randomized.\n\n- **Time Limit** - The time limit for the 3th phase, if time limit is reached before one of the sides winning, the mission will end as a draw\n- **Pickup Objects** - List of all available pickup objects\n- **Upload Objects** - List of all upload objects (At least 2 are required, one per side or more)\n- **Note that the objects used as Schematics will be indestructible.**"},{"heading":"Resulting Layout","level":4,"markdown":"You should get something similar to the picture on the right."},{"heading":"Respawn Points","level":4,"markdown":"You can add positions which are turned into respawn points after an event. For example, a player of a side entering an objective area will unlock any respawn points available for that objective.\nThe system handles 3 kinds of respawn points:\n\n- **Respawn Point logic** connected to the **Start Game Objective**\n  - It is unlocked when the owner side establishes their FOB.\n- **BLUFOR / OPFOR game logics** connected to a **Simple Objective**\n  - These are unlocked when a player of a side enters an objective area.\n- **Respawn Point logic** connected to an Upload object which is used by the **End Game Objective**\n  - It is unlocked when the last phase starts and serves as a position for the upload defenders to respawn at.\n\nWhere to find the logics?\n\n- **BLUFOR / OPFOR game logics** can be found under **Units (F1) > Game Logics > Sides**.\n- **Respawn Point logics** can be found under **Units (F1) > Game Logics > Positions**."},{"heading":"Vehicle Respawn Modules","level":4,"markdown":"For any placed vehicles in the scenario, you may add a respawn module synchronized to them, making them respawn after being destroyed, damaged and/or abandoned.\nSuch module can be found under **Modules (F7) > Multiplayer > Vehicle Respawn**."},{"heading":"Final Notes","level":4,"markdown":"> [!IMPORTANT]\n> If one of the competing sides has no players at the moment when the third and last phase starts, the match will end with the side with players being the winner."}],"categories":["Arma 3: MP Modes","Introduced with Arma 3 version 1.42"],"groups":["Multiplayer and Server"]}