General SOPs

Gameplay

Rules	Explanation
1	Our events are large, and we need order so that we can accomplish our objectives in a timely fashion so everything doesn't descend into chaos.
2	A flight can't be effective if they are not coordinating. If you're doing your own thing, you aren't operating as a cohesive unit, and your flight lead can't use his flight's full potential to accomplish his task. If flights fall apart, the package will fall apart. Learn the basic formations. Leads will often be happy with Wedge or Finger Four formations if they don't specify.
3.1	Depending on the situation, flight leads need to hear from their wingmen in order to understand what their wingmen are doing. If a wingman receives a launch warning from his RWR, for example, the wingman should immediately announce the launch using proper brevity if able. Even a simple, "2 Defensive SAM!" in the heat of the moment is better than nothing.
3.2	Radios in the F-16, and often other aircraft, operate in half-duplex. If you are transmitting, you can't hear. Also, multiple transmissions on the same frequency effectively jam that frequency, making no transmission clearly heard. It's very easy to lose transmissions or tie up the radio if you're communicating useless information. It's more important for leads to communicate than wingmen to give non-essential status information.
3.3	Sometimes element lead speaks for the flight, such as when he is leading the "hot" element during a grinder.
4	If everyone is a leader, no one is a leader, and we descend into chaos. Leaders lead. Wingmen are extensions of their leads. This doesn't mean you can't question the lead if he gives an impossible order, or respond with "unable" to a directive that is clearly going to get you killed; just don't try to mutiny and hijack a flight for your own purposes.
5	Roles within a package are often very important dependent upon one another. It's a team effort. A flight needs to focus on its objective and do it well. If your mission's task is ESCORT, don't fly off to strafe ground targets. Others are depending upon you.

1. Each pilot should follow the directives of his lead, whether element, flight, or package.
2. Wingmen should try their best to fly visually with their lead unless he says otherwise.
3. Communication:
   1. Wingmen should communicate with flight leads as required.
   2. Wingmen should stay off the radio unless it's absolutely necessary/required.
   3. Package communication should be mostly limited to flight leads. (Some exceptions apply.)
4. Going solo and doing your own thing, or directly trying to contradict the lead's plans and perform a mutiny, can result in you being uninvited from future events.
5. Flights should follow their assigned tasks, and not arbitrarily choose new missions for themselves.

UOAF Events

Rules	Explanation
1	It can take a very long time to get everyone into the server. The moderator has a plan to get everyone into the server and into the sim as fast as possible, but he needs your help.
2	Some sims can be complicated to operate for newbies, and there are many pitfalls. Usually for DCS and BMS, we require that people can take off, navigate, employ some weapons, fly something resembling a formation, communicate with lead, and land. If you can do this, and if you've flown in MP before, you should be good to attend an event. Nevertheless, UOAF reserves the right to request a checkride for any new attendant.
3	This sheet helps UOAF determine the amount of participants planning on attending a given event. We can't always secure people's wishes for which flights and slots they want, but we try our best to accommodate people. RSVP priority will be for Roster Members first and guests second with conflicts resolved by the Event Moderator.
4	The official event time is usually the briefing time. This is when the briefing needs to start in order for us to be on time. No one wants an unnecessarily long briefing. To that end, we have Marshal time, which is when everyone should begin gathering. You should be able to get into the server at Marshal time.
5	It is crucial that we start the event at event time. If that is briefing time, then we need to begin briefing right at that point. All participants are expected to be ready. While we wish to be helpful, our official events are not tech sessions; we cannot be expected to solve people's tech issues with large events. Be respectful of the time other people are investing in this. Please test your hardware and setup prior to event time, preferably before event day. If you need assistance, ask before event day!

1. Each participant should listen to, understand, and follow the directives from the Event Moderator.
2. UOAF events are generally open to all members of the community who consider themselves ready, however, some restrictions may apply. Check out the UOAF Event SOPs/Minimum Competencies.
3. All pilots who wish to attend an event should sign up on the event-specific RSVP sheet found in the #Announcements channel on UOAF Discord. Players can request slots or flights, but these will ultimately be decided on by the mission commanders.
4. Marshal and Briefing times must be respected.
5. All participants will show up on time with all hardware and installations ready to go at or before event time.

BMS-Specific

Rules	Explanation
1.	Loadouts are crucial to mission planning. Also, BMS doesn't play nicely with multiple people editing the loadout of a flight at the same time. Leave this to Flight Leads to manage their flight's loadouts.
2	Flight plans are crucial to mission planning. Leave this to Flight Leads to manage.
3	This has a tendency to make BMS unstable.
4	This is set by the mission planner, and should NOT be moved. Moving Bullseye while someone is in 3D can crash BMS.
5	Saturday events host upwards of 40 pilots. In order to get through the brief and into 3d in a timely manner, comm discipline needs to be exercised.
6.1	Bandwidth settings for BMS is a complex topic. Clients should enter bandwidth values that reflect 70% of their download and upload rates. Clients need to enter a minimum of 4mb. If you don't enter the correct values, you will be asked to reconnect with the correct values. Please be courteous and get your Bandwidth values set correctly prior to Event Time.
6.2

1. Wingmen shouldn't touch loadouts. View your stores load via the mission briefing.
2. Wingmen shouldn't touch the flight plans.
3. Wingmen shouldn't change anything to do with ground troops.
4. Bullseye shouldn't be changed.
5. Only flight leads talk during Package Brief/Debrief (wingmen listen)
   • Element leads and wings may talk/ask questions during individual flight brief
6. Bandwidth
   • Download Bandwidth should be set no lower than 4096.
   • Upload Bandwidth should be set no lower than 2048.

UOAF Pickup

• Guests are welcome to create and run pickup flights outside of main events.
• Guests can join or create a pickup flight by asking in Discord.
• Guests are expected to follow flight standards laid out in Gameplay SOPs.

UOAF Roster

• Roster members are expected to be flight commander capable, possess a high degree of competence in flight simulation, and maintain a good reputation and behavior.
• Roster members are expected to take flight leader and element leader positions during flights as required.

UOAF Fragging / Mission Planning

• Mission Planners who are creating event missions will be subject to DCS and BMS frag guidelines for mission quality purposes.