BMS Live Fragging

Fragging workflow 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

Fragging checklist Does each steerpoint for each flight have a cruise air speed > 300 knots? Is the altitude for each steerpoint appropriate? Will the SEAD and/or escort be in front of the strikers in time to deal with threats? Is there at least 1 minute between each take off time?