General SOPs

From UOAF Codex
Jump to navigation Jump to search

Gameplay SOPs


Rule Translation Explanation
The chain of command will be respected and enforced at all times. Leadership consists of a Package Commander, a Flight Leader, and an Element Leader. Listen to the directives of your leader. 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.
Under no circumstance will pilots be able to edit their load outs, it is lead's (#1) or element lead's (#3)'s decision to do so and theirs only. Wingmen shouldn't touch the loadouts. 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.
Under no circumstance will pilots except Lead(#1) or the Package Commander change steer points in the 2D planner. Wingmen shouldn't touch the flight plans. Flight plans are crucial to mission planning. Leave this to Flight Leads to manage their flight's loadouts.
Under no circumstance will pilots edit or move ground troops without notifying or consulting a second party of their action. Wingmen shouldn't change anything to do with ground troops. This has a tendency to make BMS unstable.
Comms integrity will be maintained at all times and without exception. Stay off the radio unless it's absolutely necessary. Radios in the F-16 operate in half-duplex, and multiple transmissions effectively jam the signal. It's very easy to lose transmission or tie up the radio.
Discipline will be maintained in the air and without exception. Follow your lead's directives; try your best to fly formation with him unless he says otherwise. 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
Wingmen will follow their leads' orders and aircraft at all times and will respond to all directives appropriately. Failure to do so will result in a kick or ban from the community. Countermanding orders will lead to decisive disciplinary action. Wingmen should communicate with Flight leads as required. 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. 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 or respond with "unable" to a directive; just don't try to mutiny and hijack a flight.
Flights will function within their assigned roles and flight plans as part of the package at all times and without exception. Flights should follow their assigned tasks, and not arbitrarily choose new missions for themselves. 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.


1.1 The chain of command will be respected and enforced at all times. Leadership consists of a Package Commander, a Flight Leader, and an Element Leader.

1.2 Under no circumstance will pilots be able to edit their load outs, it is lead's (#1) or element lead's (#3)'s decision to do so and theirs only.

1.3 Under no circumstance will pilots except Lead(#1) or the Package Commander change steer points in the 2D planner.

1.4 Under no circumstance will pilots edit or move ground troops without notifying or consulting a second party of their action.

1.5 Comms integrity will be maintained at all times and without exception.

1.6 Discipline will be maintained in the air and without exception.

1.7 Wingmen will follow their leads' orders and aircraft at all times and will respond to all directives appropriately. Failure to do so will result in a kick or ban from the community. Countermanding orders will lead to decisive disciplinary action.

1.8 Flights will function within their assigned roles and flight plans as part of the package at all times and without exception.

UOAF Event SOPs

2.1 Event moderator's are UOAF Regulars who ensure events run smoothly.

2.1.1 The event moderator will handle any conflicts as fairly as possible.

2.1.2 All players will follow the directions of the event moderator/s.

2.2 UOAF events are open to all members of the community who consider themselves ready.

2.2.1 New players flying their first event will be required to have flown on a pickup flight with a player that has flown past events. This SOP can be overridden at event moderator's discretion.

2.3 Members of the community that wish to attend a UOAF event must RSVP on the event’s signup sheet

2.3.1 Players can request slots or flights, but these will ultimately be decided on by the event moderator.

2.3.2 RSVP priority will be as follows: Roster members, guests.

2.3.3 Contested slots will be decided by the event moderator.

2.4 Players will show up on time with all hardware and installations ready to go.


UOAF Pickup SOPs

3.1 Players are welcome to create and run pickup flights outside of main events.

3.2 Players can join or create a pickup flight by asking in discord, teamspeak, or the forums.

3.3 Players are expected to follow flight standards laid out in 1.0 Gameplay SOPs.

UOAF Roster SOPs

4.1 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.

4.2 Roster members are expected to take flight leader and element leader positions during flights.

4.3 Roster members who are creating event missions will be subject to DCS and BMS frag guidelines.