Difference between revisions of "BMS Live Fragging"

From UOAF Codex
Jump to navigation Jump to search
Line 52: Line 52:
 
***Discuss Plan, Phasing, Contracts, Contingencies
 
***Discuss Plan, Phasing, Contracts, Contingencies
 
***Discuss DTC items (STPT lines, PPTs) (Post in Discord if desired)
 
***Discuss DTC items (STPT lines, PPTs) (Post in Discord if desired)
 +
***Consider the need for support assets (AI AWACS, AI SWEEP flight)
 +
***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'''

Revision as of 07:19, 18 December 2022

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)
  • The overall situation in the campaign should be addressed briefly to give some background and input to the fragging process
  • After the meeting, the event coordinator ensures work proceeds on the event, and is responsible for finding replacements for key figures if need be
  • The fragger and package lead can collaborate to hatch and refine a plan
  • 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)
  • 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


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 trying 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 target, and opposing forces expected
    • Assign Flight Leads.
      • Paper Rock Scissors
      • Volunteer or Voluntold.
      • Fragger, wield the hammer!!!
    • PACKAGE STRUCTURE FINALIZED no later than Muster Plus 15min
  • Get Busy Fragging
    • Fragger: Add the Package via 2D map/ATO
      • Create Package, 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 or remove them if not desired
      • SAVE THE MISSION
      • ATO PACKAGE CREATED no later than Muster Plus 30min
    • Flight Leads (not-fragger)
      • Discuss Plan, Phasing, Contracts, Contingencies
      • Discuss DTC items (STPT lines, PPTs) (Post in Discord if desired)
      • Consider the need for support assets (AI AWACS, AI SWEEP flight)
      • 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)
    • 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