The Game Guide · Chapter 2
The anatomy of a hack. Every session on this network is the same shape: find a target, chain across the map, dial in, beat the race, take what you came for, erase yourself, and leave before the alarm. This chapter walks the whole shape — including the parts that go wrong.
Four sources, four different flavors of target:
L4 chip means a tougher machine), and — rarely — other players who are scanning at the same time. The catch is printed on the scanner itself: "While scanning, you might acquire IPs of other hackers, other hackerz might acquire your IP as well."A chain is the route your connection travels, and only its last address is knocked on — every hop before it just relays your traffic. You build it in the Connection Manager: add hops from your address book, or drag links directly on the world map (set your home first, then drag from pin to pin; double-tap pulls a hop back out).
How long the chain may be is your hop budget, granted by RAM and Network hardware — with none installed you still get a single hop. The manager refuses a hop and always says why: the chain is full, the IP is already in it (no loops), the target blacklisted you, the target is isolated, or the IP belongs to your own alliance.
The moment you are inside, two clocks run. CRACK is how long you need to break the target's password. TRACE is how long the target needs to trace the connection back to your IP. Win by five seconds or more and the machine is yours. Lose and you are blacklisted.
What pushes each clock:
The full table lives in the wiki's Password Cracking & Backtracing page. In play it feels like this: the TRACE chip turns red and starts breathing under thirty seconds, and for the last ten it beeps every second — wherever you are in the app. The Disconnect key breathes with it. Plan your exit before you dial.
Access granted turns the login page into the machine's menu. The command rail carries your tools; the app tabs show what the target actually serves:
A running tool dims its key and refuses a second press until it answers — crack and scan take seconds, and a double tap is a second command you did not mean to send.
Disconnect on your own terms and the session ends in a report. The verdict is the title: a golden "HACK SUCCESSFUL!" or a warning-orange "UNOPTIMAL HACKING SESSION" if the trace got too close. Three bars — ACCESS GRANTED, LOGS CLEARED, REMOTE SCAN — fill one by one, and every bar that finishes at 90% or better rolls a reward. The tiles land with a coin-fall sound; the Claim key lights when the last one lands. Sometimes the roll comes up empty. Not every heist pays — that is what the next one is for.
If the TRACE chip wins, the target hangs up on you and the dialog is not a failure — it is a sentence: "X traced you back and blacklisted you. Its logs show the visit." There is no retry button, because retrying a door that just closed cannot work. For the next 24 hours that gateway is dead to you: the address book row turns red with a live countdown, and the map pin wears a red X.
A plain connection failure is friendlier — the gateway's own refusal, with Retry, Whois and Dismiss. And remember the target is a player: they get a notification when they blacklist you, your IP sits in their log, and they can bookmark you from it. Every heist has a witness; the only question is whether the record survives.