This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them. Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.
[In the latest in a series of Gamasutra-exclusive bonus material originally to be included in Bill Loguidice and Matt Barton's new book Vintage Games: An Insider Look at the History of Grand Theft Auto, Super Mario, and the Most Influential Games of All Time, the authors investigate the origins, permutations, and legacy of Rogue, one of the most quietly influential and long-lived games ever created. Previously in this 'bonus material' series: Elite, Tony Hawk's Pro Skater, Pinball Construction Set and Pong.]
Rogue: Exploring the Dungeons of Doom (aka Rogue), created in the early 1980s by Michael Toy and Glenn Wichman, is an intriguing game for many reasons. For one, it's still being actively played, ported, enhanced, and forked two decades later -- a fact that challenges its description as just a "vintage" or "retro" game.
It's also among a scant handful of games that have achieved worldwide recognition despite originating on UNIX, a platform better suited for science and industry than computer games.
Indeed, many UNIX terminals lack all but the most basic audiovisuals, so Rogue and the majority of other games for the platform have to rely on text or "character-set graphics," which is to say pictures made up of characters like = and .
It's also important to consider the community in which Rogue originated. Programmers like Toy and Wichman had a different background than most developers of commercial games, who were (and are) primarily concerned with making profit.
Whereas developers like Richard Garriott (see book Chapter 23, "Ultima (1980): The Immaculate Conception of the Computer Role-Playing Game") and Roberta Williams (see book Chapter 11, "King's Quest: Quest for the Crown (1984): Perilous Puzzles, Thorny Thrones") would have thought it crazy to share the source code of their bestselling games with their competitors, many UNIX developers (especially those in academic settings) tended to freely share their programs and their code.
Rogue and many of its derivatives rely entirely on character-set graphics to depict dungeons and monsters. Shown here is a battle between the player's character (the "@" symbol) and a kobold (represented by the "K").
The money was assumed to be in the hardware, not the software. Hardware companies modified UNIX as they saw fit, but it soon became apparent that an industry-wide standard was needed to ensure compatibility.
AT&T and Bell Labs, who owned UNIX, began to license closed-source versions of UNIX for commercial use, but other companies banded together to create open-source alternatives. One of these was BSD UNIX, developed at the University of California at Berkeley, where Michael Toy was a student.
One important feature of BSD UNIX was Ken Arnold's curses, a library of functions for drawing pictures on the screen using a terminal's character set. Although there were certainly serious uses for curses, it was also a great tool for making games.
Toy and Wichman, who were schoolmates at the time, had already dabbled in game development before, creating text adventures, among other small projects. Curses inspired them to create a "graphical" role-playing game, which would depict dungeons from a top-down perspective.
The monsters, treasures, traps, and other objects would be represented by certain symbols; Z for zombie, for instance. The player's character was an @ -- perhaps a play on "where you're at." However, the graphics routines, while certainly innovative, weren't the game's most distinguishing feature; procedurally generated -- or created on the fly -- dungeons were.
Shown here is Rogue Clone IV, which shows what the game could look like using the IBM PC's character set and basic color.
 The BSD UNIX distribution 4.2 in 1980 included a binary version of Rogue, allowing for wide distribution, which is the pivotal release event we'll use for initial dating. See http://users.tkk.fi/~eye/roguelike/rogue.html.
 A "fork" occurs when a programming project splits off into separate projects, usually controlled by different groups of programmers.
 Also written "Unix".
 A similar scenario played out for many home users who utilized the popular CP/M operating system standard of the late 1970s and early 1980s, which had few, if any, graphical features in its myriad implementations. Naturally, CP/M was a target for many roguelike developments, including the commercial Nemesis from SuperSoft (1981).
 See book Chapter 25, "Zork: Text Imps versus Graphics Grues" for more on text adventures.