Difference between revisions of "BMS Live Fragging"
Jump to navigation
Jump to search
(Created page with "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, pa...") |
|||
| Line 1: | Line 1: | ||
| − | Fragging workflow | + | ==Fragging workflow== |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | Fragging checklist | + | *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) |
| − | Does each steerpoint for each flight have a cruise air speed > 300 knots? | + | *The overall situation in the campaign should be addressed briefly to give some background and input to the fragging process |
| − | Is the altitude for each steerpoint appropriate? | + | *After the meeting, the event coordinator ensures work proceeds on the event, and is responsible for finding replacements for key figures if need be |
| − | Will the SEAD and/or escort be in front of the strikers in time to deal with threats? | + | *The fragger and package lead can collaborate to hatch and refine a plan |
| − | Is there at least 1 minute between each take off time? | + | *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 | ||
| + | |||
| + | <br /> | ||
| + | |||
| + | ==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? | ||
| + | *Does the escort and SEAD have enough time to work their steer points before strikers arrive? | ||
| + | *Is there at least 1 minute between each flight TOT on a co-located target? | ||
| + | *Are all co-located flight plan steer points deconflicted by either time on steer or altitude? | ||
| + | *Does every flight have an abort airfield that is safe and close to the FLOT? | ||
| + | *Are navigation steerpoints separated by a minimum of 20-30nm (Med Alt Only) + logical? | ||
| + | *Does the package have the means (weapons, terrain) to deal with every threat within range of the flight plan? | ||
| + | *Is there an AWACS fragged? | ||
| + | *Is the server flight fragged in a location to maximize the server's FPS performance? | ||
| + | |||
| + | <br /> | ||
Revision as of 02:45, 18 December 2022
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?
- Does the escort and SEAD have enough time to work their steer points before strikers arrive?
- Is there at least 1 minute between each flight TOT on a co-located target?
- Are all co-located flight plan steer points deconflicted by either time on steer or altitude?
- Does every flight have an abort airfield that is safe and close to the FLOT?
- Are navigation steerpoints separated by a minimum of 20-30nm (Med Alt Only) + logical?
- Does the package have the means (weapons, terrain) to deal with every threat within range of the flight plan?
- Is there an AWACS fragged?
- Is the server flight fragged in a location to maximize the server's FPS performance?
