This page can be used for testing everything you need before uploading to a current page.

  • This page isn't protected in any way - Please preserve this message at the top of the page
  • Be respectful of other content currently on here.
  • Please copy and paste the following at the very end of each entry:

<br clear="all" />

  • Please delete any test information once completed.

Table Transclusions Edit

Reputation TablesEdit

Ranking Stats
Rank Appearance Title Reputation
Rank down when
Reputation reaches
Extra $ per
win condition
Extra B-coin per
win condition
1Rank 01 blackNoob--00
2Rank 02 blackRookie50040050020
3Rank 03 blackTalent75065080030
4Rank 04 blackSkilled1,0009001,75060
5Rank 05 blackExperienced1,2501,1503,500120
6Rank 06 blackAdvanced1,5001,4006,500220
7Rank 07 blackSenior1,7501,6509,500330
8Rank 08 blackExpert2,0001,900 12,000400
9Rank 09 blackVeteran2,2502,15027,000900
10Rank 10 blackMaster2,5002,40055,0002,000
11Rank 11 blackElite3,0002,750120,0004,000

Luminaar (talk) 17:55, November 17, 2017 (UTC)

Offensive Strategies Edit

Summary Edit

Successful hacking is central to completing missions and simulations, daily challenges, and generally progressing as a hacker. Hacks can be completed using many different programs and strategies, but programs must be sufficiently upgraded to be effective. Understanding attack priorities, the pros, cons and qualities of brute force and stealth, and the strengths, weaknesses, and unique properties of programs will inform decisions and help conquer any network.

Program Loadouts Edit


  • Pros
    • Hacks cannot be retraced as long as the visibility bar does not reach 3600 before disconnecting
    • Very few programs are needed for each hack
  • Cons
    • Programs become very expensive at higher levels
    • Wraith and Portal take a long time to compile
    • Stealth must be continually upgraded to counter rising Scanner levels on target networks

Shuriken and Shocker:

  • Pros
    • Programs are very cheap
    • Hacks can be relatively quick, compared to other brute Force methods
  • Cons
    • Shockers take 8 minutes to compile and 6 disk space per program
    • Having enough Shockers is crucial to a hack, and could be the sharp difference been success and failure

Kraken and Worm:

  • Pros
    • Very low total disk space
    • Kraken can crush strong nodes on the way to the Core while Worms deal with weaker nodes without wasting programs
  • Cons
    • Defensive programs are almost always needed to defend nodes while Kraken and Worms replicate and move along.
    • Kraken has limited use against networks with the Core near the netConnections

Portal and Maniac:

  • Pros
    • Network security can be eliminated quickly and completely if Portal is well-placed
  • Cons
    • Compilation time is extremely long and significant disk space is required
    • Other programs will be needed for a successful hack, including Access

Blaster and ICE Wall:

  • Pros
    • Very few nodes will be able to hold for long against a Blaster of reasonable level
    • Blasters greatly decrease time spent on difficult nodes such as Code Gates, the Core, and high level storages or Security Nodes.
  • Cons
    • Blaster is slow to attack, making it almost impossible to use effectively against Maelstroms or low-level nodes
    • ICE Walls become expensive very quickly, and many may be needed per hack
    • Chokepoints can be difficult to defend, and Security Nodes must be protected to prevent the network recapturing them while Blasters attack other nodes on chokepoints

Beam, Ram and Protector:

  • Pros
    • Programs are cheap to compile
    • Hacking is intuitive and relatively simple, leading to fewer mistakes
    • A good average capable of hacking almost any type of network
  • Cons
    • Battering Ram and Protector take time to compile
    • While Code Gates may not be much of an obstacle, nodes with very high firewall and protected by Guardian shields may be very difficult to capture without stronger programs

Hacking Goals Edit

Program Placement Edit

Beam Cannon

ICE Wall

  • Strong when installed on nodes with low firewall or Security Nodes which could be recaptured by the network
  • Weak when installed on nodes with poor strategic position to continue hacking


  • Strong when installed on nodes with many connections or nodes connected to one or more strong nodes of higher priority and one or more weak nodes with lower priority but more importance to continue hacking
  • Weak when installed on nodes connected to only one uncaptured node of importance

Data Leech



  • Strong against chokepoints and high firewall nodes
  • Weak against nodes with low firewall or non-threatening nodes



  • Strong when installed on nodes connected only to captured, weak, unimportant or non-threatening nodes
  • Weak when installed on nodes connected to one or more security nodes or the Core, especially with no other programs to support it



  • Strong against chokepoints and high firewall nodes
  • Weak against non-threatening nodes

Battering Ram

  • Strong against Code Gates and high firewall nodes protected by multiple strong Guardian shields
  • Weak against very low level Code Gates and Guardian shields, and useless against anything besides filters and shields.




  • Strong on chokepoints and against high firewall nodes protected by multiple strong Guardian shields
  • Weak against non-threatening or low firewall nodes

Comparison of Defensive ProgramsEdit

  • ICE Wall and Protector level 1 statistics
Program Firewall Disk Usage Install Time Regeneration
Ice Wall40020.5 secondsNone
Protector65044 seconds45.5 per second

Two ICE Walls cost the same disk space to install as one Protector. It takes an additional 3.5 seconds to install the latter, for a bonus of 45.5 firewall regeneration per second.

Comparison of Practical Usage Edit

The ICE Wall can be installed quickly on a node that was just captured, potentially saving the node and giving you time to install offensive programs. Installing offensive programs first will works for more damage, as long as the node is able to sustain enough damage. This method also allows the node to regenerate until the shield breaks. Use the first tactic on low firewall nodes such as Scanner and the Guardian.

Once installed, even though the Protector has less than the combined Firewall of 2 ICE Walls, the regeneration makes up for it as long as the Protector stays under attack for 3.3 seconds.

Efficiency Edit

Disk usage wise, 2 ICE walls equal 1 Protector.

Be aware of having both ICE Wall and Protector remaining once the node is 100% secure. If this happens, using fewer ICE Walls and letting the Protector take more damage, or using an ICE Wall instead of the Protector for cheaper costs/using less disk space would be more efficient.

References Edit

Hackers Wikia - Gameplay Topics
Gameplay Nodes Programs

World Map • Hacks • Missions • Network Logs • Simulations • Reputation 


Home Screen • Net Building • Resources • Black Market • Patch Notes 


Getting Started • Offensive Strategies • Defensive Strategies • Game Tips 

Froste (talk) 20:24, July 21, 2017 (UTC)