Difference between revisions of "Override Transfer Array"
m (→Hacking) |
m (→Hacking: Made the images flexible depending on screen width.) |
||
| Line 69: | Line 69: | ||
The hacking mechanics are based on the old method, prior to the changes made in [[Odyssey]]. It means you can and should use as many data analyzers as possible to increase the odds of hacking on the first attempt. 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, see the image below. | The hacking mechanics are based on the old method, prior to the changes made in [[Odyssey]]. It means you can and should use as many data analyzers as possible to increase the odds of hacking on the first attempt. 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, see the image below. | ||
| − | + | <p><ul class="gallery"> | |
| − | + | <li class="gallerybox" style="border:none;"> [[image: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.]]</li> | |
| − | + | <li class="gallerybox" style="border:none;"> [[image: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(s) on it to start hacking.]]</li> | |
| − | + | <li class="gallerybox" style="border:none;"> [[image: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.]]</li> | |
| − | + | <li class="gallerybox" style="border:none;"> [[image: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.]]</li></ul></p> | |
| − | |||
= Hints & tips = | = Hints & tips = | ||
Revision as of 01:00, 24 August 2019
|
| Incursion sites |
|---|
| Click the title for a summary, or return to Incursions for general information. |
| Staging sites |
| Vanguard sites |
| Assault sites |
| Headquarter sites |
| Mothership sites |
Objectives
Force required
 |
Fleet of 10 - 12 pilots (up to 15 in low/null) 2 - 3 logistics needed Sites take about 5 - 10 minutes |
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. |
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.
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.
Synopsis from ISHAEKA-0095. DED Special Operations.
Authorized for Capsuleer dissemination.
Enemies
Below is a list of enemies that spawn in this site. See Sansha's Manual for a full list of the incursion rats.
| Name | Sig [1] | Speed [2] | Orbit / Speed [3] | Damage / Volley [4] | Range [5] | Effective HP [6] | |
|---|---|---|---|---|---|---|---|
 |
Auga Hypophysis   |
 325 m |
 1,100 m/s |
6 km  170 m/s |
480 dps  2,400 hp |
12 - 20 km  |
52k ehp  |
 |
Deltole Tegmentum   |
540 m |
850 m/s |
12 km 118 m/s |
818 dps  4,500 hp |
< 45 km |
179k ehp |
 |
Eystur Rhomben |
49 m |
3,360 m/s |
11 km 560 m/s |
120 dps 600 hp |
10 - 12 km |
9k ehp |
|
Niarja Myelen  |
53 m |
2,760 m/s |
15 km 405 m/s |
(no weapons) | (no weapons) | 4k ehp |
|
Tama Cerebellum |
39 m |
2,100 m/s |
12 km 355 m/s |
300 dps 2,700 hp |
< 70 km |
8k ehp |
- ^ While using their propulsion module, they suffer the same signature bloom as players.
- ^ This is the speed of the ship while they try to get within orbit or as they try to chase after you, suffering the same signature bloom as players do with the propulsion module on. They will turn off any propulsion modules once they get close to their preferred orbit.
- ^ Preferred orbit range and regular speed while orbiting, which is their regular speed without the propulsion module turned on.
- ^ Damage per second as well as damage per volley. Unless stated otherwise, turrets do an equal amount of EM and thermal damage while torpedoes do an equal amount of kinetic and explosive damage.
- ^ This is the effective range of this ship, presented with two values for turrets, optimal and optimal + double falloff, as well as a single range for torpedoes.
- ^ This is the amount of damage this ship can take, taking into account their resists. All ships, except the Lirsautton Parichaya have omni tanks. Hover over the icon for information about raw hitpoints.
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.
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.
| # | Targets for the entire fleet | Reason | ||
|---|---|---|---|---|
| Regular targets [1] | Small targets [2] | |||
| 1 | Niarja Myelen
|
Because the Niarja Myelen jams and neuts. | ||
| 2 | Tama Cerebellum Auga Hypophysis Deltole Tegmentum
|
The Tama warp disrupts and you remove a lot of damage quickly by shooting them first.
The Auga warp disrupts, webs and while it does less damage than the Deltole it closes the distance faster and is easier to kill. | ||
| 3 |  Eystur Rhomben
|
Eysturs are ignored, they will simply respawn if killed and aren't necessary for site completion. | ||
- ^ These targets are usually larger, cruisers or battleships and suitable for ships with good damage projection, lower tracking, like battleships with large guns.
- ^ Smaller targets, like frigates or extremely fast or small cruisers. Ideally the primary targets for strategic cruisers, Vindicators or the dronebunny as a last resort.
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.
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.
Special requirements
|
Requires the use of data analyzer modules to hack the logistics control array. (the logistics control array is roughly 30km away from the spawn point) |
Hacking
Hacking is done by approaching, locking up the logistics control array and activating the data analyzers as soon as you get within range. Once completed you will get a message saying: "Local Sansha logistics systems subverted. Hostile logistics disabled."
The hacking mechanics are based on the old method, prior to the changes made in Odyssey. It means you can and should use as many data analyzers as possible to increase the odds of hacking on the first attempt. 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, see the image below.
Hints & tips
- There are three waves in this site, more or less identical in terms of ship composition but they spawn in different positions.
- 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.
- The first wave spawns on the right side of the remote logistics station.
- 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.
- 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.
- 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 Scout. This is usually a newbie or cheap alt character attached to the fleet. They will be flying a cheap Heron fit with data analyzers. There is rarely a shortage of alts, but it can of course be done by logistics fitting data analyzers if desperate (at the cost of not having as many remote tracking computers).
- While you can do this site without hacking, it severely hampers your ability to get ships off the field quickly and drastically increases site times. The remote logistics station will repair every single Sansha ship on grid periodically, making it hard to kill ships, especially the Deltole without sufficient concentrated fire.
- 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.
