Relic and data sites: Difference between revisions

Line 110:

Sleeper caches are gated deadspace pockets with size limits for entry. Each sleeper cache has its own set of dangers. They contain a mixture of containers with damaging explosions on a failed hack, timed triggers, hazardous clouds, proximity explosions, and sentry guns. For details see the page for individual sleeper cache.

Sleeper caches contain sleeper ~~components~~, manufacturing materials, skill books, and blueprint copies for ~~polarized~~ weapons.

Sleeper caches contain sleeper blue loot, manufacturing materials for Tech 2 and capital ships, skill books and blueprint copies for Polarized weapons.

== Ghost sites ==

Line 118:

The sites have an invisible time limit after which a strong NPC force will arrive, blow up the remaining containers and attack the pilot on-site. The hacks are also riskier as a single failure will cause the container to explode dealing 4000–6000 raw explosive damage to a 10 km radius.

Ghost sites contain Covert Research Tools, Villard Wheels, blueprint copies for 'Packrat' and 'Magpie' Mobile Tractor Units, 'Wetu' and 'Yurt' Mobile Depots, and Ascendancy ~~implants~~.

Ghost sites contain Covert Research Tools, Shattered Villard Wheels, blueprint copies for 'Packrat' and 'Magpie' Mobile Tractor Units, 'Wetu' and 'Yurt' Mobile Depots, and Ascendancy implant blueprint copies.

== Sleeper sites ==

Sleeper relic and data sites are found in wormholes. They are not empty, instead, they have strong sleepers defending the site that need to be defeated before hacking.

Sleeper relic and data sites are found in wormholes. They are not empty, instead, they have strong sleepers defending the site that need to be tanked or defeated before safe hacking.

Sleeper relic and data sites can be identified from {{co|wheat|"Forgotten"}} and {{co|wheat|"Unsecured"}} at the beginning of their names. The combat in them is harder than in combat anomalies of same wormhole class and the rats drop ~~sleeper components as they do~~ in combat sites. They can be run as combat sites only looting the wrecks and ignoring the hacking part.

Sleeper relic and data sites can be identified from {{co|wheat|"Forgotten"}} and {{co|wheat|"Unsecured"}} at the beginning of their names. The combat in them is harder than in combat anomalies of same wormhole class and the rats drop Sleeper blue loot just like in combat sites. They can be run as combat sites, only looting the wrecks and ignoring the hacking part. (They only appear to despawn once the containers have been hacked, or after enough time has passed.)

== Silent Battleground ==

Line 156:

{{Important note box|Please check with your corp/alliance/coalition before doing this as they may have rules against cherry-picking. if so, self-destruct the cans instead by failing the hacks 2 times by opening and immediate closing the hacking window.}}

* Emptied sites will despawn in few ~~minutes~~. Sites that have been partially completed will despawn in a few hours.

* Emptied sites will despawn a few seconds after the last container has been successfully hacked or destroyed. Sites that have been partially completed will despawn in a few hours.

* Once a site has despawned, the same site (sorted based on data or relic) will respawn within 2 minutes within the same region, but never within the same system.

* Sites with difficulty levels I and II should be scannable for any ship fitted with a core probe launcher, and a set of ~~Sister's~~ core ~~probe scanners~~. However, as the difficulty level of the site increases, the minimum scanning strength required also increases.

* Sites with difficulty levels I and II should be scannable for any ship fitted with a core probe launcher, and a set of core scanner probes. However, as the difficulty level of the site increases, the minimum scanning strength required also increases.

* Sites with difficulty levels III and higher normally need to be scanned by a scanning-bonused ship. However, some level III sites may still be scanned by any ship if it is fitted with a Sisters core probe launcher.

* Sites with difficulty levels III and higher normally need to be scanned by a scanning-bonused ship. However, some level III sites may still be scanned by any ship if it is fitted with a Sisters core probe launcher, or if the pilot has high enough scanning skills.

* The recommended scan strength for level IV sites is around 90, while the recommended scan strength for level V sites is 100 and above.

* After the daily [[Server downtime|downtime]] (DT) all Relic and Data sites update their containers. For example, you hack 5/6 containers and leave 1. After DT all these containers will be updated and you can hack them again.

