Archive:Operation: Fortress: Difference between revisions

Line 13:

His hope was that the Operation: Fortress fleet would be running around the clock, each day.

PLEASE NOTE: The Fortress fleet is not intended to be an all-purpose fleet. For operations other than local intel and security, such as a general roam or anything else more than a few jumps away from HQ, a new fleet should be formed, and a new Mumble channel used for that operation's comms. Doing this keeps the Fortress fleet active and aligned with its purpose.

==How to create the Operation Fortress fleet==

==How to create the Operation: Fortress fleet==

Each day during scheduled maintenance any existing fleet is automatically disbanded. If you log in and search for fleets but are unable to find the Operation: Fortress in fleet finder, feel free to create one. Please ensure that there is only one Operation: Fortress fleet running at any given time.

Line 21:

Line 22:

* Right click on your name in any chat window and select ''“Form fleet with . . .”'' and the fleet window opens.

* Set up additional squads and wings, at least 2 wings with 5 squads each, although it doesn't hurt to just set up 5 wings with 5 squads each. This way there will always be enough individual squads for the separate groups.

** Create one wing for PvE, for people that want to mine or do missions

** Set up squads in the PvP wing(s) so they include Tackle, DD, Ewar/Logi.

** Change squads in the PvP wing(s) to: Tackle, DD, Ewar/Logi

** Create one wing for PvE, for people that want to mine or do missions.

** Make sure to ~~activate~~ free move so people can ~~set up their own squads as desired~~.

** Make sure to enable the "free move" option so people can move themselves within the fleet.

* Create a fleet finder advert.

Line 45:

Line 46:

After that please join the mumble channel for this operation, under '''Special Projects and Events'''.

If you haven't already, be sure to read the [http://wiki.eveuniversity.org/The_Rookie%27s_Guide_To_Fleet_Ops Rookie's Guide to Fleet Ops], which covers fleet terminology, how fleets operate, fleet member discipline, and other information you'll be expected to know if you join a QRF (Quick Response Force).

==What to do once you are in==

Line 51:

Line 54:

* Check the "My Fleet" tab to see in what Wing/Squad you where placed.

** Move yourself to squad that describes your function or ~~action in the fleet~~.

** Move yourself to a squad that describes your current function or activity. (Right-click your name and use the option "Move member".)

~~Click~~ your name and use the option "Move ~~menber~~".

* Listen to the Fortress mumble channel and pay attention to War Target reports in fleet and LiveIntel.ILN

Line 67:

Line 69:

* You get attacked by War Targets.

** Call for help in the fleet channel (Mumble would be best, but at least put something in the fleet chat channel). Let people know where you are and who is attacking you (especially how many and what ships). Any combat group of the fleet can then react and hopefully destroy the hostiles or at least chase them off so you can get out.

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

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

** 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.)

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

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

@@ Line 13: / Line 13: @@
 His hope was that the Operation: Fortress fleet would be running around the clock, each day.
+PLEASE NOTE:  The Fortress fleet is not intended to be an all-purpose fleet. For operations other than local intel and security, such as a general roam or anything else more than a few jumps away from HQ, a new fleet should be formed, and a new Mumble channel used for that operation's comms. Doing this keeps the Fortress fleet active and aligned with its purpose.
-==How to create the Operation Fortress fleet==
+==How to create the Operation: Fortress fleet==
 Each day during scheduled maintenance any existing fleet is automatically disbanded.  If you log in and search for fleets but are unable to find the Operation: Fortress in fleet finder, feel free to create one.  Please ensure that there is only one Operation: Fortress fleet running at any given time.
@@ Line 21: / Line 22: @@
 * Right click on your name in any chat window and select ''“Form fleet with . . .”'' and the fleet window opens.
 * Set up additional squads and wings, at least 2 wings with 5 squads each, although it doesn't hurt to just set up 5 wings with 5 squads each. This way there will always be enough individual squads for the separate groups.
-** Create one wing for PvE, for people that want to mine or do missions
+** Set up squads in the PvP wing(s) so they include Tackle, DD, Ewar/Logi.
-** Change squads in the PvP wing(s) to: Tackle, DD, Ewar/Logi
+** Create one wing for PvE, for people that want to mine or do missions.
-** Make sure to activate free move so people can set up their own squads as desired.
+** Make sure to enable the "free move" option so people can move themselves within the fleet.
 * Create a fleet finder advert.
@@ Line 45: / Line 46: @@
 After that please join the mumble channel for this operation, under '''Special Projects and Events'''.
+If you haven't already, be sure to read the [http://wiki.eveuniversity.org/The_Rookie%27s_Guide_To_Fleet_Ops Rookie's Guide to Fleet Ops], which covers fleet terminology, how fleets operate, fleet member discipline, and other information you'll be expected to know if you join a QRF (Quick Response Force).
 ==What to do once you are in==
@@ Line 51: / Line 54: @@
 * Check the "My Fleet" tab to see in what Wing/Squad you where placed.
-** Move yourself to squad that describes your function or action in the fleet.
+** Move yourself to a squad that describes your current function or activity. (Right-click your name and use the option "Move member".)
-   Click your name and use the option "Move menber".
 * Listen to the Fortress mumble channel and pay attention to War Target reports in fleet and LiveIntel.ILN
@@ Line 67: / Line 69: @@
 * You get attacked by War Targets.
 ** Call for help in the fleet channel (Mumble would be best, but at least put something in the fleet chat channel). Let people know where you are and who is attacking you (especially how many and what ships). Any combat group of the fleet can then react and hopefully destroy the hostiles or at least chase them off so you can get out.
+==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.
+(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.
+** 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.)
+** 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.
+* Finally, of course, enjoy any and all explosions!