Difference between revisions of "Archive:Operation: Fortress"

From EVE University Wiki
Jump to: navigation, search
m (Rayanth moved page Operation: Fortress to Archive:Operation: Fortress without leaving a redirect: Archived)
 
(17 intermediate revisions by 11 users not shown)
Line 1: Line 1:
 
+
{{Historical}}
  
 
==History==
 
==History==
Line 9: Line 9:
 
==Purpose of the operation==
 
==Purpose of the operation==
  
Korr'Tanas' stated goal was to get everyone around Aldrat (not just the Aptetter constellation, but anything within reach) into one fleet to be able to react to War Target attacks as quickly as possible and provide fewer easy targets for roaming hostiles.
+
Korr'Tanas' stated goal was to get everyone around our then-HQ Aldrat (not just the Aptetter constellation, but anything within reach) into one fleet to be able to react to War Target attacks as quickly as possible and provide fewer easy targets for roaming hostiles.
  
 
His hope was that the Operation: Fortress fleet would be running around the clock, each day.
 
His hope was that the Operation: Fortress fleet would be running around the clock, each day.
  
 +
==How an Operation: Fortress fleet was created==
  
==How to create the Operation Fortress fleet==
+
Each day during scheduled maintenance any existing fleet was automatically disbanded.  If members logged in and search for fleets but were unable to find the Operation: Fortress in fleet finder, they were encouraged to create one.  They were asked to ensure that there was only one Operation: Fortress fleet running at any given time.
  
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.
+
The actual formation of the fleet was straightforward.  
 +
* Members set up additional squads and wings, at least 2 wings with 5 squads each, although it didn't hurt to just set up 5 wings with 5 squads each. This way there would always be enough individual squads for the separate groups.
 +
** Members set up squads in the PvP wing(s) so they include Tackle, DD, Ewar/Logi.
 +
** Members created one wing for PvE, for people that want to mine or do missions.
 +
** Members made sure to enable the "free move" option so people could move themselves within the fleet.
  
The actual formation of the fleet is straightforward.  Right click on your name in any chat window and select ''“Form fleet with . . .”''.  When the fleet window opens, proceed to 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. Make sure to activate free move so people can set up their own squads as desired.
+
* The fleet advert stated:
 +
  ''Welcome To Operation Fortress
 +
  If you are new to the way the Fortress fleet works , please read in the wiki "What to do once you are in"
 +
  http://wiki.eveuniversity.org/Operation:_Fortress
 +
  Please move your self to the relevent Wing/Squad and if you have Leadership 5 Take a SC possition!
 +
  DO NOT SHARE MISSION REWARDS IN THIS FLEET THANK YOU.''
 +
 
 +
==How members joined==
  
