This is a revision to GO-07-20 (which replaced GO-3-20, which replaces GO-05-19 which replaced GO-2-18)
Due to the number of Games in Pegasus Command, the size of said games, the number of ops for each game, and the number of members in Pegasus Command that play multiple games, the following revisions to the above refenced rule is so ordered:
Game Ops were previously “protected” in their time slot, but per GO-07-20 games no longer have a 100% protected time slot. To help accommodate members that enjoy multiple games in Pegasus Command, Game Commanders need to make every effort to refrain from overlapping another game op when scheduling new ops. This is not always possible, but no game op should overlap another game’s op more than one time per week. This applies to the set time and the hour from that time. This will ensure that our members have every opportunity to attend as many various game ops as possible, and not be forced to choose between games for every op. If there is a conflict, the standing op holds precedent, but game commanders are encouraged to work together to stagger times to do what is best for Pegasus Command as a whole. In addition, every effort should be made to avoid scheduling ops during Pegasus Command Guild events. While this is not always possible for special events, reoccurring ops should be scheduled outside Guild Wide events.
Each game will have a 2 hour block that is protected from a Pegasus Command streaming standpoint (first come, first served). It is expected that all game commanders make their best effort to see that their games are streamed each week on the Pegasus Command channel.
If your game has multiple ops during the week, the streaming requirement is only for one of them (GC choice which one, but it needs to be standardized). If you can stream multiple ops each week, this is fantastic, however it is not required.
If there is a conflict and the GCs are unable to find a resolution, the SC will make a final decision.