@@ Line 110: / Line 110: @@
 Sleeper caches are gated deadspace pockets with size limits for entry. Each sleeper cache has its own set of dangers. They contain a mixture of containers with damaging explosions on a failed hack, timed triggers, hazardous clouds, proximity explosions, and sentry guns. For details see the page for individual sleeper cache.
-Sleeper caches contain sleeper components, manufacturing materials, skill books, and blueprint copies for polarized weapons.
+Sleeper caches contain sleeper blue loot, manufacturing materials for Tech 2 and capital ships, skill books and blueprint copies for Polarized weapons.
 == Ghost sites ==
@@ Line 118: / Line 118: @@
 The sites have an invisible time limit after which a strong NPC force will arrive, blow up the remaining containers and attack the pilot on-site. The hacks are also riskier as a single failure will cause the container to explode dealing 4000–6000 raw explosive damage to a 10 km radius.
-Ghost sites contain Covert Research Tools, Villard Wheels, blueprint copies for 'Packrat' and 'Magpie' Mobile Tractor Units, 'Wetu' and 'Yurt' Mobile Depots, and Ascendancy implants.
+Ghost sites contain Covert Research Tools, Shattered Villard Wheels, blueprint copies for 'Packrat' and 'Magpie' Mobile Tractor Units, 'Wetu' and 'Yurt' Mobile Depots, and Ascendancy implant blueprint copies.
 == Sleeper sites ==
 {{main|Wormhole sites}}
-Sleeper relic and data sites are found in wormholes. They are not empty, instead, they have strong sleepers defending the site that need to be defeated before hacking.
+Sleeper relic and data sites are found in wormholes. They are not empty, instead, they have strong sleepers defending the site that need to be tanked or defeated before safe hacking.
-Sleeper relic and data sites can be identified from {{co|wheat|"Forgotten"}} and {{co|wheat|"Unsecured"}} at the beginning of their names. The combat in them is harder than in combat anomalies of same wormhole class and the rats drop sleeper components as they do in combat sites. They can be run as combat sites only looting the wrecks and ignoring the hacking part.
+Sleeper relic and data sites can be identified from {{co|wheat|"Forgotten"}} and {{co|wheat|"Unsecured"}} at the beginning of their names. The combat in them is harder than in combat anomalies of same wormhole class and the rats drop Sleeper blue loot just like in combat sites. They can be run as combat sites, only looting the wrecks and ignoring the hacking part. (They only appear to despawn once the containers have been hacked, or after enough time has passed.)
 == Silent Battleground ==
@@ Line 156: / Line 156: @@
 {{Important note box|Please check with your corp/alliance/coalition before doing this as they may have rules against cherry-picking. if so, self-destruct the cans instead by failing the hacks 2 times by opening and immediate closing the hacking window.}}
-* Emptied sites will despawn in few minutes. Sites that have been partially completed will despawn in a few hours.
+* Emptied sites will despawn a few seconds after the last container has been successfully hacked or destroyed. Sites that have been partially completed will despawn in a few hours.
 * Once a site has despawned, the same site (sorted based on data or relic) will respawn within 2 minutes within the same region, but never within the same system.
-* Sites with difficulty levels I and II should be scannable for any ship fitted with a core probe launcher, and a set of Sister's core probe scanners. However, as the difficulty level of the site increases, the minimum scanning strength required also increases.
+* Sites with difficulty levels I and II should be scannable for any ship fitted with a core probe launcher, and a set of core scanner probes. However, as the difficulty level of the site increases, the minimum scanning strength required also increases.
-* Sites with difficulty levels III and higher normally need to be scanned by a scanning-bonused ship. However, some level III sites may still be scanned by any ship if it is fitted with a Sisters core probe launcher.
+* Sites with difficulty levels III and higher normally need to be scanned by a scanning-bonused ship. However, some level III sites may still be scanned by any ship if it is fitted with a Sisters core probe launcher, or if the pilot has high enough scanning skills.
 * The recommended scan strength for level IV sites is around 90, while the recommended scan strength for level V sites is 100 and above.
 * After the daily [[Server downtime|downtime]] (DT) all Relic and Data sites update their containers. For example, you hack 5/6 containers and leave 1. After DT all these containers will be updated and you can hack them again.