Plugins are the backbone of the Framework, determining what features are added into the mission and how they are configured - and as such they behave in a fundamentally modular manner, configured to not only work out of the box with the rest of the Framework, but also simple to be disabled and removed should the mission maker call for it.

If one or more features aren't what you need in your mission, worry not, as removing them is very simple. Open and comment whatever you desire from:

framework\plugins\plugins.cpp

Keep in mind that every single plugin has been added for a reason and is properly optimized - removing plugins to avoid "bloat" might be tempting but it solves a problem that doesn't exist in the first place.

Adds a help entry for medical in the diary and some mission parameters.

Revive time - determines how long players will have to live after going unconscious.
Lives - How many times can a player die before no longer being able to get up.
Medical System - determines between the Advanced and Basic medical system.
Make everyone medic - Self-explanatory.

Manages some stuff about the spectator system.

Spawn AI.

This is a large subject, so this plugin is detailed in further detail in its own page.

Runs code when a player leaves the designated area of operations, denoted by a marker named "ao".

left_ao_do = { hintSilent "Please remain within the area of operations."; }; // Default
left_ao_do = { _targetObject setPos _pos; }; // Force player/vehicle to remain in the AO.
left_ao_do = { _targetObject setDamage 1; }; // Kill deserters

It's very common that depending on the context of your mission, the use of Third Person perspective might be undesirable: for TvTs and other scenarios where realism is intended, it can cause balance issues and make things weird. However disabling it all together isn't a good solution as some missions will require players to drive in vehicles with no modeled interiors or fly on first person only, which might prove difficult.

So in order to give the mission maker the choice, a plugin to block the use of third person depending on context has been included into the Framework.

// Command group
tp_allowed_units = [blu_0_0_1, blu_0_0_2, blu_0_0_3];
// Command, squad leaders, and team leaders
tp_allowed_units = [blu_0_0_1, blu_1_0_1, blu_1_1_1, blu_1_2_1, blu_2_0_1, blu_2_1_1, blu_2_2_1, blu_3_0_1, blu_3_1_1, blu_3_2_1, blu_4_0_1, blu_4_1_1, blu_4_2_1, blu_5_0_1];
// Vehicle crew
tp_allowed_units = [blu_11_1_1, blu_11_1_2, blu_11_1_3, blu_12_1_1, blu_12_1_2, blu_12_1_3, blu_12_1_4];
// Helicopter/Plane pilots
tp_allowed_units = [blu_13_1_1, blu_13_1_2, blu_14_1_1, blu_14_1_2, blu_14_2_1, blu_14_2_2];

Ends the mission after a certain parameter determined percentage of mission set groups have died.

Integrated to work with the framework as a Plugin you can easily disable and configure.

Press Ctrl + \ to open the menu to change your terrain/object rendering distance.

Players can get particularly trigger-happy in missions, completely disregarding the safety of the poor and innocent virtual dwellers of their virtual battles. In order to add some extra dose of challenge, this script will watch over how many civilians are killed, and upon reaching a certain threshold, punish the perpetrators with a mission failure.

Before a mission can be properly started, some extra preparations are usually needed, whatever they may be. With that in mind, this plugin will make sure that until an authorized unit gives the mission the All Clear, players will not be able to fire their weapons, throw any grenades, enter any vehicles, or if your mission is a TVT, leave their setup zones.

Working with DAC can be confusing and painful, especially considering the vast amount of features and customizations. With that in mind, the Framework includes a way to create DAC zones using nothing but verbose sentences, all Headless Client compatible.

This is a large subject, so this plugin is detailed in further detail in its own page.

Ain't nothing better than some good ol' blue on blue to spice up some engagements. But for whenever you need to know who just annihilated one of their own, this plugin will come in handy.

Displays markers for player groups on the map.

If any of you doesn't know what a Headless Client is, I suggest you start by reading this. Otherwise, this plugin will determine which entity will be tasked with running the relevant AI scripts.

Some nice and simple pre-configured intro cutscenes that you can use in your mission.

Adds a scroll action that allows players who Join in Progress to teleport to their squad mates.

Draws a black screen with a loading message, while the player's game loads.

Covers the area outside of operations with a marker, in order to emphasize its borders, denoted by a marker named "ao".

Sets the mission conditions such as weather and time.

