HN Debrief

Game Engine White Papers Commander Keen

  • Programming
  • Gaming
  • Open Source
  • Hardware

The post is a long-form reverse-engineering book about Commander Keen’s engine, published free on the web and explicitly modeled on Fabien Sanglard’s Game Engine Black Books. It digs into the code and rendering tricks behind one of the first smooth-scrolling PC platformers, a feat that stood out because late-1980s PCs lacked the console-style graphics hardware that made this kind of movement cheap elsewhere.

If you build technical content, there is still strong demand for deep source-level explanations of old systems, especially when they teach durable engineering constraints. If you borrow a well-known format or visual identity, make the attribution unmistakable up front or the packaging will distract from the work.

Discussion mood

Strongly positive and nostalgic. People liked getting a serious code-level look at Commander Keen and saw it as a worthy addition to the retro engine analysis canon. The only sustained friction was over how closely the site and book mimic Fabien Sanglard’s presentation, though that softened once it became clear the homage was known to and accepted by him.

Key insights

  1. 01

    Why consoles scrolled and PCs struggled

    The hardware gap was not raw CPU power. Consoles like the SNES described scenes as tiles and sprites in video memory, then dedicated display logic assembled each frame on the fly. On a DOS PC, the CPU often had to rewrite framebuffer pixels directly. That makes smooth scrolling expensive unless you avoid touching most of the screen, which is exactly why Keen’s partial redraw approach was such a breakthrough.

    When you compare systems, look at the rendering model before you compare clock speed. If your product depends on moving lots of pixels or data, architecture can dominate compute.

      Attribution:
    • mrob #1 #2
    • wk_end #1
  2. 02

    Carmack's trick was simpler than demo-scene timing hacks

    Comparisons to Commodore 64 smooth-scrolling tricks are useful up to a point, but they can also overstate the magic. The C64 needed cycle-exact timing and hardware abuse like DMA delay. VGA packed pixels made smooth scrolling on the IBM PC much more straightforward to address, and that simplicity is part of why id could turn the idea into a practical engine instead of a one-off effect.

    Do not confuse a clever result with the hardest possible implementation path. Sometimes the win comes from spotting a hardware mode that makes the problem tractable enough to ship.

      Attribution:
    • bonzini #1
    • deaddodo #1
    • _the_inflator #1
  3. 03

    The branding issue was real but fixable

    People were right that the visual similarity creates confusion on first click. What changed the read is that the preface openly frames the book as an homage, the source history suggests direct collaboration, and Sanglard himself responded positively. That shifts the problem from plagiarism to packaging. The content can be above board and still need clearer front-page attribution.

    If you publish in a recognizable house style, put the provenance at the top, not in the preface. Clear labeling protects the work from an avoidable trust tax.

      Attribution:
    • fabiensanglard #1
    • charlietran #1
    • sasas #1 #2
  4. 04

    Use both id history books carefully

    The book discussion pulled in two overlapping accounts of id Software history: Masters of Doom and Doom Guy. The useful note is not just that both are worth reading. It is that they disagree on some details, especially around Romero-era stories, so they function better as complementary perspectives than as a single canonical timeline.

    When you lean on founder-era stories to explain technical history, cross-check the narrative source. Memoir and reported history often diverge on the same event.

      Attribution:
    • hbn #1
    • vunderba #1
    • evilturnip #1

Against the grain

  1. 01

    The homage still reads as misleading

    Even accepting good faith, the presentation was close enough that some readers genuinely thought they were looking at a Fabien Sanglard release. That criticism survives the later clarification. Consent from the inspiration does not remove the reader-confusion problem if the first impression points to the wrong author.

    Judge borrowed branding by first-glance attribution, not by intent. If a busy reader can misidentify the creator, the design needs another pass.

      Attribution:
    • wk_end #1 #2
  2. 02

    EPUB should be easy from LaTeX sources

    One reader asked for an EPUB edition, and another pushed back on the idea that this would be a major lift given the project is already open source in LaTeX. The point is practical. Once the structure exists in a source format, limiting distribution to PDF is often a choice, not a hard technical constraint.

    If you release long technical writing, ship at least one reflowable format alongside PDF. It expands where and how people can actually read the work.

      Attribution:
    • Waterluvian #1
    • jzelinskie #1

In plain english

C64 ↩
Commodore 64, a popular 1980s home computer known for highly constrained but flexible graphics hardware.
DMA delay ↩
Direct Memory Access delay, a timing-based hardware technique used on the Commodore 64 to shift display behavior in ways the original design did not directly expose.
DOS ↩
Disk Operating System, a family of older operating systems associated with early IBM PC software.
EPUB ↩
A reflowable ebook file format designed to adapt text to different screen sizes and reading devices.
Fabien Sanglard ↩
A programmer and author known for detailed reverse-engineering books and articles about classic game engines.
framebuffer ↩
A block of memory that stores the actual pixel values for the image currently being shown on screen.
IBM PC ↩
The original personal computer platform and its compatibles that became the standard DOS and Windows hardware family.
id Software ↩
The video game studio that created Commander Keen, Wolfenstein 3D, Doom, and Quake.
LaTeX ↩
A text-based document preparation system widely used for producing structured technical books and papers.
packed pixels ↩
A graphics format where pixel color values are stored sequentially in memory, making direct pixel access simpler than in planar formats.
PDF ↩
Portable Document Format, a fixed-layout document format that preserves exact page appearance across devices.
smooth scrolling ↩
A way of moving a game camera continuously across a scene rather than jumping one tile or screen at a time.
SNES ↩
Super Nintendo Entertainment System, a 1990s game console with dedicated hardware for tiles, sprites, and scrolling.
VGA ↩
Video Graphics Array, a graphics standard for IBM PCs that introduced 256-color packed-pixel modes and other display features.

Reference links

Related retro engine analyses

Books and historical context

  • Masters of Doom
    Recommended as a readable history of id Software and the origin story behind Commander Keen’s scrolling breakthrough.
  • Doom Guy
    Suggested as a complementary memoir that challenges parts of Masters of Doom and adds more detail on Ion Storm and Daikatana.

Hardware and graphics explainers

Source and attribution references