Bottom Line: Hacknet strips away the neon 3D nonsense that Hollywood calls "hacking" and hands you a real terminal, a dead man's mystery, and a ticking clock. It's tense, smart, and occasionally cruel — a cult classic that earns its 94% every time a trace timer starts counting down.
The Gameplay Loop
The core loop is elegant and endlessly reconfigurable. You scan a target with probe, discover open ports, run the matching exploit tool against each one, crack enough of them to drop the machine's security threshold, then execute porthack to force your way in. Once inside, you ls, you cat, you scp the files that matter, and you get out. Then you do it again on a harder machine.
Described flat like that, it sounds mechanical. In motion, it isn't. The tension comes from layering the pressure. Early nodes are quiet — you can poke around, read someone's emails, feel like a voyeur. Later, breaching a system trips an active trace, and now the same calm sequence of commands becomes a sprint. You're fumbling SSHcrack 22, FTPBounce 21, watching a red bar fill, and the moment you realize you forgot which port needs which tool is the moment the game has you exactly where it wants you.
What makes this work is that the game never fakes the difficulty. When you panic-type and the trace catches you, that's not the game cheating. That's you being too slow. The feedback loop is honest, and honesty is rare in this genre.
The Interface Is the Game
Here's the design thesis, stated plainly: the friction is the feature. Hacknet refuses to hold your hand, and that refusal is doing real work. Every game that puts a "HACK" button on screen is telling you, implicitly, that the fantasy is about feeling powerful. Hacknet's terminal tells you the fantasy is about being competent. Those are different emotions, and the second one is far harder to manufacture.
The onboarding is where this bites. There's a learning curve, and the game does little to flatten it. You will, at some point, sit staring at a prompt with no idea what to type. For some players that's an intoxicating "I'm really hacking" moment. For others it's a wall. Hacknet made a choice, and it doesn't apologize for it. I respect that more than I'd respect a watered-down version — but let's be clear-eyed: this design actively filters its audience, and it does so on purpose.
Where It Wobbles
The critique that shows up in nearly every honest player review is repetition, and it's fair. Once you understand the loop, the back third of the game asks you to execute it more than it asks you to rethink it. The mid-game introduces a genuinely brilliant curveball I won't spoil — a sequence that reframes the entire interface and stands as one of the best moments in any game of this type. But outside those spikes, the difficulty curve is more of a plateau. You're not learning new verbs so much as running old ones faster.
There's also a fragility to the fiction. The illusion of a "real" system holds beautifully until you wander off the intended path, and then the seams show. This is a small studio's simulation, not an operating system, and the more you test its edges the more you feel the scripting underneath. It never breaks the spell for long, but the spell is thinner than the marketing suggests.
Still, the narrative engine keeps pulling you forward. The Bit mystery is genuinely compelling, and the game's willingness to make you complicit — to have you rifle through strangers' machines and wonder whether you're the good guy — gives it a moral texture most puzzle games never attempt.