Anatomy of Incursions: Difference between revisions

{{Incursions links}}

{{#css:

.bars { height:8px; }

.text { padding-left:4px; padding-right:4px; text-align:left; }

.c4 { background-color:#51D200; } .cc4 { color:#51D200; }

/* Green - red (dark). */

/* Blue-purple (dark). */

}}

This article is not intended to be a step-by-step manual on how to lead an incursion fleet, but rather an article bringing up all the various aspects of running a site. To make sure you are aware of all the choices you'll need to be making and how they are influenced by what site you're doing, how your fleet members have fitted their ships, the skills they have and to what level of autonomy you can rely on them to perform without specific orders.

= Commanding a fleet =

Firstly, simply remember that EVE is a game where {{co|wheat|''"It depends!"''}} is the single most important thing to remember. Don't blindly follow set tactics or kill-orders you've read here or somewhere else. Put things into perspective and ''adjust to what's happening'': different site mechanics, the spawning of enemies, as well as your current fleet composition. This is a good example of where the ''"why"'' (reasoning and ability to put things into context) is more important than the ''"how"'' or ''"what"'' (rigid kill-order lists etc.). This is because knowing the ''"why"'' allows you to tackle anything the game throws at you, whereas only knowing the ''"how"'' or ''"what"'' will catch you off-guard whenever something out of order happens.

==== [[image:icon_stasis_webifier_i.png|32px|link=]] Ensure that you have enough webs ====

There are a lot of factors to consider, but before that, see this table:

|-

| <div class="wraps">

<div class="wrap"><div class="text">[[image:Icon ISIS Stasiswebifying.png|14px|link=]] x 4</div><div class="bars d1" style="width:198px;"></div><div class="text">99,21%</div></div>

</div>

|-

| <div class="wraps">

<div class="wrap"><div class="text">[[image:Icon ISIS Stasiswebifying.png|14px|link=]] x 4</div><div class="bars d1" style="width:196px;"></div><div class="text">97,99%</div></div>

</div>

|-

| <div class="wraps">

<div class="wrap"><div class="text">[[image:Icon ISIS Stasiswebifying.png|14px|link=]] x 4</div><div class="bars d1" style="width:179px;"></div><div class="text">89,55%</div></div>

<div class="wrap"><div class="text">[[image:Icon ISIS Stasiswebifying.png|14px|link=]] x 3</div><div class="bars d2" style="width:175px;"></div><div class="text">87,41%</div></div>

<div class="wrap"><div class="text">[[image:Icon ISIS Stasiswebifying.png|14px|link=]] x 1</div><div class="bars d4" style="width:120px;"></div><div class="text">60,00%</div></div>

</div>

</div>

|-

| <div class="wraps">

<div class="wrap"><div class="text">[[image:Icon ISIS Stasiswebifying.png|14px|link=]] x 4</div><div class="bars d1" style="width:173px;"></div><div class="text">86,39%</div></div>

|}

<small><references/></small>

As you can see, a single bonused web from a [[Vindicator]] is worth more than four normal webs and it's simply impossible to reach the effect of two bonused webs with normal webs due to [[stacking penalties]].

On top of that, some of our pilots fly with communities who use '''ascendancy implants''' and '''hyperspatial rigs''' increasing their warp speeds above and beyond the speed of logistics. Keep that in mind and have logistics align with the rest of the fleet if that is the case, so they don't arrive too late on grid.

|-

<div class="wrap"><div class="bars d4" style="width:250px;"></div><div class="bars d3" style="width:70px; border-left:1px solid black;"></div><div class="bars d2" style="width:90px; border-left:1px solid black;"></div><div class="text">25s (7-16s align)</div></div>

</div>

|-

<div class="wrap"><div class="bars d4" style="width:250px;"></div><div class="bars d3" style="width:70px; border-left:1px solid black;"></div><div class="bars d2" style="width:90px; border-left:1px solid black;"></div><div class="text">25s (7-16s align)</div></div>

</div>

|-

<div class="wrap"><div class="bars d4" style="width:190px;"></div><div class="bars d3" style="width:90px; border-left:1px solid black;"></div><div class="bars d2" style="width:20px; border-left:1px solid black;"></div><div class="text">19s (9-11s align)</div></div>

