Anatomy of Incursions: Difference between revisions

Without knowing these things you can't really make a good decision on how to tackle a site, because you'll need to put that into the context of the site you're doing and the challenges in it. The differences in spawns can make certain tactics very viable, or next to useless.

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

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

|-

| rowspan="2" align="center" valign="middle" | '''[[Vindicator]]'''<small>&nbsp;<ref>Other [[Serpentis]] ships have '''bonuses to web strength''' (+10% per level up to +50% stronger). The same goes for the [[Daredevil]], the [[Vigilant]], the [[Vehement]] and the [[Vanquisher]], but they are not commonly seen in incursions.</ref></small><br>{{co|grey|(bonused hull)}}

| <div class="wraps">

</div>

| <div class="wraps" style="text-align:right;">

</div>

|-

| <div class="wraps">

</div>

| <div class="wraps" style="text-align:right;">

</div>

|-

| rowspan="2" align="center" valign="middle" | '''Other ships'''<br>{{co|grey|(unbonused)}}

| <div class="wraps">

</div>

| <div class="wraps" style="text-align:right;">

</div>

|-

| <div class="wraps">

</div>

| <div class="wraps" style="text-align:right;">

</div>

|}

For [[Incursion_sites#Headquarter_sites|headquarters]], especially for fleets using webbing tactics to hold down ships where they spawn, it all boils down to having enough webs to get the job done. Depending on how their ships are fit, they usually have room for one or two webs. Obviously, the more webs per brawler the better, but you'd want at least 15 vindicator webs to ensure that you can web the spawns down into a convenient kill box.

In vanguards there will be a lot of small ships that orbit close, with only a few larger ships and they all spawn well within 70 - 75 km. The major engagement ranges for these kind of sites are of the 15 - 25 km range and the odd 60 - 65 km range for the '''Mara Paleo'''. For assaults and headquarters there will be fewer small ships and more large ships that initially spawn much further out. The engagement range for these sites vary a bit more, with brawlers engaging anywhere from 0 - 15 km and the rest at 20 - 25 km, 35 - 45km and 60+ km.   

Regardless of what type of site you'll be running, you'll need to ensure that you can handle both ships that orbit close and ships that orbit further out. In vanguards the emphasis is much higher on tracking and webs to deal with the myriad of small agile frigates, whereas for assaults and headquarters the emphasis is on projection.

! style="padding:5px;background-color:#222222; text-align:left" | Warp speed (including align time)

|-

| style="padding:0px;" | <div class="wraps">

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

|-

| style="padding:0px;" | <div class="wraps">

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

|-

| style="padding:0px;" | <div class="wraps">

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

|-

| style="padding:0px;" | <div class="wraps">

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

|-

| style="padding:0px;" | <div class="wraps">

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

|-

| style="padding:0px;" | <div class="wraps">

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

Similarly, if you're using a hacking frigate for sites like the [[Override Transfer Array]], the frigate would in turn take the gate from a stand-still as the logistics disappear off grid. Then they'd land inside the pocket after most of the Eysturs have already spawned.

It's important to know how much of your repair capabilities are tied up into each ship. That way you'll be able to quickly gauge whether you have enough support left to handle the incoming damage if one of your logistics disconnects.

<references/></small>

Using ongrid boosters is pretty much a given in any community that run incursions. A vanguard fleet with 2 logistics and an ongrid booster performs much better than a fleet with 3 logistics and no booster, simply from a defensive standpoint. Add to that the secondary benefits from skirmish and possibly even information links.

| valign="top" |

[[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>

| valign="top" |

| valign="top" |

|}

<small><references/></small>

Apart from the very tangible increase of repping powers and web range, the other bonuses all help to improve your ''"quality of life"'' making site running both safer and faster.

{{important note box|Running without boosts is '''not''' recommended as you lose a considerable amount of buffer and safety. That said, it is doable for vanguards if you understand and compensate for the weaker position your fleet will be in.}}

If you choose to run [[Incursion sites#Vanguard sites|vanguard sites]] without boosts, you'll need to keep in mind and compensate for not having the boosts listed above. Practically this means that you need to adjust your approach to site running.

| style="background:#222222;text-align:center;" | '''Description''' (see [[Sansha's Manual]] for more details)

|-

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

|}

| style="background:#222222;text-align:center;" | '''Description''' (see [[Sansha's Manual]] for more details)

|-

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

|}

| style="background:#222222;text-align:center;" | '''Description''' (see [[Sansha's Manual]] for more details)

|-

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

|}

! style="background:#222222;" | Description

|-

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

|-

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

|}

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

|}

| style="background:#222222;text-align:center;" | '''Description''' (see [[Sansha's Manual]] for more details)

|-

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

|}

| style="background:#222222;text-align:center;" | '''Description''' (see [[Sansha's Manual]] for more details)

|-

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

|}

One thing to remember about drones is that they have very short optimals and you also need to factor in travel time. You want them to spend more time shooting and less time moving. As such, there's no ''one way'' to use drones, but instead highly situational. See [[#Bonused_webs_and_flexible_dronebunny|bonused webs]] under '''Advanced tactics''' below for more information.

{{note box|The way the [[EVE University Incursion Community]] run their [[Roles_in_Incursions#Ongrid_booster|ongrid booster]] it makes for a good choice of dronebunny.}}

The first thing to remember is that the dronebunny is first and foremost a damage dealer, dronebunny second. You should never compromise your primary function of dealing damage in an attempt to be a better dronebunny. You select a dronebunny from the fleet members based on who could direct the drones with the least amount of interference or hindrance, while simultaneously making the most use of the drones.

Try to make the most out of your webs and target painters in the fleet. See the [[#Ensure that you have enough webs|bonused webs and stacking]] section above for more information.

First of all, remember that not everyone will be able to web everything. When you enter a vanguard site for example, you'll all land anywhere within a radius of roughly 4,000 meters from the beacon. This means that you can be up to 8,000 meters away from some of your fleet members. If a Sansha orbits someone that far out, they'll be +/- 8km away, potentially orbiting in and out of web range depending on their preferred orbit distance. This is why we focus so heavily on webs for vanguards, to ensure that we have enough webs available for any given target.

If you have long-webbed [[Loki]]s and [[Bhaalgorn]]s, make sure they aren't webbing things too far out. Always adjust the range of which you web things down to your fleet's damage projection capabilities. There's no point webbing things at 40km if more than half your fleet is unable to hit things for any kind of damage at that range.

The same goes for target painters, although they are harder to manage as you wouldn't immediately be able to tell how many painters are on your target, like you do with webs and velocity. Normally you don't have too many target painters for that to be a problem and a good mix of both webs and target painters often gives you better applied damage than simply piling on more and more webs.

While there are some standard target orders and priorities, there's often room for improvement based on a number of variables.

The individual skills of the pilots in your fleet can range from low skilled to high skilled, their ships from tech one to pirate faction battleships, their modules from meta 4 to tech 2, faction, deadspace or even officer modules. Ships can fit for short or long range, people can be more or less experienced and more or less attentive to your sudden commands etc.

Large guns have an easier time hitting battlecruisers and battleships than they have hitting close orbiting frigates and cruisers. While webs often cancel this effect, there's still room for micromanaging your fleet to keep people shooting targets they can apply the most damage to. The need for this increases with the number of ships in your fleet, so as not to waste damage potential.

Whenever targets spawn at range, there's a window of opportunity for any fleet with ships able to lock fast and shoot at a distance. While on approach, enemies come in at a low angular velocity with their microwarpdrive turned on and thus much easier to hit compared to when they slow down and start orbiting under your guns. Given enough scan resolution, good enough range and tracking, even battleships can pick off smaller ships as they come rushing towards you. Most tech one battleships have no real means of doing this, but faction battleships and strategic cruisers are usually more than capable of finishing off a few frigates before they even get close.

Some sites will have targets that you don't necessarily need to kill to finish the site. Sometimes they can be ignored completely, like in the case of the '''Eystur Rhomben''' in [[Override Transfer Array]] sites and the '''Antem Neo''' in [[Overwhelmed Civilian Facility]] sites.