|
|
| (96 intermediate revisions by 23 users not shown) |
| Line 1: |
Line 1: |
| {{Cleanup}} | | {{historical}} |
| | |
| [[Category:Guides]]
| |
| [[Category:PvP]]
| |
| [[Category:Ships]]
| |
| | |
| =Logistic Guide=
| |
| | |
| A basic guide for rookie logistic ship pilots.
| |
| | |
| ==Introduction==
| |
| | |
| Logistic ships in Eve Online are designed to remotely repair friendly ships. They can be used both in PvE and PvP fleets. They require a fair amount of training and thus are usually out of reach for most young combat pilots who will focus more on damage dealing ships in their early careers.
| |
| | |
| Each of the four empire factions have their own logistic ship. The Amarr have the Guardian, the Caldari have the Basilisk, the Gallente have the Oneiros, and the Minmatar have the Scimitar. The Basilisk and Scimitar have a shield transfer bonus, while the Guardian and Oneiros have an armor transfer bonus.
| |
| | |
| These ships are based on T1 cruiser hulls: the Augoror (Amarr; hit point and cap transfer bonus), the Osprey (caldari; mining and shield transfer bonus), Exequror (Gallente; cargo and armor transfer bonus), and Scythe (Minmatar; mining and tracking link bonus). This article will only discuss the proper T2 Logistics, not the T1 base hulls.
| |
| | |
| Two of the Logistic ships, the Guardian and Basilisk, have an energy transfer range and cap bonus in addition to their remote armor/shield bonus. They are most often used with four remote armor/shield modules and two energy transfer modules. A cap chain between pilots is set up to insure that all pilots give and receive cap in the chain to sustain their cap indefinitely even with all reps running.
| |
| | |
| The other two Logistics ships, the Oneiros and Scimitar, have a tracking link range and efficiency bonus in addition to their remote armor/shield bonus. Although many fittings skip the tracking links in mids for ECCM, cap modules, and/or shield tank.
| |
| | |
| ==Recommended Skills==
| |
| | |
| ===Drones===
| |
| * Drone Durability 3
| |
| * Drone Navigation 5
| |
| * Drones 5
| |
| * Electronic Warfare Drone Interfacing 3
| |
| * Repair Drone Operation 4
| |
| * Scout Drone Operation 5
| |
| | |
| ===Electronics===
| |
| | |
| * Electronic Warfare 4
| |
| * Electronics 5
| |
| * Long Range Targeting 5
| |
| * Multitasking 3
| |
| * Signature Analysis 5
| |
| * Targeting 5
| |
| | |
| ===Engineering===
| |
| | |
| * Energy Emission Systems 4
| |
| * Energy Management 5
| |
| * Energy Systems Operation 5
| |
| * Engineering 5
| |
| * Shield Emission Systems 4
| |
| * Shield Management 5
| |
| * Shield Operation 4
| |
| * Shield Upgrades 4
| |
| * Tactical Shield Manipulation 4
| |
| | |
| ===Mechanic===
| |
| | |
| * Armor Rigging 3
| |
| * EM Armor Compensation 4
| |
| * Explosive Armor Compensation 4
| |
| * Hull Upgrades 5
| |
| * Jury Rigging 3
| |
| * Kinetic Armor Compensation 4
| |
| * Mechanic 5
| |
| * Nanite Interfacing 3
| |
| * Nanite Operation 3
| |
| * Remote Armor Repair Systems 4
| |
| * Remote Hull Repair Systems 3
| |
| * Repair Systems 2
| |
| * Shield Rigging 3
| |
| * Thermic Armor Compensation 4
| |
| | |
| ===Navigation===
| |
| | |
| * Acceleration Control 4
| |
| * Afterburner 4
| |
| * Evasive Maneuvering 4
| |
| * Fuel Conservation 4
| |
| * High Speed Maneuvering 4
| |
| * Navigation 4
| |
| * Warp Drive Operation 4
| |
| | |
| ===Science===
| |
| | |
| * Biology 3
| |
| * Science 4
| |
| * Thermodynamics 4
| |
| | |
| ===Spaceship Command===
| |
| | |
| * Amarr Cruiser 5
| |
| * Caldari Cruiser 5
| |
| * Gallente Cruiser 5
| |
| * Logistics 4/5
| |
| * Minmatar Cruiser 5
| |
| * Spaceship Command 4
| |
| | |
| Logistics 4 is the minimum you should be flying a logistic ship with. But you should train it up to 5 as soon as possible if you want to fly logistic ships regularly.
| |
| | |
| ==Fittings==
| |
| | |
| ===Basilisk===
| |
| | |
| ===Guardian===
| |
| | |
| ===Oneiros===
| |
| | |
| ===Scimitar===
| |
| | |
| ===Module & Rig Selection===
| |
| | |
| * AB vs. MWD
| |
| * ECCM
| |
| * Cap Modules
| |
| * Tanking
| |
| * Remote Shield and Armor Transfer
| |
| * Energy Transfer
| |
| * Tracking Links
| |
| * Rigs
| |
| | |
| ==Logi Channel==
| |
| | |
| Once you've joined a fleet, ask for the logi channel. The logi channel is used to give information to logi pilots they may require.
| |
| | |
| Hopefully the logi channel has a Logistic Coordinator that will tell all logi pilots what they need to know. Some fleets will not have a designated logi coordinator. In this case, hopefully one of the experienced logi pilots will step up to guide the rookies.
| |
| | |
| The logi channel can be used for the following information:
| |
| * Who is the logi anchor (if different than the rest of the fleet's anchor), and orbit range.
| |
| * Who should be on the watch list.
| |
| * Provide warp-ins for logi pilots that have just joined fleet, or missed warps, etc.
| |
| * How the cap chain should be set up.
| |
| * Where you should be aligned (prop mod on or off, full speed or 3/4 speed).
| |
| * Current orders. Sometimes the logis should follow different orders from the rest of the fleet.
| |
| * Catch the attention of logi pilots not doing what they should be doing. Linking their name by drag-and-drop from the channel list can help. If they still don't respond, do the same in the fleet channel and remind them to read logi chat.
| |
| | |
| The cap chain can be sorted either through the logi channel member list or through the overview. The cap chain is usually set up to be two down, or one up one down. If your corp, alliance, or coalition does not have a fixed rule for this, you should always ask in the logi channel which sorting and cap chain methods are being used.
| |
| | |
| Channels are sometimes bugged and you will appear to be in the channel but will not be able to see what anyone else types. If you don't see anyone else typing in the logi channel, ask if anyone can read what you type, then rejoin the channel if no one responds. This is sometimes a persistent bug that requires leaving and re-joining the channel several times to fix.
| |
| | |
| ==Watch List==
| |
| | |
| The FC or Logi Coordinator will sometimes tell you who you should have on your watch list. Sometimes he won't if he's too busy. If you are in a guardian or basilisk, you should have the people you should be cap transferring on your watch list at least. If you're in a small gang, you may want all the other logi pilots on your watch list.
| |
| | |
| Other ships that you may want to have on watch list: The fleet commander (both the actual FC and the person holding FC position if they aren't the same), wing commanders, the fleet booster, recon tacklers (huginn, rapier, lachesis, arazu) and sometimes T3 recon configured Proteus and Loki, some ECM ships such as scorpions.
| |
| | |
| Ask in the logi channel who you should have on your watch list. You can add people to your watch list by right clicking their name in a chat channel or the overview, and going through the menu: Fleet > Add to watch list. Or through the fleet member list in the fleet window, right click a name > add to watch list.
| |
| | |
| Fleet members taking damage will blink red in your watch list. You can instantly lock them by control-clicking their name in the watch list.
| |
|
| |
|
| ==Overview== | | ==Overview== |
| Line 177: |
Line 32: |
| # Save the preset as '''9B - Blue Logi''' | | # Save the preset as '''9B - Blue Logi''' |
|
| |
|
| This '''Blue Logi''' overview preset will show all blue logistic ships on grid, not just those in your fleet. It is not possible to set up an overview preset that would only shows fleeted logi pilots. | | This '''Blue Logi''' overview preset will show all blue logistic ships on grid, not just those in your fleet. It is not possible to set up an overview preset that would only shows fleeted logi pilots. However this only shows T2 logi, not T1. |
|
| |
|
| ===Blue Caps=== | | ===Blue Caps=== |
| Line 194: |
Line 49: |
| # Save the preset as '''9C - Blue Caps''' | | # Save the preset as '''9C - Blue Caps''' |
|
| |
|
| ==Cap Transfer==
| |
|
| |
| The cap chain helps keep Guardians and Basilisks cap stable. Pilots with sufficient skills will generate cap in the chain, since the energy transfer modules will require less cap to activate than it will transfer to the target.
| |
|
| |
| If you are in an Oneiros or Scimitar, you should not be depending on cap transfers. These ships are usually set up to be cap stable on their own at the cost of less repping power, or sometimes using cap boosters to maintain more reps for a limited amount of time.
| |
|
| |
| If you are in a Guardian or Basilisk, you should be cap stable when receiving two cap transfers if you have the skill Logistics 4, and one cap transfer of you have Logistics 5. Each logi pilot should transfer cap to two other logi pilots, even if those who receive cap have logi 5. This insures redundancy in combat situations where the cap chain is often broken when ships are neuted, ECM jammed, or destroyed. Some fleets that have all logi pilots with Logistics 5 and veteran logi pilots that are good at multitasking will only transfer to one other logi pilot in the chain and will take cap requests during combat.
| |
|
| |
|
| ===Cap Direction=== | | ===Cap Direction=== |
| Line 220: |
Line 68: |
| If the overview is used to order the cap chain, you should sort the Blue Logi overview by name. You should look for the two pilots that you are meant to cap according to the cap direction rule, and activate one cap transfer module on each. You must skip over Scimitars and Oneiros, you should never give cap to these ships in normal circumstances. Pay attention to ship type in the overview when setting up your cap chain list. | | If the overview is used to order the cap chain, you should sort the Blue Logi overview by name. You should look for the two pilots that you are meant to cap according to the cap direction rule, and activate one cap transfer module on each. You must skip over Scimitars and Oneiros, you should never give cap to these ships in normal circumstances. Pay attention to ship type in the overview when setting up your cap chain list. |
|
| |
|
| If you use the overview to determine sorting order, the logi channel will include non-cap transferring logi, sometimes the FC and other commanders, pilots that have had their ships destroyed, pilots that are off grid, pilots that are in another system, etc. This can help to use the logi channel to coordinate between all logi pilots and commanders. | | If you use the overview to determine sorting order, the logi channel may include non-cap transferring logi, sometimes the FC and other commanders, pilots that have had their ships destroyed, pilots that are off grid, pilots that are in another system, etc. This can help to use the logi channel to coordinate between all logi pilots and commanders. |
|
| |
|
| ===Cap Transfer Protocol=== | | ===Cap Transfer Protocol=== |
| Line 230: |
Line 78: |
| ==Anchor== | | ==Anchor== |
|
| |
|
| The Anchor is the ship you should be orbiting. You default orbit distance should be between 5 and 15 km. At 5 km orbit distance you may not have your full speed while orbiting. 10 km orbit is a common distance that will let you orbit at full speed. If your orbit distance is too far you may have a low angular velocity against the enemy fleet for a prolonged time, or you could be out of range of some broadcast requests if a fleet spreads out to chase an enemy or deblob to avoid bombing runs, or you could run into an enemy shield during a pos siege if the anchor is too close. | | The Anchor is the ship you should be orbiting. You default orbit distance should be between 5 and 15 km in PvP fleets. Scimitars and Oneiros will sometimes not have an anchor and just try to keep at range from the hostiles while staying in rep range of each other and their fleetmates. In Incursion fleets, the orbit is often less than 5 km to prevent rats from orbiting too far from the damage dealers if they aggress the logi. |
| | |
| | At 5 km orbit distance you may not have your full speed while orbiting with an AB. 10 km orbit is a common distance that will let you orbit at full speed. If your orbit distance is too far you may have a low angular velocity against the enemy fleet for a prolonged time, or you could be out of range of some broadcast requests if a fleet spreads out to chase an enemy or deblob to avoid bombing runs, or you could bump into a hostile starbase shield during a pos siege if the anchor is too close. |
|
| |
|
| If you fight on a stargate, the anchor could be set as the stargate with an orbit that stays within jump range. Logi ships that take too much damage and cannot get repped fast enough can jump through if they don't have aggression. | | If you fight on a stargate, the anchor could be set as the stargate with an orbit that stays within jump range. Logi ships that take too much damage and cannot get repped fast enough can jump through if they don't have aggression. |
| Line 246: |
Line 96: |
| * Target: You should have this unchecked unless target broadcasts are being used to focus repping on a starbase. | | * Target: You should have this unchecked unless target broadcasts are being used to focus repping on a starbase. |
|
| |
|
| You should ignore all capacitor requests unless the fleet is not engaging an enemy fleet nor attacking a hot POS. If cap requests have been authorized by the FC or logi coordinator, you should switch cap transfer to one down, and use the second cap transfer module to cap up ships that have broadcast for cap. The pilots broadcasting for cap should type '''CF''' (for Cap Full) in fleet chat to indicate they no longer need cap. If a pilot fails to type CF after 2 to 5 cycles (this will depend on the number of cap transferring logistic ships in the fleet), you should unlock him and move on to the next broadcast in queue. | | You should ignore all capacitor requests unless the fleet is not engaging an enemy fleet nor attacking a hot POS. If cap requests have been authorized by the FC or logi coordinator, you should switch cap transfer to one down, and use the second cap transfer module to cap up ships that have broadcast for cap. The pilots broadcasting for cap should type '''CF''' (for Cap Full) in fleet chat to indicate they no longer need cap, or use the 'in position' broadcast, depending on how the fleet usually handles this. If a pilot fails to indicate full cap after 2 to 5 cycles (this will depend on the number of cap transferring logistic ships in the fleet), you should unlock him and move on to the next broadcast in queue. |
| | |
| ==Boosters==
| |
| | |
| * '''Standard X-Instinct''': This booster will reduce signature radius and should be used if you are being shot to mitigate damage.
| |
| | |
| For Highsec empire inhabitants, the '''Synth X-Instinct Booster''' can be used instead.
| |
|
| |
|
| ==Drone Selection== | | ==Drone Selection== |
|
| |
|
| Maintenance bots should be prioritized over other drones. Many battles will happen outside of drone control range, the logistic ships get a bonus to drone repping, and in many fights logistic pilots will be too busy with repping to manage offensive drones separately from reps.
| | Logistic ships get a bonus to drone repping, so these drones are sometimes preferred. Some battles will happen outside of drone control range, and in many fights logistic pilots will be too busy with repping to manage offensive drones separately from reps. Logistic drones will not give aggression, contrary to EW and combat drones. Aggression will prevent jumping through a stargate or docking in a station for 1 minute. |
|
| |
|
| * Armor Maintenance Bot: Guardians can hold five light armor maintenance bots, Oneiros can hold five medium armor mainenance bots. | | * Armor Maintenance Bot: Guardians can hold five light armor maintenance bots, Oneiros can hold five medium armor mainenance bots. |
| Line 266: |
Line 110: |
| * Warrior: Warriors are the light scout drones of choice for their speed and damage type which is good against T1 armor tankers and many T2 ships that have enhanced resists. These can be especially useful against light ships, such as interdictors and various tacklers, that come withing drone control range. | | * Warrior: Warriors are the light scout drones of choice for their speed and damage type which is good against T1 armor tankers and many T2 ships that have enhanced resists. These can be especially useful against light ships, such as interdictors and various tacklers, that come withing drone control range. |
|
| |
|
| ==Positioning & Range Control== | | ===Video=== |
| | |
| [...]
| |
| | |
| ==Heavy Interdictors==
| |
| | |
| [...]
| |
| | |
| ==Capital Ships==
| |
|
| |
|
| [...] | | * [https://youtu.be/j4hPTGN3Q6w?list=PLo1eELyNWdOXizh7sJac6z2ldzMqPwXoC Ironclad] - A Rooks and Kings video detailing logistic and triage carrier tactics. |
|
| |
|
| ==Related Links==
| |
|
| |
| ===UniWiki===
| |
|
| |
| * [[Logistics Ships 101]] - Class Curriculum
| |
| * [[Overview Guide]]
| |
|
| |
| ===Video===
| |
|
| |
|
| * [http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1342627 Ironclad] - A Rooks and Kings video detailing logistic and triage carrier tactics.
| | ===Other=== |
|
| |
|
| * [http://www.eveonline.com/ingameboard.asp?a=topic&threadID=1288092 Double Edged] - A Pandemic Legion video in two parts with logistic footage. | | * [http://www.evealtruist.com/2011/10/know-your-enemy-logistics.html Know Your Enemy - Logistics] - Article on The Altruist blog by Azual Skoll. |
