Limited Sleeper Cache: Difference between revisions

The '''Limited Sleeper Cache''' is the easiest of the Sleeper Cache Sites. Sleeper Cache sites are significantly more difficult than normal data or relic site, and pilots will be risking their ship when trying any of them. However, once familiar with these sites, pilots should be able to run the site without taking any damage. Like all Sleeper Cache sites, the Limited Sleeper Cache require the use of both Data and Relic Analyzers. Entry is restricted to frigates, and an exploration frigate is highly recommended in order to make use of their hacking bonuses.

Limited Sleeper Caches are [[Cosmic Signatures]] that you need to scan down with scanner probes. They are more difficult to scan down than normal signatures, and require well-developed scanning skills to completely scan down.

== Running the site ==

Once you warp to the indication, you'll land in the entry room. You should see a Hyperfluct Generator present. If it has been hacked and a rift is activated, then someone is there, or has been there. If not, it's your turn! Go ahead and hack that Hyperfluct Generator. I will list the outcomes possible below:<br />

'''CAN DIFFICULTY: 7/10 [RED HACK]'''<br />

<span style="color:green">SUCCESS:</span> A new spatial rift (acceleration gate) is opened to the main area, which is called the Ransacked Storage Site.<br />

<span style="color:red">FAILURE:</span> You have two minutes to attempt a successful hack of the can. Should you fail within that time, the site will despawn.

By taking the Spatial Rift, the first room is made available to the player. Initially, it's important to cargo scan the containers to evaluate the value of the site. Those inexperienced with the site should probably run it anyways if there isn't much value for the experience. Drop the mobile depot to get the counter counting down. Let us assume the container inside the wreck field has good things inside it: there are two approaches of dealing with it.<br />

| style="padding:8px;" | ''The can difficulty numbers do vary slightly each time, because of the way that the random hacking minigame is generated. For reference, high-sec rookie practice cans (in the Rookie Systems) are 1/10. Regular high sec easy-peasy cans are 3 or 4/10. Low-sec, null-sec, and wormhole space cans are 5 to 8/10, depending on the value of the can, in most cases. Generally, I've found them to be about 6 to 7/10 in difficulty.''

[[File:3P38 Limited 28.png|200px|thumb|right|Some hacks are not meant to be]]The first is to hack the Remote Pressure Control Unit, cook a Microwarpdrive (afterburner is not fast enough) to the container inside the wreck cloud, quickly hack it, then burn the Microwarpdrive back out before the timer runs out. There is enough time for 2 "standard paced" hacks, 1 "slow hack" or 3 really fast hack attempts, depends how good the hacker is and ... luck. Normally it's a red hack, which means all the usual Virus Suppressors and Restoration Nodes. The problem with this approach is both the limited timeframe and if a player cannot survive the incoming damage after the timer is up, there is a chance of explody bits.

The second approach is to fit specifically for surviving the area of affect cloud. All toxic gas clouds, both the prespawned ones and the ones that are generated upon detonation of an Unstable Plasma Chamber do similar damage per second, omni-damage types. This approach is recommended, though it does require excellent capacitor skills and proper tank skills. The advantage of this approach is the hacker can hack the container at his leisure, with little personal risk to himself before the hack can be completed.

:2. Hack the Remote Pressure Control Unit (a Data hack):

::'''CAN DIFFICULTY: 7/10 [RED HACK]'''<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.

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

|[[File:3P38 Limited 4.png|thumb|none|alt=A|Sustaining 96 damage from RPCU failure]]||[[File:3P38 Limited 10.png|thumb|none|alt=A|A Magnate tanking the damage field]]||[[File:3P38 Limited 8.png|thumb|none|alt=A|Heron sustaining the DPS comfortably]]||[[File:3P38 Limited 2.png|thumb|none|alt=A|This is why T2 Analyzers are a must (the early days)]]

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.

# Refit to the appropriate capstable local repair module fit.