Network Isolation

Network isolation is a shield around your gateway. While it is up, your gateway refuses every incoming connection — nobody can connect to you, no matter how long their bounce chain is. It is the closest thing to going dark on the network.

Network Isolation Buying a Package

Isolation is sold in the shop as packages. Each purchase places a package file in your /packages directory — copies of the same package stack into a single file with a counter, and packages cannot be deleted, renamed or edited. One copy buys one shield window:

PackageShield duration per copy
network_isolation_8h.pkg8 hours
network_isolation_16h.pkg16 hours
network_isolation_24h.pkg24 hours

Activating the Shield

Open the isolation key on the Connection Map (top-left row) and run one of your packages — or run the .pkg file directly from your file manager. A terminal connects to the Hackerz Online Network Security service, engages the shield, and reports how long the isolation will last. The copy is consumed when the shield goes up.

While your gateway is isolated, the isolation key on the Connection Map shows your remaining time. Everyone else only sees that a gateway is isolated — the world map and address book mark isolated machines with a shield — but the exact moment the shield drops is visible to you alone.

The Rules

  • One shield at a time. While a window is live, a new package is refused until the remaining time has burned down under 10% of the new package's own duration — an 8-hour copy is refused while more than 48 minutes remain, a 16-hour one while more than 1 h 36 m remain, a 24-hour one while more than 2 h 24 m remain. The refusal tells you exactly when to retry, and the copy is not consumed.
  • Windows never stack. When a new package is accepted, its timer starts from now and replaces whatever was left of the previous window — it does not add to it.
  • The switch runs hot. For 10 minutes after your last outbound connection you cannot raise the shield at all — activation is refused with a "network switch is running hot" message.
  • Dialing out drops the shield. The moment one of your connections touches another player's machine — as the target or as a bounce hop — your isolation ends immediately. Chains that only touch NPC machines keep the shield intact. The game asks you to confirm before you dial a chain that would drop it.
  • Refused connections cost nothing. A knock that never starts neither drops your shield nor heats the switch.

What Attackers See

Anyone trying to connect to an isolated gateway is simply refused: the target is "temporarily isolated from the network". The refusal happens before any other check — blacklists, subnet gates and password cracks never even come into play. Your firewall log stays quiet about attempts that were bounced by the shield.

Tip: When to Isolate
Raise the shield before logging off for the night, right after a profitable heist, or whenever you suspect your IP is burned. A backtrace may have already handed your IP to someone's firewall log — isolation does not erase that, but it makes the address useless until the shield drops.
Risk: The Shield Only Stops Incoming Calls
Isolation does not hide you — it only refuses connections. The moment you dial out to another player, the shield is gone, and the 10-minute switch cooldown means you cannot raise it again right away. Plan your moves first, then isolate; do not expect to duck back under the shield mid-run.
← Back to Game Mechanics