Toggle menu
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Hacking: Difference between revisions

From EVE University Wiki
Arin Mara (talk | contribs)
Removed epithets, specified what makes minigames identical, substituted goal for object, omitted needless words, specified what a Node may contain, omitted the Minesweeper reference
Arin Mara (talk | contribs)
Formatted, capitalized and reworded
Line 14: Line 14:


===Defensive Subsystems===
===Defensive Subsystems===
These are represented by large circles with an icon inside, and they will be the bane of your hacking existence. '''Defensive Subsystems prevent you from exploring adjacent nodes until they are disabled.''' Each Defensive Subsystem has two ratings: '''Coherence''' represented by an asterisk atop the Subsystem, which is the equivalent of its health/HP, and '''Strength''' represented by a “wifi/signal” icon listed at the bottom of the Subsystem, which is equivalent to its “attack power.”
'''Defensive Subsystems prevent you from exploring adjacent nodes until they are disabled.'''


Your virus has a Coherence and Strength, too, which you can use to disable the system’s defenses!  Your virus’s Coherence and Strength are listed in the bottom left of the hacking window. You can attack a Defensive Subsystem by clicking it after it has been explored. Attacking a Subsystem is turn-based: your virus will attack the Subsystem lowering the subsystem's Coherence by your Virus Strength, and then, ''if the Subsystem is still active'', it will attack your virus back. If you reduce the subsystem's Coherence to 0, it is disabled and removed from the board.
Each Defensive Subsystem has:
* '''Coherence''' which is its health displayed atop the Subsystem
* '''Strength''' which is its attack power displayed below the Subsystem


If your Virus Coherence reaches 0, you fail the hack and the window is closed. Failing a hack '''once''' does not matter for regular Data/Relic sites, but failing a second hack will destroy that container.  (Note that for some special kinds of containers/sites, such as [[Ghost Site|Ghost Sites]], Sleeper Caches, etc., failing the first hack might cause an explosion, or have other negative effects.). Interrupting a hack counts as a failure, and that includes moving too far away from the can (out of range of your analyzer) while the hacking window is open. This is sometimes a problem for frigates with a MicroWarpDrive active, where you can overshoot the can when Approaching it too fast - so be careful.
Your Virus’s Coherence and Strength are listed in the bottom left of the hacking window. Your Virus will attack a Defensive Subsystem when you click it. Attacking a Subsystem is turn-based: your Virus attacks first, lowering the Subsystem's Coherence by your Virus Strength, and then the Subsystem retaliates if it survived the attack. When you reduce the Subsystem's Coherence to 0, it is disabled and removed from the board.
 
You fail the hack when your Virus Coherence reaches 0. Failing the hack '''once''' does not matter for regular Data/Relic sites, but failing a second hack will destroy that container.  (Note that for some special kinds of containers/sites, such as [[Ghost Site|Ghost Sites]], Sleeper Caches, etc., failing the first hack might cause an explosion, or have other negative effects.). Interrupting a hack counts as a failure, and that includes moving too far away from the can (out of range of your analyzer) while the hacking window is open. This is sometimes a problem for frigates with a MicroWarpDrive active, where you can overshoot the can when Approaching it too fast - so be careful.


[[File:Core node medium orange black background.png|right|thumb|Medium System Core]]
[[File:Core node medium orange black background.png|right|thumb|Medium System Core]]