Toggle search
Toggle menu
4.5K
7.6K
15.6K
232.1K
EVE University Wiki
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
More actions
← Older editNewer edit →
VisualWikitext
Arin Mara (talk | contribs)
5,648 edits
m Specified which Missions require hacking: Agent Missions
Arin Mara (talk | contribs)
5,648 edits
Added a System Core header and created a table that shows which Defensive Subsystem can appear in a hack
Line 5: Line 5:
[[File:Hacking_Indications.png|400px|thumb|right|The hacking minigame with systems indications.]]
[[File:Hacking_Indications.png|400px|thumb|right|The hacking minigame with systems indications.]]


The goal of the hacking minigame is to '''find and disable the Container’s System Core'''. You do this by maneuvering a Virus through the board of nodes that represent the Container’s electronics.
The goal of the hacking minigame is to '''find and disable the Container’s System Core'''. You do this by maneuvering a Virus through the board of nodes that represents the Container’s electronics.


Nodes are:
Nodes are:
Line 12: Line 12:
* gray if neither explored or adjacent to explored nodes
* gray if neither explored or adjacent to explored nodes


Clicking on a green unexplored node will reveal its contents: if the node is empty, it will turn orange and allow you to further explore adjacent nodes.
Clicking on a green, unexplored, node will reveal its contents: if the node is empty, it will turn orange and allow you to further explore adjacent nodes.


Instead of being empty a node may contain:
Instead of being empty a node may contain:
Line 20: Line 20:
* a Data Cache
* a Data Cache


If the newly explored node is empty it will briefly display a number between 1 and 5. The number says how far you are from the nearest node with a Utility Subsystem, System Core or Data Cache.
If the newly explored node is empty it will briefly display a number between 1 and 5. The number says how far you are from the nearest node with a System Core, Utility Subsystem or Data Cache.


Number:
Number:
* 1 means an adjacent node is a Utility Subsystem, System Core or Data Cache
* 1 means an adjacent node is a System Core, Utility Subsystem or Data Cache
* 2, 3 and 4 means the nearest Utility Subsystem, System Core or Data Cache is respectively 2, 3 and 4 nodes away
* 2, 3 and 4 means the nearest System Core, Utility Subsystem or Data Cache is respectively 2, 3 and 4 nodes away
* 5 means you are 5 or more nodes away from the nearest Utility Subsystem, System Core or Data Cache
* 5 means you are 5 or more nodes away from the nearest System Core, Utility Subsystem or Data Cache


The number doesn't tell you how distant you are from the nearest Defensive Subsystem.
The number doesn't tell you how distant you are from the nearest Defensive Subsystem.


===Defensive Subsystems===
===System Core===
'''Defensive Subsystems prevent you from exploring adjacent nodes until they are disabled.'''
'''Finding and disabling the System Core is the goal of the hacking minigame.'''
 
System Cores and Defensive Subsystems have:
* '''Coherence''' which is its health displayed atop the icon
* '''Strength''' which is its attack power displayed below the icon
 
Your Virus’s Coherence and Strength are listed in the bottom left of the hacking window.
 
Your Virus will attack the System Core or Defensive Subsystem when you click it. Attacking a is turn-based: your Virus attacks first, lowering their Coherence by your Virus Strength, and then the System Core or Defensive Subsystem retaliates if they survived the attack. When you reduce their Coherence to 0, it is disabled and removed from the board.
 
You fail the hack when:
* your Virus Coherence reaches 0
* close the hacking window for any other reason such as moving too far away from the Container structure
 
If you fail the hack:
* twice a Data or Relic Site Container structure will be destroyed
* once a Covert Research Facility or Ghost Site Container structure will be destroyed and deal a large amount of damage to all ships in range
* once a Sleeper Cache may release a toxic gas, raise an alarm or put up another obstacle