The next step is to create a fleet finder advert.  In the Fleet window, go to the tabs labeled ''“Fleet Finder > My Advert”'' and click the bottom button labeled ''“Create Advert”''Change the fleet name to ''“Operation Fortress”'' so that it can easily be found your fellow Unistas. In the description include at minimum a link to [http://forum.eveuniversity.org/viewtopic.php?f=31&t=58485&start=0 http://forum.eveuniversity.org/viewtopic.php?f=31&t=58485&start=0] and [http://forum.eveuniversity.org/viewtopic.php?f=31&t=58427 http://forum.eveuniversity.org/viewtopic.php?f=31&t=58427], the two threads created by Director Emeritus Korr’Tanas. In the ''“Open Fleet to”'' section make sure to only allow corporation and alliance members and check ''“Hide details”''. If you need help with any of this please ask in Chat.E-Uni or Q&A.E-uni.
+
Assuming a fleet has already been created correctly members were be able to find it in the Fleet Finder.  Alternatively this fleet might have been advertised in Alliance channel (and possibly some other channels as well) with a link for members to just click on to join the fleet.
  
You do not need any ingame skills for any of this.  The [[Skills:Leadership|Leadership]] skill is solely used for the passing of fleet buffs to squad members, not the actual formation of the fleet.
+
After that members were asked to join the mumble channel for this operation, under '''Special Projects and Events'''.
  
 +
Members were requested 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 they would be expected to know if you join a QRF (Quick Response Force).
  
==How to join==
+
==What Operation: Fortress did==
  
Assuming a fleet has already been created correctly you will be able to find it in the Fleet Finder.  Click on the fleet button (''Neocom > Eve menu > Social > Fleet'') and look for the Operation: Fortress fleet. The leader should be a University pilot and the name should be 'Operation: Fortress' or something similar. Alternatively this fleet might be advertised in Alliance channel (and possibly some other channels as well) with a link you can just click on to join the fleet.
+
Whatever members wanted, within reason.  
  
After that please join the mumble channel for this operation, under '''Special Projects and Events'''.
+
* Listened to the Fortress mumble channel and paid attention to War Target reports in fleet and LiveIntel.ILN
 +
** When there was no immediate hostile threat members could conduct business as usual, and could ask in fleet if someone wanted to join in whatever they were doing, for example missions, mining. Free move was activated for this fleet, so the group could move into its own squad or wing and set up their fleet/wing/squad boosters as desired. It was encouraged that at least someone should be in a position so that they could warp the entire group off when needed. Members could use a separate mumble channel for their group and set up a separate chat channel ingame as well.
  
==What to do once you are in==
+
* If a war Target(s) was heading over to our then-HQ Aldrat (or wherever the fleet was) instructions were to:
 +
** Alert the fleet
 +
** Put the info in LiveIntel.ILN if it's not there already.
 +
** Be smart and dock up.
 +
** Optional: switch to a combat ship
 +
** Change squad, if a member switched ships, to be ready to join the rest of the combat pilots if they try to attack the War Targets.
  
Do what you want, within reason. '''Joining the Operation: Fortress fleet does not in any way supersede or invalidate the [[Wartime Standard Operating Procedures]]. Fly smart.'''
+
* If a members was attacked by War Targets instructions were to:
 +
** Call for help in the fleet channel. Any combat group of the fleet could then react and hopefully destroy the hostiles or at least chase them off so the member could get out.
  
Pay attention to War Target reports in fleet and LiveIntel.ILN and if any War Targets head over to Aldrat (or wherever you are) be smart: don't hang around in your mining ship, instead get out of harms way and dock up and maybe switch to a combat ship (keep in mind certain T1 ships can be [[Ship Replacement Program|reimbursed]] by the University if lost while PvP-ing in a combat fleet).  Be ready to join the rest of the combat pilots if they try to attack the War Targets. Do so in an organized manner only, either following the direction of a brave leader, or stepping up yourself!
+
==Proper Use of Mumble==
  
Assuming there is no immediate hostile threat you can conduct business as usual. And of course you can ask in fleet if someone wants to join you in whatever you are doing. For example you could fly with a few people and run missions together, possibly higher level mission than you could do on your own. Or you could set up some miners with some fleet boosts and mine together. Free move should be activated for this fleet, so your group can move into it’s own squad or wing and set up your fleet/wing/squad boosters as desired. Or at least have someone in such a position so that they can warp the entire group off when needed. You can use a separate mumble channel for your group and set up a separate chat channel ingame as well.
+
In Mumble under "Special Projects and Events" was 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, members were asked to adhere to the following guidelines for proper comms use:
  
If you get attacked by War Targets ask 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.
+
* The main Mumble channel "Operation: Fortress" was to remain manned at all times so fleet members (who may or may not be involved in a QRF) could benefit from local intel and security.
 +
* When a QRF was active:
 +
** Because operational security was often a concern (spies), the QRF Fleet Commander -- whoever was leading the operation at the time -- was asked 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.
 +
** Members were requested to only join the Command channel if the FC invited them
 +
** Standard fleet comms displine was observed. The FC could relax comms at his/her discretion.

Latest revision as of 05:58, 7 October 2021

E-UNI Emblem.png This page's intent is to provide information on the the history of EVE University. The information on this page is no longer current.

History

In a reaction to less-than-satisfactory performance in a series of wars against the University, Director Emeritus Korr’Tanas proposed a solution. On September 4th 2012, he created a general discussion thread titled Operation: Fortress and encouraged Ivy League members to read and participate in the discussion. Korr’Tanas’ original post included his reasons for proposing the operation, and suggestions on how to create a continuous corporation-wide fleet for everyone in the University Headquarters of Aldrat, as well as the surrounding systems. The interest of members was strong with both supporters and detractors joining in on the discussion.

The Operation: Fortress fleet was soon created in game, and over the course of only a couple of days had various encounters with War Targets - some successful others less so. On September 6th 2012, Director Emeritus Korr’Tanas created a secondary thread explaining the nuts and bolts of the Operation: Fortress fleet as not everyone would necessarily have fleet formation experience.

Purpose of the operation

Korr'Tanas' stated goal was to get everyone around our then-HQ Aldrat (not just the Aptetter constellation, but anything within reach) into one fleet to be able to react to War Target attacks as quickly as possible and provide fewer easy targets for roaming hostiles.

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

How an Operation: Fortress fleet was created

Each day during scheduled maintenance any existing fleet was automatically disbanded. If members logged in and search for fleets but were unable to find the Operation: Fortress in fleet finder, they were encouraged to create one. They were asked to ensure that there was only one Operation: Fortress fleet running at any given time.

The actual formation of the fleet was straightforward.

  • Members set up additional squads and wings, at least 2 wings with 5 squads each, although it didn't hurt to just set up 5 wings with 5 squads each. This way there would always be enough individual squads for the separate groups.
    • Members set up squads in the PvP wing(s) so they include Tackle, DD, Ewar/Logi.
    • Members created one wing for PvE, for people that want to mine or do missions.
    • Members made sure to enable the "free move" option so people could move themselves within the fleet.
  • The fleet advert stated:
  Welcome To Operation Fortress
  If you are new to the way the Fortress fleet works , please read in the wiki "What to do once you are in" 
  http://wiki.eveuniversity.org/Operation:_Fortress
  Please move your self to the relevent Wing/Squad and if you have Leadership 5 Take a SC possition!
  DO NOT SHARE MISSION REWARDS IN THIS FLEET THANK YOU.
  

How members joined

Assuming a fleet has already been created correctly members were be able to find it in the Fleet Finder. Alternatively this fleet might have been advertised in Alliance channel (and possibly some other channels as well) with a link for members to just click on to join the fleet.

After that members were asked to join the mumble channel for this operation, under Special Projects and Events.

Members were requested to read the Rookie's Guide to Fleet Ops, which covers fleet terminology, how fleets operate, fleet member discipline, and other information they would be expected to know if you join a QRF (Quick Response Force).

What Operation: Fortress did

Whatever members wanted, within reason.

  • Listened to the Fortress mumble channel and paid attention to War Target reports in fleet and LiveIntel.ILN
    • When there was no immediate hostile threat members could conduct business as usual, and could ask in fleet if someone wanted to join in whatever they were doing, for example missions, mining. Free move was activated for this fleet, so the group could move into its own squad or wing and set up their fleet/wing/squad boosters as desired. It was encouraged that at least someone should be in a position so that they could warp the entire group off when needed. Members could use a separate mumble channel for their group and set up a separate chat channel ingame as well.
  • If a war Target(s) was heading over to our then-HQ Aldrat (or wherever the fleet was) instructions were to:
    • Alert the fleet
    • Put the info in LiveIntel.ILN if it's not there already.
    • Be smart and dock up.
    • Optional: switch to a combat ship
    • Change squad, if a member switched ships, to be ready to join the rest of the combat pilots if they try to attack the War Targets.
  • If a members was attacked by War Targets instructions were to:
    • Call for help in the fleet channel. Any combat group of the fleet could then react and hopefully destroy the hostiles or at least chase them off so the member could get out.

Proper Use of Mumble

In Mumble under "Special Projects and Events" was 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, members were asked to adhere to the following guidelines for proper comms use:

  • The main Mumble channel "Operation: Fortress" was to remain manned at all times so fleet members (who may or may not be involved in a QRF) could benefit from local intel and security.
  • When a QRF was active:
    • Because operational security was often a concern (spies), the QRF Fleet Commander -- whoever was leading the operation at the time -- was asked 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.
    • Members were requested to only join the Command channel if the FC invited them
    • Standard fleet comms displine was observed. The FC could relax comms at his/her discretion.