</div>

|-

<div class="wrap"><div class="bars d4" style="width:170px;"></div><div class="bars d3" style="width:60px; border-left:1px solid black;"></div><div class="bars d2" style="width:10px; border-left:1px solid black;"></div><div class="text">17s (6-7s align)</div></div>

</div>

|-

<div class="wrap"><div class="bars d4" style="width:160px;"></div><div class="bars d3" style="width:60px; border-left:1px solid black;"></div><div class="bars d2" style="width:10px; border-left:1px solid black;"></div><div class="text">16s (6-7s align)</div></div>

</div>

|-

<div class="wrap"><div class="bars d4" style="width:70px;"></div><div class="bars d3" style="width:40px; border-left:1px solid black;"></div><div class="bars d2" style="width:20px; border-left:1px solid black;"></div><div class="text">7s (4-6s align)</div></div>

</div>

Below is a table comparing the various means of repairing other ships, to give you a general idea of their potency. As you can see, the difference between various flights of drones can be quite big, which is why being aware of the fleet composition is so important.

|-

| rowspan="2" | [[image:icon_shield_transporter_i.png|40px|Large Remote Shield Boosters]]

| Large Remote Shield Booster II

</div>

|-

| Large S95a Remote Shield Booster

</div>

|-

| rowspan="9" | [[image:icon_drone_bandwidth.png|40px|Shield Maintenance Bots]]

| 5 x Heavy Shield Maintenance Bot II

|-

| 5 x Heavy Shield Maintenance Bot I

|-

| 4 x Heavy Shield Maintenance Bot II<small>&nbsp;<ref>Standard setup for a [[Vindicator]] in the [[EVE University Incursion Community]] is to use 5 light damage drones 4 heavy shield maintenance bots.</ref></small>

|-

| 4 x Heavy Shield Maintenance Bot I

|-

| 5 x Medium Shield Maintenance Bot II

|-

| 4 x Medium + 1 x Light Shield Maintenance Bot II<small>&nbsp;<ref>Standard setup for a [[Scimitar]] in the [[EVE University Incursion Community]] is to use 4 medium and 1 light shield maintenance bot and they get a bonus to drone repair amount.</ref></small>

|-

| 5 x Medium Shield Maintenance Bot I

|-

| 5 x Light Shield Maintenance Bot II<small>&nbsp;<ref>Standard setup for a [[Basilisk]] in the [[EVE University Incursion Community]] is to use 5 light shield maintenance bot and they get a bonus to drone repair amount.</ref></small>

|-

| 5 x Light Shield Maintenance Bot I

|}

<small>&nbsp;&nbsp;&nbsp;&nbsp;Legend: &nbsp;<font class="ee4">&#9608;</font> Base repair amount &nbsp;<font class="ee3">&#9608;</font> Ship bonuses &nbsp;<font class="ee2">&#9608;</font> Shield Command Burst bonus

In the [[EVE University Incursion Community]] we set the bar fairly high for ongrid boosters, requiring them to have the following links and implant:

|-

|}

Below are some practical effects of having a maxed booster with the appropriate mindlink implant:

|-

[[image:icon_resists.png|24px|link=]] +22,50% increased resists<small>&nbsp;<ref>While the shield command burst has a max value of +22,50% and is a set value, the practical effect normally varies depending on how many modules the recipient of the link has that effects resists (like hardeners, amplifiers and resist rigs). See [[stacking penalties]] for more information</ref></small><br>

[[image:Icon_ship_sig.png|24px|link=]] -16,88% signature radius<br>

[[image:icon_shield_transporter_i.png|24px|link=]] -22,50% cycle time on remote shield boosters<small>&nbsp;<ref>The 22,50% reduction to cycle time translated into a +29,03% increase in practical repping power.</ref></small>

[[image:icon_stasis_webifier_i.png|24px|link=]] +33,75% web range<br>

[[image:Icon_inertia.png|24px|link=]] -16,88% inertia (faster align)

[[image:Icon_shield.png|24px|link=]] +22,50% shield hit points<br>

[[image:Icon_target_range.png|24px|link=]] +48,52% Targeting Range<br>

|}

<small><references/></small>

