More actions
| Line 677: | Line 677: | ||
::<span style="color:red">FAILURE:</span> No specific site penalty, a small amount of damage is absorbed by your ship -- in the test case, 96 damage against a Heron with a MSE, Limited Adaptive Invulnerability Field and Anti-EM/Anti-Thermal rigs. It's not severe enough to warrant any particular concern. | ::<span style="color:red">FAILURE:</span> No specific site penalty, a small amount of damage is absorbed by your ship -- in the test case, 96 damage against a Heron with a MSE, Limited Adaptive Invulnerability Field and Anti-EM/Anti-Thermal rigs. It's not severe enough to warrant any particular concern. | ||
:# Immediately apply Keep at Range (2250m) on the Storage Depot inside the wreck cloud, then turn on the Microwarpdrive. Turn it off when you get close enough to it. Lock it up if not done so already, and immediately begin hacking it with the Relic Analyzer II. | :# Immediately apply Keep at Range (2250m) on the Storage Depot inside the wreck cloud, then turn on the Microwarpdrive. Turn it off when you get close enough to it. Lock it up if not done so already, and immediately begin hacking it with the Relic Analyzer II. | ||
:# | :# <span style="color:red">Watch messages in local:</span> if not successful by the 30 second mark, just align back to the Remote Pressure Control Unit (or straight up/straight down) and burn the Microwarpdrive. Otherwise, loot it and burn out with the Microwarpdrive to a safe direction away, probably best towards the Mobile Depot. | ||
The Area of Effect damage cloud near the wreck does roughly 100 DPS to a standard unmodified resistance profile of a Tech I vessel. Its approximate dimensions, measured from the Storage Depot within, is about 12km in radius. | The Area of Effect damage cloud near the wreck does roughly 100 DPS to a standard unmodified resistance profile of a Tech I vessel. Its approximate dimensions, measured from the Storage Depot within, is about 12km in radius.<br /> | ||
Now onto the second approach. ''The specific fit must be able to rep more than 60 EHP/sec and capacitor stability is a must.'' The Relic Analyzer II does not count in the capacitor stability checks: keep it off in EFT/Pyfa whilst checking for capacitor stability. | Now onto the second approach. ''The specific fit must be able to rep more than 60 EHP/sec and capacitor stability is a must.'' The Relic Analyzer II does not count in the capacitor stability checks: keep it off in EFT/Pyfa whilst checking for capacitor stability. | ||
| Line 706: | Line 706: | ||
<span style="color:red">FAILURE:</span> This is a very interesting topic. There appear to be two possibilities: | <span style="color:red">FAILURE:</span> This is a very interesting topic. There appear to be two possibilities: | ||
:# Nothing happens. I once waited for one hour inside the site for "something to happen", and nothing happened. If this occurrence happens, then it seems that the can be hacked repeatedly, but be prepared for (b). | :# Nothing happens. I once waited for one hour inside the site for "something to happen", and nothing happened. If this occurrence happens, then it seems that the can be hacked repeatedly, but be prepared for (b). | ||
:# The container explodes. A Heron with an Anti-EM Screen Reinforcer, Anti-Thermal Screen Reinforcer, Medium Azeotropic Restrained Shield Extender, a Limited Adaptive Invulnerability Field and a Damage Control II ate 1225 damage, while Keeping at Range (5000m) from the container. After this, the other containers did not have any forcefield generators spawn to inhibit hacking attempts, which was distinctly unexpected. The container seems to explode about ten seconds after the hack attempt is failed. | :# The container explodes. A Heron with an Anti-EM Screen Reinforcer, Anti-Thermal Screen Reinforcer, Medium Azeotropic Restrained Shield Extender, a Limited Adaptive Invulnerability Field and a Damage Control II ate 1225 damage (dropped shields to about 25%), while Keeping at Range (5000m) from the container. After this, the other containers did not have any forcefield generators spawn to inhibit hacking attempts, which was distinctly unexpected. The container seems to explode about ten seconds after the hack attempt is failed. | ||
As for the second approach, given that the the Forcefield Generator itself spawns a [http://games.chruker.dk/eve_online/item.php?type_id=13200 Large EM Forcefield], it does call for some DPS. It's not exactly difficult to destroy it, however the 150hp/sec regeneration is a problem. 110 DPS is not enough: and given that Destroyers and Stealth Bombers cannot enter the site, this is a job for either multiple people or a high-damage frigate, such as an Assault Frigate or something like a Taranis. A test with an all-damage fit Taranis which did 304 DPS unheated using Void S (36 rounds exactly, with two Hobgoblin IIs) took it out handily in 20 seconds. | As for the second approach, given that the the Forcefield Generator itself spawns a [http://games.chruker.dk/eve_online/item.php?type_id=13200 Large EM Forcefield], it does call for some DPS. It's not exactly difficult to destroy it, however the 150hp/sec regeneration is a problem. 110 DPS is not enough: and given that Destroyers and Stealth Bombers cannot enter the site, this is a job for either multiple people or a high-damage frigate, such as an Assault Frigate or something like a Taranis. A test with an all-damage fit Taranis which did 304 DPS unheated using Void S (36 rounds exactly, with two Hobgoblin IIs) took it out handily in 20 seconds. | ||