You're a hacker with a terminal, four terrible scripts, and an anonymous contact who needs files from places they really shouldn't be. The scripts were free, and you can tell.
Your port scanner checks all 65,535 ports, which is thorough and also going to take longer than you have patience for. Your password cracker just brute-forces everything and wakes up the intrusion detection system doing it. Both will technically get the job done, the way a spoon will technically dig a tunnel.
So you rewrite them, and the new probe only checks common ports and finishes in seconds, while the new cracker skips guessing entirely and reads the admin's own password hints straight off the filesystem. Nobody told you to fix these - you just got tired of using tools this bad.
That's Blackdoor - you write the code, the code hacks the servers, and better code hacks them faster, quieter, and before the trace catches up.
Not a hacking-themed clicker. An actual terminal.
There are no buttons, no "press X to hack", no minigames where you rotate pipes or match symbols. You sit at a command line with tab completion, a built-in code editor, and the full set of commands you'd expect - and you write scripts in a custom Python-like language that was built to be fun to learn and satisfying to master. Every script executes line by line, so you see exactly where it works, where it breaks, and how much faster it gets once you're the one who rewrote it.
If you've never programmed before, it's more sink-or-swim than a tutorial - you're straight into scripts that already work but could work better, picking up variables, loops, and functions by actually touching them. If you have, you'll skip past the basics quickly and start writing proper tooling. The language is close enough to Python that your instincts will carry over. Either way, the regulars will accidentally teach you things by arguing about it in IRC.
The Job
Your contact goes by second_hand, who operates through #blackdoor - a small IRC channel populated by hackers, script kiddies, and at least one person who thinks printing "hello" counts as a proof of concept - and doesn't do small talk. You get a server IP, a brief explanation of what's on it, "good luck", and payment on delivery.
The work escalates - unlocked test servers turn into corporate networks with intrusion detection, single-user boxes turn into multi-user environments where you crack a weak account and escalate privileges from inside, and simple downloads end up as encrypted files behind filtered ports you have to fight through first.
Every job harder than the last, solvable more than one way, with a story underneath it all about why your contact needs these files so badly - and what they plan to do with them.
Your code, your rules
There's no right answer - you get targets and tools, and how you combine them is entirely up to you.
Write a surgical probe that scans five ports and quits, or something that downloads every file on the server and sorts through it later, or just find the admin's password sitting in a text file some intern left in their home directory and skip cracking entirely - all of it works. The scripting language is simple enough to learn in minutes, deep enough that you'll still be optimising scripts hours later.
Spend your earnings on hardware upgrades (faster processing, more memory, better network) or on software tools that unlock new capabilities, or just write better code and keep the money - either way works.
SSH Isn't the Only Door
Not every server plays by the same rules, and not every lock needs the same key.
Some run web forms that hand over their whole user table to a stray quote mark, or a "diagnostics" page that quietly shells out to the OS underneath. A real browser automation API means you can script your way through a signup form as easily as an SSH session, watching it fill in and submit itself if you're looking at the right pane. Some gate the good stuff behind a file that's normally locked, only readable for a few seconds out of every cycle - keep trying, and grab it the moment it opens.
Some boxes run mail - connect on port 25, log into a mailbox, and read what people actually say to each other when they think nobody official is reading, or send a very convincing email as someone you're not and see who takes the bait.
All of it shows up as ordinary side work, posted by contacts in IRC same as everything else - just more ways for a job to go sideways.
You're not alone in here
You're never alone in #blackdoor. Hackers chat while you work - sharing tips, posting side jobs, placing bets on whether anon42 can find a port (he can't). Your contact DMs you mission briefings, and the channel reacts when jobs get done. Like any real IRC channel, most of the advice is unsolicited and some of it is wrong.
#lounge is a live channel where real players talk about anything - help, questions, scripts, general chat. It's not moderated in real time, though Steam's text filter still applies.
Share everything
Every script you write is a real file, and every server is a JSON config - edit scripts in the built-in editor, share them (or whole campaigns) through Steam Workshop, and download other players' work the same way. Anything you subscribe to shows up ready to use on your in-game drop server. No menus - just files on a server, like everything else.
Key Features
Hack servers - Probe ports, crack passwords, explore filesystems, escalate privileges, steal data. Every server has its own users, files, and weak points to find.
Race the trace - Every connection starts a countdown that speeds up the more noise you make, and getting traced ends it right there.
A real terminal - Tab completion, command history, a code editor - no theming, no skin over a menu, this is the actual interface.
Upgrade your rig - Faster hardware means faster scripts, better tools unlock new capabilities, or just save your money and write better code instead.
Story campaign - An anonymous contact, escalating jobs, a corporate conspiracy, and a secret that might be worth more than the pay.
IRC - Hackers chat, argue, and accidentally teach you things while you work, and side jobs and tips both get shared along the way.
Your approach - No fixed solution - write surgical tools or blunt instruments, find passwords in config files or brute-force them, and if you find a shortcut nobody else did, that's the point.
Live community chat - #lounge connects you to other players. Ask questions, share scripts, compare notes.
Workshop - Share scripts and entire campaigns, download community tools, and see how other people solved the same problems.
