10 Open Source Roguelikes That Refuse to Die (And Why Devs Keep Forking Them)

NetHack was built collaboratively in 1987. Angband needed a coordinated relicensing effort decades later. Pixel Dungeon was declared complete and immediately forked into dozens of variants. This is how roguelikes work—they don't die, they fork.

10 Open Source Roguelikes That Refuse to Die (And Why Devs Keep Forking Them)

TL;DR

  • Roguelikes have been developed collaboratively since before most people had internet access
  • Games like NetHack (1987) and Angband still get active updates in 2026
  • When developers declare projects "complete," communities fork them into dozens of variants
  • The genre thrives on public iteration, shared servers, and contributors who refuse to let good systems stall

The Big Picture

NetHack was built collaboratively over networked systems in 1987. Angband required a coordinated relicensing effort decades later just to become fully open source. Pixel Dungeon was declared "complete" and immediately forked into dozens of new games.

This is how roguelikes work. They don't die. They fork.

The genre emerged from Rogue, a Unix-era experiment built for character-based terminals around 1980. By the early 1990s, Usenet communities like rec.games.roguelike were trading variants and philosophies. That collaborative DNA never left. Today, events like the 7DRL challenge (build a complete roguelike in seven days) and the annual Roguelike Celebration keep the same spirit alive—fast iteration, public testing, ideas that leave lasting marks.

Recently, a developer built an experiment that turns GitHub repositories into roguelike dungeons. That idea came from a genre that has been evolving in the open for decades, shaped as much by players as by developers. Many of the games that defined roguelikes are still actively maintained today, with contributors refining systems, debating mechanics, and layering in new ideas over time.

Here are 10 open source roguelikes that started small and never stayed that way.

Cataclysm: Dark Days Ahead — Simulation That Never Stops Growing

Cataclysm: Dark Days Ahead drops you into a world where everything has already collapsed. Cities sit abandoned, labs hum with leftover experiments, forests reclaim the edges. You scavenge while hunger, injury, weather, and time keep pressing in.

It started as a fork of Cataclysm and never really stopped growing. Contributors kept layering in new systems until the simulation reached a kind of sprawling completeness. You can wire in cybernetics, mutate into something barely recognizable, or assemble an armored vehicle from salvage. None of it is scripted. It all emerges from the rules underneath.

The level of detail spills into the community, where players argue about nutrition, crafting logic, and what should realistically exist in pull requests. The simulation is so deep that contributors regularly debate real-world physics just to get a mechanic right.

NetHack — Four Decades of Vindictive Dungeon Logic

NetHack was first released in 1987 as a fork of Hack, which grew out of Rogue's dungeon-crawling experiments. It drops you into a dungeon packed with shrines, traps, cursed gear, and monsters that seem personally invested in your downfall. Every object follows its own rules, and those rules collide in ways that feel almost vindictive.

After decades of contributions, the game is dense with edge cases and hidden mechanics. Curiosity rarely goes unpunished. The deeper you go, the more the dungeon seems to anticipate whatever terrible idea you are about to try next.

NetHack 5.0.0 was just announced in 2026, proving that even after nearly four decades, the dungeon is still finding new ways to surprise people. The release notes capture the game's strange, systemic humor: illiterate heroes who receive a spellbook from their deity get the spell shoved directly into their mind, fleeing leprechauns bury their gold after teleporting, and monsters can blind you with a camera.

The "Net" in NetHack comes from how it was built. It's one of the earliest games developed collaboratively over the internet, with contributors coordinating across networks long before modern open source workflows existed.

Dungeon Crawl Stone Soup — When Communities Refuse to Let Projects Stall

Dungeon Crawl Stone Soup unfolds across a network of dungeon branches, each tuned to test a different kind of mistake. Lairs full of beasts, vaults packed with threats, deeper levels that stop pretending to be fair. You choose a species, a background, maybe a god to follow, and your choices carry through everything that comes after.

You can play offline or on public servers, where other players' ghosts appear and people watch games unfold in real time. It's a shared space as much as a dungeon. Resources stay tight, every decision stacks, and you deal with the outcome.

Dungeon Crawl Stone Soup is what happens when a community refuses to let a project stall. Forked in 2006 to revive a slowing codebase, it's still evolving today—sometimes by adding features, sometimes by deleting them. That willingness to remove systems that don't serve the design is rare in open source gaming.

Angband — The Relicensing That Changed Everything

Angband stretches downward from a quiet town into a massive dungeon tied to decades of development. Each level pushes deeper toward a final confrontation that has defined runs for generations. A steady contributor base keeps refining mechanics while variants and forks branch off in different directions.

It traces its lineage back to Moria in the 1980s. Forks spun out into dozens of variants—some tweaking balance, others rebuilding systems or shifting the setting entirely. Ideas move between them, get reworked, and show up somewhere else a few years later.

Angband didn't start fully open source. It took a coordinated relicensing effort in 2009 to get there. Decades of contributors had to align to make it happen, turning one of the oldest roguelikes into something the community could truly take forward.

