Toggle search
Toggle menu
4.5K
7.6K
15.6K
232K
EVE University Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Override Transfer Array: Difference between revisions

From EVE University Wiki
More actions
← Older edit
VisualWikitext
Xelrich (talk | contribs)
21 edits
Change background color to design-token. Rework heading levels. Replace deprecated html with CSS. Implement flex container.
 
(33 intermediate revisions by 11 users not shown)
Line 1: Line 1:
[[Category:Work in progress]]
{{incursions sites}}
<div style="float:right; font-size:80%; line-height:125%; list-style-type:none; text-indent:0in; margin-left:0px; padding:0.5em;">__TOC__</div>
== Objectives ==
=Forces Required=
=== Force required ===
* 5 - 10 pilots
{{incursion sites|vanguards}}


=Military Intelligence=
=== Military information ===
Your objective is to destroy the Sansha’s Nation fleet amassing here. They will be making use of logistics arrays, so disabling them may be advisable.
{|
| [[File:incursions_sansha_transmission.png]]
| Your objective is to destroy the Sansha's Nation fleet amassing here. They will be making use of logistics arrays, so disabling them may be advisable.
|}


=== Background information ===
One of the most significant evolutions in the Nation's strategy has been the move away from abducting planetary populations. Their new tactical doctrine, which relies in part upon system-wide capsule interference, is clearly focused on limiting the power and influence of the capsuleer class.


=Rewards=
The technology underlying the system-wide capsule overrides is not dissimilar to CONCORD's own Tracking and Response System (TRS). Where it veers into new territory is in the application of new technologies designed to override local resources in ways previously thought impossible. Intelligence gathered by DED operatives strongly suggests that this facility is chiefly responsible for establishing these overrides.


[[File:Vanguard_rpr.PNG|right|Vanguard Reward Payout Ratio]]
''Synopsis from ISHAEKA-0095. DED Special Operations.''<br>''Authorized for Capsuleer dissemination.''
* 15,000,000 ISK × ratio
* 2,000 CONCORD LP × ratio


