Archive:Operation: Fortress: Difference between revisions

Line 72:

==Proper Use of Mumble==

In Mumble under "Special Projects and Events" you'll find the fleet's main channel, "Operation: Fortress", along with several subchannels under it: "Red Squadron", "Blue Squadron", etc. For optimal use and efficiency, especially when a QRF (Quick Response Force) is active, please adhere to the following guidelines for proper comms ~~(Mumble)~~ use. These have proven most effective and should apply under most circumstances.

In Mumble under "Special Projects and Events" you'll find the fleet's main channel, "Operation: Fortress", along with several subchannels under it: "Command", "Red Squadron", "Blue Squadron", etc. For optimal use and efficiency, especially when a QRF (Quick Response Force) is active, please adhere to the following guidelines for proper comms use. These have proven most effective and should apply under most circumstances.

(Some of the organization and discipline described below mirrors that of the Ivy League Navy channels and their "Command" subchannels, so if you've flown in a "regular" fleet, they should be familiar.)

* The main Mumble channel "Operation: Fortress" should remain manned at all times so fleet members (who may or may not be involved in a QRF) can benefit from local intel and security.

* When a QRF is active:

** ~~The~~ QRF Fleet Commander (whoever is leading the operation at the time) may ~~designate one of~~ the ~~subchannels (e.g., "Red Squadron"), as the "command" channel. He would then typically~~ invite ~~all~~ wing and squad commanders and scouts there to coordinate the operation without broadcasting details to the general fleet.

** Because operational security is often a concern (spies), the QRF Fleet Commander -- whoever is leading the operation at the time -- may want to use the Command subchannel and invite wing and squad commanders and scouts there to coordinate the operation without broadcasting details to the general fleet.

** ~~Everyone should remain in~~ the ~~main~~ channel ~~unless invited to the "command" channel by~~ the FC. (~~However, if~~ you~~'re in a subchannel being used for purposes other than the QRF, then staying there should~~ be ~~fine~~.)

** Only join the Command channel if the FC invites you (otherwise you will be kicked and possibly banned from Mumble).

** Standard fleet comms displine should be observed. Of course, as with "regular" fleets, the FC may relax comms at his/her discretion.

* Please avoid inappropriate language. This is a general University rule anyway, but it ~~may be~~ a bit more important in the Fortress because ~~a variety~~ of ~~members~~ frequently join ~~the channel~~ and participate ~~in the open fleet~~.

* Please avoid inappropriate language. This is a general University rule anyway, but it's a bit more important in the Fortress because it's an open fleet and members of various ages and disciplines frequently join and participate.

* Finally, of course, enjoy any and all explosions!

@@ Line 72: / Line 72: @@
 ==Proper Use of Mumble==
-In Mumble under "Special Projects and Events" you'll find the fleet's main channel, "Operation: Fortress", along with several subchannels under it: "Red Squadron", "Blue Squadron", etc. For optimal use and efficiency, especially when a QRF (Quick Response Force) is active, please adhere to the following guidelines for proper comms (Mumble) use. These have proven most effective and should apply under most circumstances.
+In Mumble under "Special Projects and Events" you'll find the fleet's main channel, "Operation: Fortress", along with several subchannels under it: "Command", "Red Squadron", "Blue Squadron", etc. For optimal use and efficiency, especially when a QRF (Quick Response Force) is active, please adhere to the following guidelines for proper comms use. These have proven most effective and should apply under most circumstances.
-(Some of the organization and discipline described below mirrors that of the Ivy League Navy channels and their "Command" subchannels, so if you've flown in a "regular" fleet, they should be familiar.)
 * The main Mumble channel "Operation: Fortress" should remain manned at all times so fleet members (who may or may not be involved in a QRF) can benefit from local intel and security.
 * When a QRF is active:
-** The QRF Fleet Commander (whoever is leading the operation at the time) may designate one of the subchannels (e.g., "Red Squadron"), as the "command" channel. He would then typically invite all wing and squad commanders and scouts there to coordinate the operation without broadcasting details to the general fleet.
+** Because operational security is often a concern (spies), the QRF Fleet Commander -- whoever is leading the operation at the time -- may want to use the Command subchannel and invite wing and squad commanders and scouts there to coordinate the operation without broadcasting details to the general fleet.
-** Everyone should remain in the main channel unless invited to the "command" channel by the FC. (However, if you're in a subchannel being used for purposes other than the QRF, then staying there should be fine.)
+** Only join the Command channel if the FC invites you (otherwise you will be kicked and possibly banned from Mumble).
 ** Standard fleet comms displine should be observed. Of course, as with "regular" fleets, the FC may relax comms at his/her discretion.
-* Please avoid inappropriate language. This is a general University rule anyway, but it may be a bit more important in the Fortress because a variety of members frequently join the channel and participate in the open fleet.
+* Please avoid inappropriate language. This is a general University rule anyway, but it's a bit more important in the Fortress because it's an open fleet and members of various ages and disciplines frequently join and participate.
-* Finally, of course, enjoy any and all explosions!