# Cataclysm: Dark Days Ahead: a turn-based survival roguelike you install from a package or build from source > Cataclysm: Dark Days Ahead is an open source, turn-based survival game set in a procedurally generated post-apocalyptic world. It ships as a large C++ codebase with ncurses and SDL builds, and its documentation covers packaging, compilation and contribution rather than a managed runtime. **CleverRaven/Cataclysm-DDA** — Cataclysm - Dark Days Ahead. A turn-based survival game set in a post-apocalyptic world. - Repository: https://github.com/CleverRaven/Cataclysm-DDA - Website: http://cataclysmdda.org - Stars: 13,271 · Forks: 4,658 - Language: C++ - License: NOASSERTION - Published: 2026-09-21 · Updated: 2026-09-21 · Language: en - Canonical page: https://hysenlabs.com/projects/cleverraven-cataclysm-dda ## What Cataclysm: Dark Days Ahead actually simulates The README frames the project as a turn-based survival game in a post-apocalyptic world, and it pushes back on the label people reach for first: while some describe it as a zombie game, the README says there is far more to Cataclysm than that. The world is persistent and procedurally generated, and the loop is scavenging the remains of a dead civilization for food, equipment, or a vehicle with a full tank of gas. Combat ranges from zombies to giant insects, killer robots, and, in the README's phrasing, things far stranger and deadlier, plus other survivors who want what you have. That description matters for adoption because it sets the scope. This is not a short session game with a discrete win state. It is a simulation with many interacting systems, and the repository reflects that: data/, gfx/, lang/, src/, tests/, tools/ and doc/ sit at the top level, which tells you content, tilesets, translations, engine code and documentation are all versioned together in one tree. If you want a survival game where the interesting decisions are inventory, body state, crafting chains and movement over a tile map, this is the target audience. If you want action combat, it is the wrong tool, and the README's own framing is the evidence. ## How the codebase is put together and how a turn resolves The repository is C++ with a Makefile and a CMakeLists.txt at the root, plus CMakeModules/, CMakePresets.json, pch/ and msvc-full-features/ for the Visual Studio path. Game content lives in data/, artwork in gfx/, and translations in lang/. Tests live in tests/ with a tests_bat.bat for Windows. The Makefile header is the clearest statement of the architecture in the repository: it lists build types including Debug (the default, no optimizations), Release via RELEASE=1, and Tiles via TILES=1, which switches from ncurses to SDL. Sound requires SDL, so the Makefile states TILES=1 SOUND=1 together. The turn-based claim is structural rather than cosmetic. Because the build can target ncurses or SDL, the simulation and the presentation are separated: the same world logic runs behind a text interface or a tiles interface. That separation is why tilesets are a data concern in gfx/ rather than a rendering rewrite. It also explains the Makefile's breadth of targets, from NATIVE=linux64 and NATIVE=osx to NATIVE=emscripten, and cross-compilation prefixes such as CROSS=i686-pc-mingw32-. The practical consequence for a reader deciding whether to adopt: you are choosing a build configuration, not just a download, and the flags you pass determine whether you get a terminal game or an SDL one. ## Installing Cataclysm: Dark Days Ahead on Linux, or compiling it yourself The README's packaging section is the fastest path on Linux. Arch users install from the community repos, and the README gives both the ncurses and tiles package names: ```bash sudo pacman -S cataclysm-dda sudo pacman -S cataclysm-dda-tiles ``` Fedora users install from the official repos with a single package, which the README does not split into curses and tiles variants: ```bash sudo dnf install cataclysm-dda ``` Debian and Ubuntu users get two packages from the official repos, one for each interface: ```bash sudo apt install cataclysm-dda-curses cataclysm-dda-sdl ``` Flatpak is also listed, pointing at Flathub for org.cataclysmdda.CataclysmDDA. There is no install command for it in the README, only the Flathub page. After install, the README's first real use is the tutorial: it lives under the Special menu on the main menu, and the README warns that due to many code changes the tutorial may not function. In-game documentation is reached with the ? key. If you build from source instead, the README points at doc/c++/COMPILING.md for general recipes and doc/c++/COMPILER_SUPPORT.md for supported compilers, with separate guides for MSYS2, vcpkg and CMake (the CMake guide is marked unofficial). The Makefile header shows the shape of a build: RELEASE=1 for optimizations, TILES=1 for SDL instead of ncurses, and SOUND=1 alongside TILES=1 for audio. The source can also be taken as a .zip archive or cloned from the repository. ## The tutorial warning and the experimental release cadence Two things in the README should give a prospective player pause. The first is its own note on the tutorial: it sits in the Special menu, and the README states plainly that due to many code changes the tutorial may not function. A project that documents its own onboarding path as possibly broken is telling you something about how fast the content moves relative to the documentation. The in-game ? key is the fallback, and the README treats it as the real reference. The second is the release cadence. The releases listed run cdda-experimental-2026-09-21-0103 and cdda-experimental-2026-09-21-0004 on the same day, with a stable tag 0.I-1 dated 2026-09-20. Experimental builds are cut frequently, which is consistent with a project whose last push was on 2026-09-21 and which maintains a general build matrix in CI. For a player, that means the experimental channel is a moving target: content, balance and save compatibility can shift between builds. The stable tag is the conservative choice. The README does not document a rollback procedure or a save migration path, so anyone planning a long-running world should treat the release channel as a decision, not a default. ## Cataclysm: Dark Days Ahead vs Bright Nights and other forks The related searches around this project include Cataclysm: Bright Nights and cataclysm dda vs bright nights, so the fork question is one people actually ask. The available documentation does not describe Bright Nights' design, and I will not invent that. What the README does establish is the upstream side of the comparison: Cataclysm: Dark Days Ahead is the CleverRaven repository, it is the project the README describes, and it is the one with the packaging entries, the COMPILING guides and the stable 0.I-1 tag. Any fork comparison has to start from which tree you are pulling, because a fork's differences are defined against this baseline. A more useful comparison for someone choosing a game rather than a repository is scope. The README lists systems that go well past survival staples: mutations appear in the related searches, tilesets are a supported data concern, and mods are part of the ecosystem. That breadth is the reason the codebase is large and the reason the tutorial can drift. If you want a smaller, more tightly scoped variant, a fork is a legitimate answer, but you should verify its release channel and save compatibility yourself, because the README does not document any fork's behaviour. ## Licence, contribution and the cost of staying current The README states the project is the result of contributions from over 1000 volunteers under the Creative Commons Attribution ShareAlike 3.0 license, and that the code and content are free to use, modify and redistribute for any purpose. It also notes that some code distributed with the project is not part of the project and is released under different software licenses, with those files carrying their own notices. The repository bears this out: LICENSE.txt sits alongside LICENSE-Apache-Robot-Font.txt and LICENSE-OFL-Terminus-Font.txt, so bundled fonts are under separate terms. The GitHub metadata reports the license as NOASSERTION, which is a signal to read LICENSE.txt rather than trust a label. This is not legal advice; if you plan to redistribute a build, the per-file notices are what you need to check. Upgrade cost follows from the cadence. If you track experimental builds, you are re-downloading frequently and accepting that saves and content can move under you. If you stay on a stable tag such as 0.I-1, you trade new content for a fixed target. Building from source adds the toolchain cost the README's guides describe, plus the dependency wrangling the Makefile acknowledges with flags like LOCALIZE=0 to disable gettext and BACKTRACE=0 where backtrace support is unavailable. None of that is unusual for a C++ game of this size, but it is real work, and the README does not promise a simpler path. ## Conclusion Adopt Cataclysm: Dark Days Ahead if you want a turn-based, procedurally generated survival simulation and you are comfortable reading in-game documentation rather than a polished tutorial. Do not adopt it if you need a stable save-compatible experience across versions or a graphical onboarding path, because the README warns that the tutorial may not function after code changes and the project ships rapid experimental builds. Before committing, verify which release channel you are installing (stable 0.I-1 or an experimental build), check the packaging status for your distribution, and read doc/c++/COMPILING.md if you intend to build from source. ## FAQ ### What is Cataclysm: Dark Days Ahead? It is a turn-based survival game set in a post-apocalyptic world, with a persistent, procedurally generated world you scavenge for food, equipment and vehicles. The README notes that while some call it a zombie game, there is far more to it than that. ### How do I download and install Cataclysm: Dark Days Ahead? You can install it from distribution packages on Arch, Fedora, Debian and Ubuntu, get it from Flathub, or download releases from cataclysmdda.org. The source is also available as a .zip archive or by cloning the GitHub repository. ### How do I play Cataclysm: Dark Days Ahead? The README points to a tutorial under the Special menu on the main menu, though it warns the tutorial may not function due to many code changes. In-game documentation is available with the ? key, and you can generate a world from the World menu with Create World. ### Is Cataclysm: Dark Days Ahead still being developed? Yes. The repository is not archived, the last push was on 2026-09-21, and experimental builds were released the same day, with a stable tag 0.I-1 dated 2026-09-20. ### How do I install Cataclysm: Dark Days Ahead on Debian or Ubuntu? The README gives a single apt command that installs both interfaces: sudo apt install cataclysm-dda-curses cataclysm-dda-sdl. The curses package is the terminal build and the sdl package is the tiles build. ### How does Cataclysm: Dark Days Ahead compare with Bright Nights? The README does not describe Bright Nights, so no design comparison can be drawn from it. What it does establish is the upstream baseline: this repository carries the packaging entries, the COMPILING guides and the stable 0.I-1 tag that a fork is defined against. ## Sources - [CleverRaven/Cataclysm-DDA on GitHub](https://github.com/CleverRaven/Cataclysm-DDA) - [Issues](https://github.com/CleverRaven/Cataclysm-DDA/issues) - [Project website](http://cataclysmdda.org) - [README](https://github.com/CleverRaven/Cataclysm-DDA/blob/master/README.md) - [Releases](https://github.com/CleverRaven/Cataclysm-DDA/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/cleverraven-cataclysm-dda