Limited Sleeper Cache: Difference between revisions

Line 54:

| mid4name=5MN Quad LiF Restrained Microwarpdrive

| mid4typeID=35658

| mid5name=Limited ~~Adaptive Invulnerability Field~~ I

| mid5name=Limited Multispectrum Shield Hardener I

| mid5typeID=9632

| rig1name=Small Anti-EM Screen Reinforcer I

Line 343:

:::'''CAN DIFFICULTY: 7/10 DATA [RED HACK]'''

:::SUCCESS: The area of effect damage cloud surrounding the wreck is turned off for two to three minutes.

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

:::FAILURE: 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 Multispectrum Shield Hardener and Anti-EM/Anti-Thermal rigs. It's not severe enough to warrant any particular concern.

:3. 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 on if not done so already, and immediately begin hacking it with the Relic Analyzer.

:4. Watch messages in local: 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, which should be near the site warpin beacon.

Line 395:

::FAILURE: There are two possibilities:

::# Nothing happens. In this case, the can be hacked repeatedly, but be prepared for (2) on subsequent failures. An experiment was ran for 1 hour after such a failure and nothing happened. Another experiment left the client running for 13 hours, with nothing resulting from failure of the container.

::# 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 will not have any forcefield generators spawn to inhibit hacking attempts. The container explodes 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 Multispectrum Shield Hardener 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 will not have any forcefield generators spawn to inhibit hacking attempts. The container explodes about ten seconds after the hack attempt is failed.

====Method 2: Destroy the Forcefield====

@@ Line 54: / Line 54: @@
 | mid4name=5MN Quad LiF Restrained Microwarpdrive
 | mid4typeID=35658
-| mid5name=Limited Adaptive Invulnerability Field I
+| mid5name=Limited Multispectrum Shield Hardener I
 | mid5typeID=9632
 | rig1name=Small Anti-EM Screen Reinforcer I
@@ Line 343: / Line 343: @@
 :::'''CAN DIFFICULTY: 7/10 DATA <span style="color:red">[RED HACK]</span>'''<br />
 :::<span style="color:green">SUCCESS:</span> The area of effect damage cloud surrounding the wreck is turned off for two to three minutes.<br />
-:::<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 Multispectrum Shield Hardener and Anti-EM/Anti-Thermal rigs. It's not severe enough to warrant any particular concern.
 :3. 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 on if not done so already, and immediately begin hacking it with the Relic Analyzer.
 :4. <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, which should be near the site warpin beacon.
@@ Line 395: / Line 395: @@
 ::<span style="color:red">FAILURE:</span> There are two possibilities:
 ::# Nothing happens. In this case, the can be hacked repeatedly, but be prepared for (2) on subsequent failures. An experiment was ran for 1 hour after such a failure and nothing happened. Another experiment left the client running for 13 hours, with nothing resulting from failure of the container.
-::# 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 will not have any forcefield generators spawn to inhibit hacking attempts. The container explodes 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 Multispectrum Shield Hardener 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 will not have any forcefield generators spawn to inhibit hacking attempts. The container explodes about ten seconds after the hack attempt is failed.
 ====Method 2: Destroy the Forcefield====