=Background Intelligence=
== Enemies ==
One of the most significant evolutions in the Nation’s strategy has been the move away from abducting planetary populations. Their new tactical doctrine, which relies in part upon system-wide capsule interference, is clearly focused on limiting the power and influence of the capsuleer class.
Below is a list of enemies that spawn in this site. See [[Sansha's Manual]] for a full list of the incursion rats.
{{incursion rats|Start}}
{{incursion rats|Auga Hypophysis}}
{{incursion rats|Deltole Tegmentum}}
{{incursion rats|Eystur Rhomben}}
{{incursion rats|Niarja Myelen}}
{{incursion rats|Tama Cerebellum}}
{{incursion rats|End}}


The technology underlying the system-wide capsule overrides is not dissimilar to CONCORD’s own Tracking and Response System (TRS). Where it veers into new territory is in the application of new technologies designed to override local resources in ways previously thought impossible. Intelligence gathered by DED operatives strongly suggests that this facility is chiefly responsible for establishing these overrides.
=== Priorities ===
This is a generic kill order that works no matter what fleet you're running. Certain special doctrines or fleet compositions could change some things in order to optimize their fleet efficiency, so this isn't necessarily the only kill order, but it works.


Synopsis from ISHAEKA-0095. DED Special Operations.
As a general rule of thumb, if you cannot shoot the highest priority target due to low damage projection, move on to the next target you can actually hit. Just remember to switch back to a higher priority target if it moves into range later on.
Authorized for Capsuleer dissemination.
{| class="wikitable"
|- style="background-color: var(--background-color-warning-subtle);"
! colspan="2" rowspan="2" | #
! colspan="2" | Targets for the entire fleet
! style="text-align: center" rowspan="2" nowrap | Reason
|- style="background-color: var(--background-color-warning-subtle); white-space: nowrap;"
! Regular targets<small>&nbsp;<ref>These targets are usually larger, cruisers or battleships and suitable for ships with good damage projection, lower tracking, like battleships with large guns.</ref></small>
! Small targets<small>&nbsp;<ref>Smaller targets, like frigates or extremely fast or small cruisers. Ideally the primary targets for '''strategic cruisers''', [[Vindicator]]s or the [[Roles in Incursions#Dronebunny|dronebunny]] as a last resort.</ref></small>
|- style="vertical-align: top;"
| 1
| style="background-color: Red;" |
| style="text-align: center; padding: 5px;" colspan="2" | '''Niarja Myelen'''&nbsp;[[File:Icon_target_max.png|24px|link=|Jamming]][[File:icon_energy_neutralizer_i.png|24px|link=|Energy neutralizing]]
| style="padding:5px;" | Because the '''Niarja Myelen''' jams and neuts.
|- style="vertical-align: top;"
| 2
| style="background-color: OrangeRed;" |
| style="text-align :center; padding: 5px;" colspan="2" nowrap | '''Tama Cerebellum'''&nbsp;[[File:icon_warp_disruptor_i.png|24px|link=|Warp disrupting]]<br>'''Auga Hypophysis'''&nbsp;[[File:icon_warp_disruptor_i.png|24px|link=|Warp disrupting]][[File:icon_stasis_webifier_i.png|24px|link=|Webbing]]<br>'''Deltole Tegmentum'''&nbsp;[[File:icon_warp_disruptor_i.png|24px|link=|Warp disrupting]][[File:icon_energy_neutralizer_i.png|24px|link=|Energy neutralizing]][[File:icon_target_painter_i.png|24px|link=|Target painting]]
| style="padding: 5px;" | The '''Tama''' warp disrupts and you remove a lot of damage quickly by shooting them first.


=Encounter=
The '''Auga''' warp disrupts, webs and while it does less damage than the '''Deltole''' it closes the distance faster and is easier to kill.
[[File:OTA_enc.PNG|Override Transfer Array Encounter]]
|- style="vertical-align :top;"
==Objectives==
| 3
| style="background-color: Green;" |
| style="background-color: var(--background-color-destructive-subtle); text-align: center; padding: 5px;" colspan="2" | [[File:icon_large_red_x.png|24px|Do not shoot!]]'''Eystur Rhomben'''
| style="padding: 5px; background-color: var(--background-color-destructive-subtle);" | '''Eysturs''' are to be ignored, they will simply respawn when killed and aren't necessary for site completion.
|}
<small><references/></small>


This site has smaller waves than usual due to the immense ship health regeneration speed while the Logistics Station remains active
=== Triggers ===
With the exception of the '''Eysturs''', the last enemy killed normally triggers the next wave. Sometimes a new wave might be triggered with one or two '''Tamas''' left on grid. If that happens, they will still need to be killed for site completion.


*Hack Logistics Control Array disabling Remote Logistics Station. ''Requires a ship fitted with a Codebreaker module.''
You can completely ignore '''Eysturs''' as they are not part of the wave mechanics nor are they necessary to kill for site completion or extraction.
*Kill all defending Sansha Battleship pirates.


''Note: Eystur Rhomben will continuously re-spawn if destroyed and do not need to be eliminated in order to complete the site. It is therefore recommended to ignore them unless you are competing with another fleet.''
=== Special requirements ===
{|
| [[File:Icon data analyzer i.png|48px|link=]]
| Requires the use of '''data analyzer''' modules to hack the logistics control array.<br>''(the logistics control array is roughly 30km away from the spawn point)''
|}


==NPCs==
==== Hacking ====
There are two different versions of the OTA at present, one with Eysturs and one without. Both versions have 3 waves. Each wave spawns:
Hacking is done by approaching&locking up the logistics control array, activating the data analyzer as soon as you get within range and then completing the [[Hacking|Hacking Minigame]]. Once completed you will get a message saying:'' "Local Sansha logistics systems subverted. Hostile logistics disabled."''
*Deltole Tegmentum x1 ''(target painter/warp disruptor/neut battleship)''
*Auga Hypohysis x1-3 ''(web/warp disruptor/very high laser DPS cruiser)''
*Niarja Myelen x1-3 ''(jam/neut frigate)''
*Tama Cerebellum x2-5 ''(wev/warp disruption/hit missile DPS frigate)''


In the Eystur version 5 Eysturs will spawn one by one after the first ship warps in. This ships endlessly respawn and should be ignored. (In the event a fleet takes too long or leaves the site for a prolonged period the Eysturs will warp out without the other ships being killed.) In both versions the next wave will not spawn until all Battleships and Cruisers are destroyed. In the Eystur version all the Frigates must be destroyed as well. In the version without Eysturs not all Frigates must be killed and it is possible to end up with a lot of Tamas on the field if not careful.
* This part can usually be skipped as a a grope of paladins can be use to out-dps the reps
* Since failing the minigame carries not further consequences, feel free to (within reason) use more speed and less caution than you would at a regular data site.
* One cycle of your Microwarpdrive should bring you into range to start hacking, it is adviced to 'Turn off Auto-Repeat' so you don't overshoot and move out of the max range of your Data Analyzer.
* Once hacked the tower will stop repairing for about six minutes, which is usually more than enough for a decent fleet to finish the site. The control array to hack will be available in a clockwise pattern, starting at exactly 90° to your left when you warp in, see the image below.


==Kill Order==
<div style="display: flex; flex-wrap: wrap>
<div>
[[File:Incursions_hacker_array.png|thumb| If you look down the direction your ship is warping in, the first tower to hack will be on your left.]]
</div>
<div>
[[File:incursions_logistics_control_array.png|thumb| The active control array will turn into an interactive object, much like a mission loot container. Simply lock it up and activate your data analyzer on it to start hacking.]]
</div>
<div>
[[File:incursions_remote_logistics_station.png|thumb| When the '''remote logistics station''' is hacked it'll have this easily identifiable mist- or cloud-like effect around it. The graphics may be slightly different depending on your shader settings, potentially much greener. But the nebulae effect, regardless of colour, is a dead give-away.]]
</div>
<div>
[[File:incursions_ota_order.png|thumb| Normally we only need one hack, but in the case we need multiple hacks the control array to hack will be available clockwise; Control array to your left, then the one to the right closest to the repair station, then the one to the right furthest away from the repair station.]]
</div>
</div>


===Per wave as present===
== Hints & tips ==
*Niarja ''(tag when the tower is up)''
* There are three waves in this site, more or less identical in terms of ship composition but they spawn in different positions.
*Auga
** Waves spawn roughly 70 km off, with the exception of the third wave that spawns 35 - 40 km away from the beacon. The Sansha will then rapidly close the distance to their preferred orbit. The '''Eystur Rhombens''' will spawn, as well as respawn if killed, right in front of the remote logistics station.
*Deltole
*** The first wave spawns on the right side of the remote logistics station.
*Tama ''(Drone Bunny attacks these after the Niarjas)''
*** The second wave spawns on the left side of the remote logistics station.
*** The third one above or below the remote logistics station.
** The different waves are slightly randomised. The same type of ships will spawn in each wave, but the number of each is randomised. So you will encounter the same type of ships in each site, but the number of ships per type in each individual wave will be slightly different. There will only be one '''Deltole Tegmentum''' per wave however.
* Focusing fire is really important at the start of this site to overcome the repairs. Tagging '''Niarjas''', '''Tamas''' and '''Augas''' as quickly as possible helps ensure that the fleet knows in what order they are to hit their primary targets. This is due to the logistics tower hack, as noted below.
* Hacking is preferably done by the [[Roles in Incursions#Hacker.2FScout|Scout]]. This is usually a newbie or cheap alt character attached to the fleet. They will be flying a cheap [[Vanguard Incursion fits#Heron|Heron]] fit with a data analyzer. There is rarely a shortage of alts, but it can of course be done by logistics fitting a data analyzer if desperate (at the cost of not having as many remote tracking computers).
** If you hack the tower you probably won't need to continue tagging the '''Niarjas''' and '''Tamas''', but tagging the '''Augas''' is still helpful.
* When run with a hacker, this site is usually the fastest of the Vanguard sites and is typically preferred when possible. Note that other factors can play a role in the site decision, such as contesting fleets and their priorities, as well as warp distance from the current site.


===Ships to ignore:===
{{Incursions sites horizontal}}
*Eystur Rhomben


===Safety Tips===
*All guns should be brought to bear on Niarja frigates if they are present.
*Most ships can be brought down with enough DPS, so a good enough fleet does not have to hack the tower.


==Hints and Tips==
[[Category:Incursions sites]]
*''This site can be out-dps'ed with enough fleet damage.''
*''If the fleet doesn't have enough DPS, arrays need to be hacked.''
*''After the array is hacked, the Station will deactivate and be covered in a white cloud until re-activated.''
*''There are 3 Logistics control arrays.  Only 1 is active at a time.''
*''Arrays activate in clockwise order, starting with the tower on the left. Arrays are approximately 30km from warp in.''
*''A Battlecruiser or Cruiser with a Microwarpdrive and a codebreaker is sufficient to hack the tower.''
*''OTA sites tend to tear through drones, keep an eye on your own and recall individual units as they take damage.''
*''For this reason it is recommended to delay drone deployment until the Eystur Rhomben have already selected their first target.''
 
[[Category:Incursion]]
Retrieved from "https://wiki.eveuniversity.org/Override_Transfer_Array"