Difference between revisions of "BMS Live Fragging"

From UOAF Codex
Jump to navigation Jump to search
 
(8 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
==Live Fragging Considerations==
+
==BMS Live Fragging Considerations==
  
−
*During planning meetings, some time is set aside to discuss the two upcoming events, allocating as many people as possible to the two events (coordinator, package lead, server host/backup, and a fragger)
+
*Peoples' Time Is Valuable
−
*The overall situation in the campaign should be addressed briefly to give some background and input to the fragging process
+
**People like to fly BMS
−
*After the meeting, the event coordinator ensures work proceeds on the event, and is responsible for finding replacements for key figures if need be
+
**People don't mind spending a reasonable amount of time making sure their game time is soundly set up (enhances fun)
−
*The fragger and package lead can collaborate to hatch and refine a plan
+
**If this takes too long, people are going to get frustrated and quit the session
−
*The fragger creates the mission and products according to sop/other resources established by the frag team, and finally posts event to discord (format TBD)
+
**If roles are not cleanly being sorted and/or decisions not being made, people are going to get frustrated and quit the session
−
*This can be done individually or as a team effort (group fragging is encouraged for less experienced people)
 
−
*The frag can also be double checked by other fraggers, spontaneously or on request of the fragger
 
−
*Players RSVP indicating preferred slot, and are expected to read and process the briefing, in order to expedite briefing
 
−
*On game night, Package commander should be already aware of the tactical situation, possibly having planned with fragger ahead of time; package brief is kept to a minimum and flight briefs/question time can take most of the briefing time
 
−
*Mission is played, everyone has a good time
 
−
*Debriefing of event, feedback to fragger/pl/fl; keep track of issues and over time propose changes to fragging SOPs if necessary
 
  
 
<br />
 
<br />
  
−
==Live Fragging checklist==
+
*Fully pre-fragged regular event Saturday missions normally commit to launch an hour or less after muster.
 +
**This process shouldn't take longer than that.
 +
 
 +
<br />
 +
 
 +
*This used to be "normal"
 +
**All Regular Saturday Events used to be put together like this
 +
**FNF's are almost always put together like this
 +
**There are a few people who do it really well, and others who lack experience
 +
**This is meant to capture the best practices, and provide a framework<br />
 +
 
 +
==BMS Live Fragging checklist==
 
[[File:FRAG-TL.png|861x861px]]
 
[[File:FRAG-TL.png|861x861px]]
  
Line 26: Line 31:
 
**Volunteer, or Voluntold.
 
**Volunteer, or Voluntold.
 
**'''FRAGGER IDENTIFIED''' no later than '''Muster Plus 2min'''
 
**'''FRAGGER IDENTIFIED''' no later than '''Muster Plus 2min'''
−
**If you are still trying to pick a fragger after like 2-3 minutes... just give up and go do something else (try again another day)
+
**If you are still struggling to pick a fragger after like 2-3 minutes... just give up and go do something else (try again another day)
 
*Spend 6-9 minutes analyzing the campaign to identify the Mission/Target.
 
*Spend 6-9 minutes analyzing the campaign to identify the Mission/Target.
 
**Solicit input from players (preferences, suggestions)
 
**Solicit input from players (preferences, suggestions)
Line 33: Line 38:
 
*Spend 5 minutes or so deciding on Package Make-Up
 
*Spend 5 minutes or so deciding on Package Make-Up
 
**i.e. 4-Ship SWEEP, 4-Ship SEAD, 2-Ship OCA (or whatever)
 
**i.e. 4-Ship SWEEP, 4-Ship SEAD, 2-Ship OCA (or whatever)
−
**Based upon target, and opposing forces expected
+
**Based upon attendance/preferences, target, and opposing forces expected
−
**'''PACKAGE STRUCTURE FINALIZED''' no later than '''Muster Plus 15min'''
+
**Assign Flight Leads.
−
*Get Busy Fragging
+
***Paper Rock Scissors
 +
***Volunteer or Voluntold.
 +
***<u>Fragger, wield the hammer!!!</u>
 +
**'''PACKAGE STRUCTURE FINALIZED / FLIGHT LEADS SET''' no later than '''Muster Plus 15min'''
 +
*Get Busy Fragging.  These two functions should be going on simultaneously.
 
**Fragger:  Add the Package via 2D map/ATO
 
**Fragger:  Add the Package via 2D map/ATO
−
***Create Package, Lock Take-Off Time @20min from current game time
+
***Create Package, Click map @Target Area.  Lock Take-Off Time @20min from current game time
 
***Add the Supported Flight first (i.e. the OCA Strike, if you are striking an airbase)
 
***Add the Supported Flight first (i.e. the OCA Strike, if you are striking an airbase)
 
***Add the Supporting Flights next (i.e. the SWEEP and SEAD)
 
***Add the Supporting Flights next (i.e. the SWEEP and SEAD)
 
***Lock down the Takeoff Time, and TOT for the Supported Flight
 
***Lock down the Takeoff Time, and TOT for the Supported Flight
 
***Roll the takeoff times 1 minute earlier for the Supporting Flights (i.e. SEAD -1min, SWEEP -2min)
 
***Roll the takeoff times 1 minute earlier for the Supporting Flights (i.e. SEAD -1min, SWEEP -2min)
−
***Evaluate any hold points or remove them if not desired
+
***Evaluate any hold points for every package flight, or remove them if not desired (change from Hold to Nav)
 +
***Ensure there is a server flight fragged
 +
****For Campaigns, Server Takeoff Time should be far in the future
 +
****For Tactical Engagements, Server Takeoff Time should be with the package
 
***SAVE THE MISSION
 
***SAVE THE MISSION
 
***'''ATO PACKAGE CREATED''' no later than '''Muster Plus 30min'''
 
***'''ATO PACKAGE CREATED''' no later than '''Muster Plus 30min'''
 
**Flight Leads (not-fragger)
 
**Flight Leads (not-fragger)
 
***Discuss Plan, Phasing, Contracts, Contingencies
 
***Discuss Plan, Phasing, Contracts, Contingencies
−
***Discuss DTC items (STPT lines, PPTs)
+
***Assign Roles/Targets to the flights
 +
***Discuss DTC items (STPT lines, PPTs) (Post in Discord if desired)
 +
***Consider the need for support assets (AI AWACS, AI SWEEP flight, Tanker)
 +
***Consider where BULLSEYE should be located
 
*When the package is ready, Slot In and complete IVC Checks
 
*When the package is ready, Slot In and complete IVC Checks
 
**'''IVC CHECKS COMPLETE''' no later than '''Muster Plus 35min'''
 
**'''IVC CHECKS COMPLETE''' no later than '''Muster Plus 35min'''
−
*Are all co-located flight plan steer points deconflicted by either time on steer or altitude?
+
*Break up into Flight Briefings (<u>20min max</u>)
−
*Does every flight have an abort airfield that is safe and close to the FLOT?
+
**Set Flight Loadouts
−
*Are navigation steerpoints separated by a minimum of 20-30nm (Med Alt Only) + logical?
+
**Discuss/Modify flight paths (do not modify Takeoff or TOT)
−
*Does the package have the means (weapons, terrain) to deal with every threat within range of the flight plan?
+
**Set flight admin (TACAN, DL, J/B, Formation, Weaponeering/Assignments, Etc)
−
*Is there an AWACS fragged?
+
**Clean up any IVC problems
−
*Is the server flight fragged in a location to maximize the server's FPS performance?
+
**<u>Flight Leads, Wield the Hammer!</u>
−
 
+
**'''FLIGHT BRIEFS COMPLETE''' no later than '''Muster Plus 55min'''
−
<br />
+
*Take a 3-5min Bio Break
 +
*Speed-Read SOP's and '''COMMIT''' no later than '''Muster plus 60min'''
 +
**<u>FASTER IS BETTER</u>

Latest revision as of 18:06, 18 December 2022

BMS Live Fragging Considerations

  • Peoples' Time Is Valuable
    • People like to fly BMS
    • People don't mind spending a reasonable amount of time making sure their game time is soundly set up (enhances fun)
    • If this takes too long, people are going to get frustrated and quit the session
    • If roles are not cleanly being sorted and/or decisions not being made, people are going to get frustrated and quit the session


  • Fully pre-fragged regular event Saturday missions normally commit to launch an hour or less after muster.
    • This process shouldn't take longer than that.


  • This used to be "normal"
    • All Regular Saturday Events used to be put together like this
    • FNF's are almost always put together like this
    • There are a few people who do it really well, and others who lack experience
    • This is meant to capture the best practices, and provide a framework

BMS Live Fragging checklist

FRAG-TL.png

  • Start on time! MUSTER TIME.
    • Have the server up and running at Muster time (5-10min before is better)
    • HALT/STOP the clock on the server
  • Identify a fragger (if not already done)
    • Paper Rock Scissors
    • Volunteer, or Voluntold.
    • FRAGGER IDENTIFIED no later than Muster Plus 2min
    • If you are still struggling to pick a fragger after like 2-3 minutes... just give up and go do something else (try again another day)
  • Spend 6-9 minutes analyzing the campaign to identify the Mission/Target.
    • Solicit input from players (preferences, suggestions)
    • Fragger, wield the hammer and PICK the mission by Muster+10
    • MISSION/TARGET SELECTED no later than Muster Plus 10min
  • Spend 5 minutes or so deciding on Package Make-Up
    • i.e. 4-Ship SWEEP, 4-Ship SEAD, 2-Ship OCA (or whatever)
    • Based upon attendance/preferences, target, and opposing forces expected
    • Assign Flight Leads.
      • Paper Rock Scissors
      • Volunteer or Voluntold.
      • Fragger, wield the hammer!!!
    • PACKAGE STRUCTURE FINALIZED / FLIGHT LEADS SET no later than Muster Plus 15min
  • Get Busy Fragging. These two functions should be going on simultaneously.
    • Fragger: Add the Package via 2D map/ATO
      • Create Package, Click map @Target Area. Lock Take-Off Time @20min from current game time
      • Add the Supported Flight first (i.e. the OCA Strike, if you are striking an airbase)
      • Add the Supporting Flights next (i.e. the SWEEP and SEAD)
      • Lock down the Takeoff Time, and TOT for the Supported Flight
      • Roll the takeoff times 1 minute earlier for the Supporting Flights (i.e. SEAD -1min, SWEEP -2min)
      • Evaluate any hold points for every package flight, or remove them if not desired (change from Hold to Nav)
      • Ensure there is a server flight fragged
        • For Campaigns, Server Takeoff Time should be far in the future
        • For Tactical Engagements, Server Takeoff Time should be with the package
      • SAVE THE MISSION
      • ATO PACKAGE CREATED no later than Muster Plus 30min
    • Flight Leads (not-fragger)
      • Discuss Plan, Phasing, Contracts, Contingencies
      • Assign Roles/Targets to the flights
      • Discuss DTC items (STPT lines, PPTs) (Post in Discord if desired)
      • Consider the need for support assets (AI AWACS, AI SWEEP flight, Tanker)
      • Consider where BULLSEYE should be located
  • When the package is ready, Slot In and complete IVC Checks
    • IVC CHECKS COMPLETE no later than Muster Plus 35min
  • Break up into Flight Briefings (20min max)
    • Set Flight Loadouts
    • Discuss/Modify flight paths (do not modify Takeoff or TOT)
    • Set flight admin (TACAN, DL, J/B, Formation, Weaponeering/Assignments, Etc)
    • Clean up any IVC problems
    • Flight Leads, Wield the Hammer!
    • FLIGHT BRIEFS COMPLETE no later than Muster Plus 55min
  • Take a 3-5min Bio Break
  • Speed-Read SOP's and COMMIT no later than Muster plus 60min
    • FASTER IS BETTER
Retrieved from "http://codex.uoaf.net/index.php?title=BMS_Live_Fragging&oldid=7690"