These bonuses might not seem that impressive if you're looking at them one by one, but they are very powerful when combined.

Give people enough commands to know what to do and hit the ground running when they land on grid, but avoid overdoing it. No need to add commands for the entire wave right away, get people started, then amend target calls with secondary or tertiary targets once people have started shooting. The key is to give them enough targets to fill up their pre-locks, so they have secondary targets locked already when the primary goes down.

== Stay calm ==

People who get nervous or worked up tend to miss details or end up with butterfingers doing what they shouldn't be doing. This is true for everyone and the fleet commander sets the tone for most of this. Don't make rash, split-second decisions. Instead, take that extra second or two and consider your options, in the end that will serve you better. It is important to make a decision that you believe is best for the safety and well being of the fleet, don't worry about maybes or what-ifs, use the information available to you to act and give commands to the best of your abilities that you think will keep the fleet safe. The longer you wait, the higher the chance someone will panic and do something stupid, potentially risking the entire fleet.

== Removing jammers ==

The following ships have target jamming capabilities:

|-

| A weak frigate with low signature and no offensive capabilities (also neuts).

|-

| A weak frigate with low signature and no offensive capabilities (also neuts).

|-

| A sturdy cruiser with minor medium range damage capabilities.

|}

It is usually safer to commit the entire fleet to taking care of jammers, one by one in order, to minimize the time any of your fleet members are jammed. Sometimes it is necessary due to repairs, like in [[Override Transfer Array]]s when the logistics tower isn't hacked. Other times, like in assault sites where you have more people in your fleet, you can send the dronebunny alone to take care of the Niarjas, while the rest of the fleet focuses on the larger Arnons. If you do decide to split your fleet's damage like that and have only a single person like the dronebunny go after one of the jammers, be prepared to change plans if he or she ends up being jammed. A common strategy is to have secondary "dronebunny", without any assisted drones, that will target the jamming ships but only engage them if the primary dronebunny is jammed.

== Handling neuting threats ==

Below are the ships capable of neuting:

|-

| A weak frigate with low signature and no offensive capabilities (also jams).

|-

| A weak frigate with low signature and no offensive capabilities (also jams).

|-

| A sturdy battleship with medium range damage capabilities (also warp disrupts and webs).

|-

| A sturdy torpedo battleship with high damage but poor damage application (also warp disrupts and target paints).

|}

Both the Niarja and the Orkashu Myelen shouldn't live long enough to get within range of neuting you because they are also target jammers. But it is important to know that if you can't remove them quickly enough, they will start neuting in addition to jamming, which is bad.

The following ships make up for the majority of the damage:

{| class="wikitable" style="font-size:90%;"

|-

| A sturdy torpedo battleship with high damage but poor damage application to non-battleships (also warp disrupts, neuts and target paints).

|-

| A strong fighter bomber with high damage and {{co|crimson|perfect application}}<small>&nbsp;<ref>The '''Lirsautton Parichaya''' has bonuses that removes any reduction from '''explosive radius''' and '''explosive velcoity''', meaning resists are the only thing mitigating damage from them.</ref></small> to all ships.

|-

| A torpedo frigate with low signature and very high damage but poor application to non-battleships (also warp disrupts).

|-

| A close orbiting cruiser with short range and excellent damage application (also warp disrupts and webs).

|-

| A torpedo frigate with low signature and decent damage but poor application to non-battleships (also warp disrupts).

|-

| A sturdy torpedo battleship with high damage but poor application to non-battleships (also warp disrupts, neuts and target paints).

|-

| A sturdy battleship with good range that stays at mid-range.

|-

| A sturdy cruiser with medium range and excellent damage application.

|}

The following would apply to sniper targets:

{| class="wikitable" style="font-size:90%;"

|-

| A battleship with long range and high damage but poor tracking.

|-

| A sturdy cruisers with long range and moderate damage but relatively poor tracking.

|}

<small><references/></small>