With the transition to GitHub, Angband's development split into distinct branches: a stable mainline and experimental offshoots. This shift led to what David L. Craddock describes as an "explosion of productivity," with new versions appearing almost nightly. These development branches functioned like a "secret lab," where the dev team could freely experiment without risking the integrity of the official release.

Brogue Community Edition — Clarity That Spawned a Mod Scene

Brogue presents a dungeon built with clarity and intent. Rooms connect in ways that funnel you into decisions you cannot ignore. Light drops off into darkness, fire spreads through terrain, gas drifts, and the environment joins every fight. Each floor feels deliberate, with just enough unpredictability to keep you alert.

That clarity has led to a surprisingly active mod scene, with dozens of community variants experimenting on top of the same foundation—some adding new monsters and items, others reworking pacing, visuals, or the feel of a run entirely.

The original Brogue stopped receiving official updates years ago, but the community didn't leave it there. Development continued as Brogue Community Edition, with contributors picking up the codebase and still shipping new releases today.

Pixel Dungeon — Declared Complete, Immediately Forked

Pixel Dungeon is structured as a series of quick-hit layers. Sewers give way to prisons, then caves, then worse. Every level adds a small twist—a trap, a new enemy, a bad surprise behind a door you probably should not have opened. Built as a free passion project with no monetization hooks, it leans on tight design and fast pacing.

Pixel Dungeon went open source in 2014 and was declared "complete" a year later. The community took that as a starting point, not an ending. Dozens of forks and variants spun up and are still being updated today.

Shattered Pixel Dungeon is the most prominent fork. It started as a small balance mod and quietly turned into a full game over years of continuous updates. A decade later, it's seen dozens of releases, millions of downloads, and is widely considered one of the best open source games out there—all while sticking to pure roguelike principles with no permanent upgrades, just better decisions each run.

DRL — When a Trademark Notice Speeds Up Open Source

DRL runs through military bases and hell-infested corridors filled with familiar threats and very loud intentions. Tight levels, heavy weapons, and encounters that escalate fast. The structure stays turn-based, but the pressure feels immediate. Built in Free Pascal and fueled by 90s shooter DNA, it delivers short runs that hit hard and end fast if you hesitate.

DRL started life as "Doom, the Roguelike," before a trademark notice forced a rename—ironically speeding up its transition to open source. It's been evolving since the early 2000s and still gets updates today, all while turning one of the fastest FPS games ever made into a turn-based roguelike that somehow keeps the same intensity.

KeeperRL — Build the Dungeon, Break the Heroes

KeeperRL begins underground, where you carve out rooms, lay traps, and build a dungeon designed to break incoming heroes. The surface world pushes back with raids, while your minions train, craft, and occasionally cause problems of their own. You can step in directly for tactical combat or let the systems play out.

Fire spreads, creatures react, and the dungeon develops a personality that reflects your decisions. KeeperRL leans hard into its open source roots. You can buy the full version by donating to wildlife charities, grab a completely free ASCII build if you prefer a terminal experience, and even get help from the developer compiling it yourself.

HyperRogue — When Geometry Becomes the Enemy

HyperRogue spreads across dozens of strange lands where geometry refuses to cooperate. Paths diverge in unexpected ways, space expands faster than expected, and returning to a familiar spot takes more precision than it should. Each region introduces its own rules, enemies, and hazards, all layered on top of that shifting foundation.

Built on hyperbolic geometry, its world expands faster than intuition can track. Paths that seem parallel drift apart, returning to a previous location requires deliberate precision, and positioning against enemies forces you to learn a new spatial logic under pressure. Movement alone becomes a skill you have to learn.

HyperRogue doubles as a long-running research project. Its developer continuously experiments with hyperbolic geometry, adding new lands, mechanics, and systems that explore how games behave when the rules of space itself change.

What This Changes For Developers

What stands out across all of these projects is how active they still are. People are adding systems, revisiting old decisions, and pushing mechanics into weird corners just to see what holds up. Some have evolved with updated graphical interfaces, others stay true to their terminal roots, and a few let you switch between both.

The same thing is happening around them too, in tools like Ghostty, Charm's suite, and Ratatui, where the terminal keeps getting stretched in new directions. Tight loops, visible systems, communities that don't drift away. That's what keeps roguelikes here—and the CLI is built on the same foundation.

These projects also demonstrate something valuable about contributing to open source. You don't need to build something from scratch. You can fork an existing project, refine a system, or add a single mechanic that changes how the game feels. Many of the most successful roguelikes started as small forks that grew into full games over years of iteration.

The roguelike community has been doing this since before GitHub existed. They coordinated over Usenet, built games collaboratively before modern version control, and kept projects alive through decades of contributor turnover. The tools have changed, but the approach hasn't.

The Bottom Line

Play these if you want to see how open source gaming actually works. Skip them if you need a game that ends. The real opportunity here is not just playing—it's studying how these projects stay alive. They fork when they stall. They delete features that don't serve the design. They let contributors experiment in branches without breaking the main release.

These projects don't die. They just get forked. And that's exactly how open source is supposed to work.

Source: GitHub Blog