The people around the dungeon
The games survived because people kept passing them around.
source patch
\ /
\ /
.-+---+-.
| net |
'---+---'
|
+------+------+
| | |
player port maintainer
| |
story release
The network as a workshop
Brouwer’s Hack archive preserves the circumstances of a release sent across Usenet in pieces. It also records the creation of a dedicated discussion group after the game attracted enough traffic. Distribution, questions, bug reports and arguments lived close together.
Hack’s original postings and newsgroup history
NetHack’s credits and Angband’s history make the collective work visible: ports, patches, new maintainers and people whose small contribution outlived the machine they used to make it.
Angband maintainers and variants
Watching someone think
Stone Soup’s early history describes the importance of public servers. The game could be watched and discussed. Scores and traces of earlier players gave a solitary expedition a social setting.
The resulting stories are often extremely specific. A corridor, a nearly empty wand, a remembered mistake. You do not need a cinematic replay to understand why someone is still annoyed about that door.
Seven days
The Seven Day Roguelike challenge offered a small enough frame to finish an experiment. Cogmind’s 2012 prototype and HyperRogue’s expanded 2012 version show two different outcomes. One concentrated on a replaceable robot body; the other on the consequences of unfamiliar geometry.
Neither should be confused with the much larger game subsequently built around it.
Naming the form
The Berlin Interpretation came out of a 2008 developer gathering. Its list of characteristics is a useful historical document, not a law that every reader has to adopt. Even its introduction cautions against treating missing characteristics as an automatic exclusion.
Here, the scope is practical: traditional turn-based exploration and combat, with position, uncertainty and the risk of losing a run. The game entries explain important exceptions and modes.