Each Defensive Subsystem has:
The color of the System Core reflects the difficulty of the Container structure. Some Defensive Subsystems defend only the more difficult System Cores.
* '''Coherence''' which is its health displayed atop the Subsystem
* '''Strength''' which is its attack power displayed below the Subsystem


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.
{|class="wikitable"
! scope="col" style="width: 80px;" | Difficulty
! scope="col" style="width: 80px;" | System Core
! scope="col" style="width: 80px;" | Firewall
! scope="col" style="width: 80px;" | Anti-Virus
! scope="col" style="width: 80px;" | Resto. Node
! scope="col" style="width: 80px;" | Suppressor


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.
|-
|Very Easy
|Place Holder
| style="text-align:center;" |[[File:Firewall_node.png]]
| style="text-align:center;" |[[File:Antivirus_node.png]]
| style="text-align:center;" |[[image:Icon_large_red_x.png]]
| style="text-align:center;" |[[image:Icon_large_red_x.png]]


[[File:Core node medium orange black background.png|right|thumb|Medium System Core]]
|-
|Easy
| style="text-align:center;" |[[File:Core node easy green.png]]
| style="text-align:center;" |[[File:Firewall_node.png]]
| style="text-align:center;" |[[File:Antivirus_node.png]]
| style="text-align:center;" |[[image:Icon_large_red_x.png]]
| style="text-align:center;" |[[image:Icon_large_red_x.png]]


[[File:Core node hard red.png|right|thumb|Hard System Core]]
|-
|Medium
| style="text-align:center;" |[[File:Core node medium orange black background.png]]
| style="text-align:center;" |[[File:Firewall_node.png]]
| style="text-align:center;" |[[File:Antivirus_node.png]]
| style="text-align:center;" |[[File:Restorer_node.png]]
| style="text-align:center;" |[[image:Icon_large_red_x.png]]
 
|-
|Hard
| style="text-align:center;" |[[File:Core node hard red.png]]
| style="text-align:center;" |[[File:Firewall_node.png]]
| style="text-align:center;" |[[File:Antivirus_node.png]]
| style="text-align:center;" |[[File:Restorer_node.png]]
| style="text-align:center;" |[[File:Supressor_node.png]]
|}
 
===Defensive Subsystems===
'''Defensive Subsystems prevent you from exploring adjacent nodes until they are disabled.'''


{|class=wikitable style="width: 900px;background:#111111"
{|class=wikitable style="width: 900px;background:#111111"
Line 60: Line 111:
|[[File:Supressor_node.png]]
|[[File:Supressor_node.png]]
|'''Virus Suppressor''' subsystems lower your Virus Strength while active.
|'''Virus Suppressor''' subsystems lower your Virus Strength while active.
|-
|[[File:Core node easy green.png]]
|'''Core''' is the target of hacking. Disabling it will complete the hack.<br> The color of the System Core reflects the difficulty of the container: Green for easy; Orange for medium; Red for hard.
|}
|}
===Data Caches===
Data Caches act a bit like a “treasure chest.” They can contain either a “treasure” (a useful Utility Subsystem), or a “trap” (a particularly nasty Defensive Subsystem). Data Caches have to be manually opened after being exposed (single-click them), so you can safely leave the decision as to whether or not to chance their activation until later on in your hacking attempt.


===Utility Subsystems===
===Utility Subsystems===
Line 94: Line 138:
|}
|}


Thankfully, exploring until you find the System Core and then annihilating it isn’t too difficult in the vast majority of sites you will find in high-sec. With a little practice, you’ll be hacking with the best of them!
===Data Caches===
Data Caches act a bit like a “treasure chest.” They can contain either a “treasure” (a useful Utility Subsystem), or a “trap” (a particularly nasty Defensive Subsystem). Data Caches have to be manually opened after being exposed (single-click them), so you can safely leave the decision as to whether or not to chance their activation until later on in your hacking attempt.


== Skills ==
== Skills ==
Retrieved from "https://wiki.eveuniversity.org/Hacking"