How much damage a certain ship puts out in comparison to their resists and buffer as well as how easy they are to hit, is what matters if your goal is to reduce the incoming damage as fast as possible. Ships with a high amount of damage but weak tanks are commonly referred to as ''"glass cannons"''' in EVE and for minimum effort you remove a lot of damage from the grid by focusing on them first.

== Overcoming enemy logistics support ==

The following ships have fleet supporting capabilities:

|-

| A sturdy battleship logistics with decent damage capabilities and minor reps.

|-

| A logistics cruiser with low signature and no damage capabilities but with strong reps.

|-

| The Sansha flagship, spawns in the [[Uroborus]] and [[The Kundalini Manifest]] mothership sites (also neuts and ECM bursts).

|-

| A sturdy command ship with no damage capabilities.

|}

Depending on the fleet composition and fitting doctrine, sometimes removing webbers can be a high priority. The ships that web are:

{| class="wikitable" style="font-size:90%;"

|-

| A close orbiting cruiser with short range and excellent damage application (also warp disrupts).

|-

| A sturdy frigate with high speed and low signature that is very hard to hit due (also warp disrupts).

|-

| A sturdy frigate with low signature that is hard to hit.

|-

| A weak frigate that is otherwise similar to the '''Renyns'''.

|-

| A sturdy battleship with medium range damage capabilities (also warp disrupts and neuts).

|}

The Schmaeels and Renyns have a webbing range of 15km while the others frigates have a standard range of 10km. The Outuni has a webbing range of 20km but is often killed long before that due to its longer neut range.

== Facilitating a controlled warp-out ==

Sometimes things go wrong, like a logistics ship disconnecting, and you get overwhelmed on a site and need to get the fleet out. In order to safely warp a fleet out of a site you need everyone pre-aligned and all warp disrupting capable ships on grid destroyed. The ships capable of warp disrupting are:

|-

| A sturdy torpedo battleship with high damage but poor damage application (also neuts and target paints).

|-

| A torpedo frigate with low signature and very high damage but poor damage application

|-

| A sturdy frigate with high speed and low signature that is very hard to hit due (also webs).

|-

| A torpedo frigate with low signature and decent damage but poor damage application

|-

| A close orbiting cruiser with short range and excellent damage application (also webs).

|-

| A sturdy torpedo battleship with high damage but poor damage application (also neuts and target paints).

|-

| A sturdy battleship with medium range damage capabilities (also neuts and webs).

|}

<small><references/></small>

It is important to take your fleet composition into consideration when a logistics pilot disconnects or they all get jammed and you're left with no remote repairs. Most fleets with a proper setup including remote capacitor transmitters (formerly energy transfers), remote shield boosters (formerly shield transporters), shield maintenance bots and calm pilots can usually remove enough damage from the field to hold down the fort until the logistics pilot reconnects. Starting to align can in fact be a bad choice in some circumstances (since it reduces your tracking), so take a second to get confirmation on warp disrupts (who's warp disrupted and by whom) while making a judgement call if you can handle the incoming damage or not. If you do start aligning, remind the logistics to turn their afterburners off so they don't run out of range and keep an eye on the fleet if you end up staying aligned for longer periods of time.

== Utilizing drones ==

Drones can be a tremendous asset on the field, with a damage potential anywhere from 500 up to 900+ dps from light combat drones alone in vanguards. But you need to use them wisely or end up wasting their potential.

==== [[image:icon_bounty.png|32px|Drone target]] Drone targets ====

In a less skilled fleet consisting of regular tech one ships the frigates present a noticeable problem. To remedy the problem we utilize the dronebunny to effectively handle the fast, small signature, tight orbiting frigates. Drones can even dispose of unwebbed frigates, although they should always be complemented with a web or two to speed things up.

== Overheating defensive modules and remote shield boosters ==

Overheating a '''Multispectrum Shield Hardener II''' module will increase its efficiency by 20% allowing you to push your resists up by a few percent, easily giving you a 10% reduction to incoming damage. An overheated '''Large Remote Shield Booster II''' module will lower the duration of the module by 15% giving them more than 17% more effective repairs. The combined effect of the two will usually buy you enough time to resolve the situation and get things under control again.  This can be an even more effective strategy when a capsuleer is using a [[Strategic Cruiser]] as they are bonused to reduce module heat damage taken, with high enough skills you can overheat a module for prolonged periods without causing too much damage.

= Advanced tactics =

Whatever you decide to do, remember to do it in a controlled manner. Don't throw caution to the wind just because you have another fleet at the gate.

[[Category:Incursions]]