Limited Sleeper Cache: Difference between revisions

Line 56:

| mid5name=Limited Multispectrum Shield Hardener I

| mid5typeID=9632

| rig1name=Small ~~Anti-~~EM ~~Screen~~ Reinforcer I

| rig1name=Small EM Shield Reinforcer I

| rig1typeID=31716

| rig2name=Small Anti-Thermal Screen Reinforcer I

Line 169:

| rig2name=Small Anti-Thermal Screen Reinforcer I

| rig2typeID=31752

| rig3name=Small ~~Anti-~~EM ~~Screen~~ Reinforcer I

| rig3name=Small EM Shield Reinforcer I

| rig3typeID=31716

| high1name=open

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

::# The container explodes. A Heron with an EM Shield 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 56: / Line 56: @@
 | mid5name=Limited Multispectrum Shield Hardener I
 | mid5typeID=9632
-| rig1name=Small Anti-EM Screen Reinforcer I
+| rig1name=Small EM Shield Reinforcer I
 | rig1typeID=31716
 | rig2name=Small Anti-Thermal Screen Reinforcer I
@@ Line 169: / Line 169: @@
 | rig2name=Small Anti-Thermal Screen Reinforcer I
 | rig2typeID=31752
-| rig3name=Small Anti-EM Screen Reinforcer I
+| rig3name=Small EM Shield Reinforcer I
 | rig3typeID=31716
 | high1name=open
@@ 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 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.
+::# The container explodes. A Heron with an EM Shield 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====