After consultation, I've documented the following operational doctrine for FGM within its ArmA III operations.
Doctrine is the expression of how military forces contribute to campaigns, major operations, battles, and engagements. It is a guide to action, rather than hard and fast rules. Doctrine provides a common frame of reference, helping standardize operations, and facilitate readiness by establishing common ways of accomplishing military tasks.
Vision
To enjoy the multi-player experience of ArmA III through team work, camaraderie and game play immersion.
Strategy
Operations can be identified using two categories. Open involvement & immersion events.
Open involvement is exactly that, operational structure, tactics and communication are not pre-defined, scenarios will be run under the remit of those in-game. The level of operational discipline and banter, provided it is respectful, is under the consensual agreement of those active on the server. In basic terms, do what you want.
Immersion events. These events will aim to be run with a militaristic structure and an element of operational discipline. Within these events we will look to stretch those involved and get the adrenaline flowing. Structure will be based upon squads and two fire teams per squad with mixed combat competencies, AT, Medic, LMG etc. Squad and fire team leaders are expected to be vocal and willing to support immersion. Squad size can fluctuate as large as 12 with a fire team being a minimum of 2. These events will also look to develop battle buddy tactics and standardised radio communication terminology, all with the objective of having fun through increasing immersion.
Schedule
Week days the server will be open involvement for all members. This is also an opportunity for groups to run boot camp events or test research and developments. New content will be focussed on immersion events, with those scenarios that add value then being available for open involvement.
Saturdays, the server will be open involvement unless someone wishes to call for an immersion event. Immersion events should be broadcast in the forums prior to give everyone the opportunity to join should they wish to.
Sundays, the sever will run an immersion event. Muster starts from 13:00 GMT, briefing at 13:15 and boots on the ground at 13:30. Those joining later are welcome but will have to hit the ground running.
Activation
Scenarios
Finding suitable scenarios for around 10 people is not that easy. Much of the MP content on steam is either for below 5 people or not optimised, resulting in a poor game play experience. Open dynamic content helps keep scenarios interesting and adds longevity. This minimises server maintenance and allows everyone to focus on participation.
In the medium term we must begin to develop the skills and competencies within the FGM community to develop scenarios. This will help ensure we have sustainable content. Tools such as MCC, Alive and the BIS editor will support this content. I will look to create a research and development group to share knowledge and expand our skill sets. This will help accelerate learning and is also a area of interest for many involved in ARMA III.
MODs
To support the vision and to minimise server management additional MOD content must be stable, and provide a game play functional benefit and also an immersion benefit. Thorough testing on any new MOD will be done before release to the FGM community. A locked FGM MOD sticky will be maintained to ensure transparency on MOD requirements.
This doctrine is by no means a fait accompli. It is expected to be a living breathing embodiment of all that is FGM ARMA III. Please feel free to add your views and constructive inputs and I will edit the doctrine where appropriate.
Doctrine is the expression of how military forces contribute to campaigns, major operations, battles, and engagements. It is a guide to action, rather than hard and fast rules. Doctrine provides a common frame of reference, helping standardize operations, and facilitate readiness by establishing common ways of accomplishing military tasks.
Vision
To enjoy the multi-player experience of ArmA III through team work, camaraderie and game play immersion.
Strategy
Operations can be identified using two categories. Open involvement & immersion events.
Open involvement is exactly that, operational structure, tactics and communication are not pre-defined, scenarios will be run under the remit of those in-game. The level of operational discipline and banter, provided it is respectful, is under the consensual agreement of those active on the server. In basic terms, do what you want.
Immersion events. These events will aim to be run with a militaristic structure and an element of operational discipline. Within these events we will look to stretch those involved and get the adrenaline flowing. Structure will be based upon squads and two fire teams per squad with mixed combat competencies, AT, Medic, LMG etc. Squad and fire team leaders are expected to be vocal and willing to support immersion. Squad size can fluctuate as large as 12 with a fire team being a minimum of 2. These events will also look to develop battle buddy tactics and standardised radio communication terminology, all with the objective of having fun through increasing immersion.
Schedule
Week days the server will be open involvement for all members. This is also an opportunity for groups to run boot camp events or test research and developments. New content will be focussed on immersion events, with those scenarios that add value then being available for open involvement.
Saturdays, the server will be open involvement unless someone wishes to call for an immersion event. Immersion events should be broadcast in the forums prior to give everyone the opportunity to join should they wish to.
Sundays, the sever will run an immersion event. Muster starts from 13:00 GMT, briefing at 13:15 and boots on the ground at 13:30. Those joining later are welcome but will have to hit the ground running.
Activation
Scenarios
Finding suitable scenarios for around 10 people is not that easy. Much of the MP content on steam is either for below 5 people or not optimised, resulting in a poor game play experience. Open dynamic content helps keep scenarios interesting and adds longevity. This minimises server maintenance and allows everyone to focus on participation.
In the medium term we must begin to develop the skills and competencies within the FGM community to develop scenarios. This will help ensure we have sustainable content. Tools such as MCC, Alive and the BIS editor will support this content. I will look to create a research and development group to share knowledge and expand our skill sets. This will help accelerate learning and is also a area of interest for many involved in ARMA III.
MODs
To support the vision and to minimise server management additional MOD content must be stable, and provide a game play functional benefit and also an immersion benefit. Thorough testing on any new MOD will be done before release to the FGM community. A locked FGM MOD sticky will be maintained to ensure transparency on MOD requirements.
This doctrine is by no means a fait accompli. It is expected to be a living breathing embodiment of all that is FGM ARMA III. Please feel free to add your views and constructive inputs and I will edit the doctrine where appropriate.