
Game Overview
A stark neon grid becomes the battlefield for a one-person revolt against corporate control, where every hacked terminal can either fund your survival or trigger a lethal response. 868-BACK frames its cyberpunk rebellion through the lens of a tightly designed tactical roguelike: you infiltrate hostile networks, steal valuable data, and try to survive long enough to cripple the systems that keep the MegaCorps in power. The atmosphere is cold, minimalist, and oppressive rather than cinematic, with its sparse presentation putting full emphasis on tense decisions and the mounting pressure of a compromised run. Death is permanent, so even a seemingly minor mistake can end a promising assault.
Each mission unfolds on compact, turn-based network maps filled with terminals, security threats, money, and dangerous opportunities. Moving, hacking, and deploying acquired progs all cost turns or resources, while enemy activity escalates as you attract attention, making greed just as dangerous as poor positioning. Stolen programs act as your toolkit, granting attacks, defensive tricks, movement options, and ways to manipulate the board, but their effects and costs demand careful planning instead of reckless button pressing. Progress comes from learning the systems, unlocking more useful options, and recognizing when to cash out, push deeper, or cut a run short before corporate security overwhelms you.
What makes 868-BACK memorable is how much strategy it extracts from an intentionally stripped-down interface. Its abstract visuals and concise runs give it the clarity of a board game, while its unpredictable combinations of progs, escalating enemy spawns, and resource choices create the improvisation associated with the best roguelikes. Fans of Michael Brough’s other minimalist designs, or players who enjoy the tactical compression of Hoplite and the risk management of classic roguelikes, find plenty to master here. It suits veterans looking for demanding, repeatable strategy sessions most of all, though newcomers willing to accept frequent failure can appreciate its clean rules and satisfying moments of calculated digital sabotage.
Screenshots
Installation
- Select the Download button at the top of this page to open UploadHaven.
- On UploadHaven, wait for any countdown, then select Free Download. Optional: UploadHaven Pro for faster downloads.
- When complete, extract the archive to a 868-BACK folder using 7-Zip.
- Open the extracted folder and start the game normally.
- For errors, check Setup Guide & Troubleshooting below. Keep your security software enabled.
System Requirements
- OS: Windows 10
- Processor: Dual Core CPU – 2.4 GHz+
- Memory: 4 GB RAM
- Graphics: 512 MB VRAM, Vulkan 1.0 or OpenGL 3.3
- Storage: 600 MB available space
Setup Guide & Troubleshooting
How do I fix missing DLL errors for 868-BACK?
After extracting 868-BACK, navigate to the _Redist or _CommonRedist folder inside the game directory and install DirectX, Vcredist, and any other dependencies included.
What should I do if the downloaded file is corrupted?
The full archive is 466.31 MB — make sure your download completed fully before extracting. Use 7-Zip to extract the files. If you still see a "file corrupted" error, re-download and try again.
Do I need to run the game as administrator?
Usually, no. Start the game normally from the extracted folder. If you see a permissions or save error, check that the folder is writable and follow the game's documented fix. Only grant administrator access when a trusted game's specific setup requires it.
How do I update my GPU drivers for this game?
The game won't launch — what should I try?
Check that extraction completed and your PC meets the system requirements. Note any error message before choosing a fix. If it identifies a missing runtime, install the required DirectX components or Microsoft Visual C++ Redistributable from Microsoft.
My antivirus is blocking the game — is it safe?
A warning needs to be investigated; the download source alone cannot confirm that a file is safe. Keep your security software enabled and review the detection details. Do not run or restore a flagged file unless you have verified that it is a false positive. If you are unsure, leave it quarantined.