Adds a few handy scroll actions to the player when testing in single player.

• Arsenal (Vanilla/ACE)
• Initialize/Stop AI units

Provides a multiplayer compatible arsenal garage.

BRM_FMK_MPGarage_fnc_open
	0: Object/Array/String position - The position of the shown vehicles
		Object - position and direction of object
		Array - position and optional direction (direction: index 3)
		String - position and direction of Marker

	1: Bool allowExternal - False to disable load/save (optional, default: true)
	2: Code spawnHandler - Custom code that is called when player presses OK (optional, default: spawns the selected vehicle near the position)
		Params: [Array position, Number direction, String vehicleClass, String texture, Array animations, Array loadout]
			position: Position that was passed to "Open", converted to Array position
			direction: Direction that was passed to "Open", in position
			vehicleClass: Class name of the selected vehicle
			texture: Variant class name
			animations: Array of animation sources and probability: ["AnimationSource1", 0, "animationSource2", 1]; Probability is 1 if selected, otherwise 0
			loadout: Array of the selected pylon loadouts: [[pylonIndex, pylonPriority, pylonMagazineName, pylonTurret], ...]

	3: String/Array/Code vehicleFilter - Filters the selectable vehicles (optional, default: "all")
		String - predefined filters: "air", "plane", "heli", "land", "car", "tank", "static", "ship", "all". Invalid filter name results in no vehicles being allowed
		Array - CfgVehicles type names. E.g. ["Motorcycle"], ["Tank", "StaticWeapon"], ["Plane", "Motorcycle"]
		Code - called with params [Config vehicleClass]. Return true if vehicle is allowed.

	4: Bool allowIncompatiblePylons - True to allow incompatible weapons on pylons. (optional, default: false)

// Garage 20 meters in-front of player, facing same direction as player
[(player getRelPos [20, 0]) + [getDir player]] call BRM_FMK_MPGarage_fnc_open;

// Air-only garage on position/direction of helipad object, with no loading/saving.
[helipad, false, nil, "air"] call BRM_FMK_MPGarage_fnc_open;

// Garage on marker "Garage", with custom vehicle spawn handler.
["Garage", nil, {
	params ["_position", "_direction", "_vehicleClass", "_texture", "_animations", "_loadout"];

	systemChat format ["You selected a '%1'!", _vehicleClass];
}, nil] call BRM_FMK_MPGarage_fnc_open;

Allow players to place buildings and other objects.

After a certain period of time, the server will lock players into their current slots, and will prevent any attempt to re-join as a different unit.

Generates radio channels and frequencies based on what groups are active in the mission and setups players radio.

This simple respawn system manages player lives and whether or not a player should be able to respawn, integrated with the Spectator System.

Manages rounds for TvT/COTvT missions.

Creates a perimeter around the players in TvT missions in which they cannot leave, removed only upon a certain time limit is reached or if the Commander Lock plugin is enabled, all sides are ready to start the mission.

Ever needed to spawn some AI in your mission without wanting to deal with DAC's limitations, but short of time to learn something new? Don't worry, the Framework has you covered. This plugin will handle AI spawning in an extremely flexible and simple manner, and in only a few minutes you'll have your enemies up and running.

The plugin utilizes only a single function, BRM_FMK_SpawnAI_fnc_infantry (although it does way more than just create infantry).

[WEST, "USARMY", 0, 2, 1, 0.5, "AWARE", "YELLOW", "PARADROP", ["B_Heli_Light_01_F"], true, ["point_2_1"], ["point_2_LZ"], ["point_2_2"], [200, 100, 50]] spawn BRM_FMK_SpawnAI_fnc_infantry;

Nobody likes getting killed because of an accidental grenade or misfire right after the mission starts. This plugin creates a protection zone around each side's respawn point, protecting friendly units from any kind of damage.

Whenever a player disconnects or leaves the session for whatever reason, the server will memorize its mission relevant data, like location, ACE status, gear and even what vehicle they were in - and then reassign them all upon them joining again.

Creates a diary page with information about all members of your side, separated by group, colored by class and denoted by rank. Works with custom callsigns.

Creates a module that makes time go faster. Can also freeze time.

After a certain time limit has passed in the mission, the main side in the mission will fail it.

Enables compatibility with the vanilla spectator system.