User:Koddestia Kud Usoko: Difference between revisions

Line 30:

|}

The {{co|#9ef37c|(Faction)}} in the above site and container names will be the local pirate group for each region. For a list of {{co|#9ef37c|(site)}} names, see .

The {{co|#9ef37c|(Faction)}} in the above site and container names will be the local pirate group for each region. For a list of {{co|#9ef37c|(site)}} names, see [[List of data and relic sites]].

You'll have to hack into the containers first by playing the [[hacking|hacking minigame]]. In order to attempt a hack, you’ll need to lock on to the container and activate the corresponding hacking module. The module (Relic Analyzer in a Relic Site, Data Analyzer in a Data Site, or Integrated Aanalyzer for both) only works if the distance between the container and your ship is less or equal to the module's maximum activation range. Activating the module will open a new window containing the hacking minigame. Failing to hack a container twice will destroy it and its contents.

@@ Line 30: / Line 30: @@
 |}
-The {{co|#9ef37c|(Faction)}} in the above site and container names will be the local pirate group for each region.  For a list of  {{co|#9ef37c|(site)}} names, see .
+The {{co|#9ef37c|(Faction)}} in the above site and container names will be the local pirate group for each region.  For a list of  {{co|#9ef37c|(site)}} names, see [[List of data and relic sites]].
 You'll have to hack into the containers first by playing the [[hacking|hacking minigame]]. In order to attempt a hack, you’ll need to lock on to the container and activate the corresponding hacking module. The module (Relic Analyzer in a Relic Site, Data Analyzer in a Data Site, or Integrated Aanalyzer for both) only works if the distance between the container and your ship is less or equal to the module's maximum activation range. Activating the module will open a new window containing the hacking minigame. Failing to hack a container twice will destroy it and its contents.