BETA / LIVE
Organising a Mission and the UNITAF Framework - UNITAF Force Manual (FM)


Group

Organising a Mission and the UNITAF Framework



FM/BG-1243 - Introduction to Mission Making in UNITAF

UNITAF operations follow a strict framework which is outlined in this section. Ultimately the goal of standardisation in UNITAF is to ensure in our system of dynamic ORBATs that standardisation is maintained across all operations so players know what to expect when joining, preparing, planning, gearing out and executing UNITAF operations. This standardisation encompasses but is not limited to;

  • What factions can be played
  • Duration of missions
  • SOP standardised ORBAT organisation
  • ORBAT restrictions
  • Equipment restrictions
  • Database integration
  • Limited arsenals
FM/BP-1244 - The UNITAF Framework

All UNITAF operations use a database framework which ultimately issues standard loadouts to players based on database driven loadouts directory. The framework can be obtained from Operations Command (OC) or Operations Staff (J3) a template is provided and can be copied to your desired maps.

For a mission to be approved, it must follow the framework, in order to follow the framework it must be in line with the following;

  • Full arsenals are not to be used under any circumstances, this means;
    • Arsenal content is dictated by the Framework and restricted per the content provided to it by Loadouts Staff (J5) in accordance with FM/C110 - Loadouts and Factions
    • Arsenals with unrestricted content, or not utilising the Framework are not permitted.
  • Loadouts should be attainable through the framework ORBAT injection system and must be approved by Loadouts Staff (J5)
  • All mods must be on the UNITAF approved mods list
  • The faction players are deploying as must be an approved faction
    • Approved factions have limited arsenals prepared already according to that factions equipment
    • Approved factions have default loadouts created for all combat positions that can be ORBAT deployed
    • If a faction is not on the approved factions list, then the faction must be created before the mission can be approved
  • The mission file with integrated framework should be ready and tested, prior to the ORBAT being released.
FM/BP-1669 - Theatre operation naming convention
  • Theatre Operations must be named using the format:
    • Operation [Name] [Roman Numeral] (e.g. Operation Overlord I).
  • The operation name must remain unchanged for all deployments within the same operation.
  • If the mission is a one-off operation, there is no requirement to use a Roman numeral.
  • The Roman numeral must increment sequentially for each deployment within the same operation.
  • The maximum number of deployments within a Theatre Operation is 10, anything beyond this should be submitted to J3 as a campaign.
  • The first deployment of an operation must use Roman numeral I.
  • Each subsequent deployment must increase the numeral by one sequential value.
  • Subtitles, additional descriptors, or secondary naming elements are not permitted.
This page generated 1.56MB in 0.1149 seconds.