Dirty Rebirth
A community revival of a shut-down objective shooter. Nineteen maps, including maps cut from the original game and two never publicly released.
- Maps
- 19
- Unreleased maps
- 2
- Game install
- ~8.5GB
- Analytics collected
- 0
Download
PausedDownloads are paused. We are pushing an update to the live servers. The launcher will be back here shortly — join the Discord for the word when it is.
The launcher
You download the launcher, not the game. Run the installer and you get a desktop shortcut — no admin rights needed. The launcher then signs you in with Discord, installs the game (about 8.5 GB), keeps it updated, and starts it — one button.
Windows SmartScreen may warn when you run the installer — it is new and not code-signed, so Windows has never seen it before. That is expected for a project like this.
Linux
On Linux? There's an experimental
command-line launcher ()
for Proton/Wine users. Download it, then in a terminal:
chmod +x dr-cli and ./dr-cli — it signs you in, installs
the game, and starts it under umu-run or wine. Same
requirements and the same verification as the Windows build. Run
./dr-cli doctor first to check your setup; the game needs
vcrun2013 in the Wine prefix and doctor prints the exact command.
Ask in the Discord if you get stuck.
Before you download
Playing requires a Discord account, and sign-in is checked on every launch. All three of these must be true before the launcher will let you in:
- You are a member of the project's Discord server.
- You have accepted the rules there and been approved.
- You hold the Playtester role.
If any of these is missing, sign-in will refuse you and say why. That is the gate doing its job — not a broken download. Join the Discord and get set up first.
Getting in
- Step01
Join the Discord server, accept the rules, and wait to be approved and given the Playtester role.
- Step02
Download the launcher above and run the installer. It needs no admin rights and puts Dirty Rebirth Launcher on your desktop. Have roughly 10 GB of disk free for the game.
- Step03
Sign in with Discord inside the launcher and press Play. The first run downloads the game; after that the same button updates and launches it.
What the launcher does to your machine
This mirrors the disclosure in the launcher's own Transparency tab — the tab is authoritative, and you can check every claim here against it on your own machine.
Verified content
Every build is described by a list of content blocks signed with a key only the project holds. The launcher checks that signature before downloading anything, then checks every block it receives against the signed list; anything that does not match is discarded. Whoever hosts the files cannot alter what you receive.
Signing key fingerprint: bc43344c187a415223b6e04cb844cc2d — the
launcher's Transparency tab shows the same value.
What leaves your machine
The launcher contacts exactly two places: mainframe.advancement-protocol.com
(whether you are signed in, which build is current, which servers are up) and the
content host it names in its Updates tab (game files). Nothing else is contacted,
no analytics are collected, and your play is not tracked. Your sign-in token is held
in memory only and is never written to disk.
Crash reporting is off
The original game shipped a crash reporter that uploaded memory dumps to a third-party service. Those dumps contain local file paths, which means your Windows username. It has been disabled: crash files stay on your own machine and are never sent anywhere.
Where matches run
Matches run only on the project's own servers. Players cannot host, and your game never connects to another player's machine, so no player can see another player's IP address. Your game connects to a server operated by the project and nothing else.
The game is modified
The client is a patched build: the dependency on a store client was removed so the game can start on its own, and the ability to host a match was restored in the binary — though only project servers can actually be joined, as above.
Because the executable is modified and the downloader assembles files, antivirus software may object. That is expected and is a permanent limitation of a project like this, not a sign that something is wrong.
Updates are mandatory
The launcher never downloads anything you have not asked for when automatic updates are off — but an out-of-date install cannot launch until it updates. Install, update and play are one button, so everyone plays the current build.
Anti-cheat
There is no anti-cheat system. Match results are recorded per match rather than as running totals, so a bad result can be removed without unpicking anyone's whole history.
If something fails
Sign-in refuses you
The message says which requirement is missing; the list above is the checklist. Fix it in Discord, then sign in again.
The game itself won't start
On a fresh machine, install Microsoft's Visual C++ 2013 x64 redistributable, then press Play again.
Anything else
Post in the Discord's #bug-reports with what happened and
the build number from the launcher.
Not affiliated with Splash Damage
Dirty Rebirth is an unofficial, fan-made project. It is not affiliated with, endorsed by, sponsored by, or connected to Splash Damage Ltd., Nexon, or any company involved in making or publishing Dirty Bomb.
"Dirty Bomb", "Splash Damage" and all related names, characters and artwork are the property of their respective owners. No ownership is claimed over any of it. This project exists because the original game was shut down and can no longer be bought or played.
Nobody involved here speaks for Splash Damage. Do not contact them about this project, and do not report problems with it to them.