Repo brief: id-Software/DOOM

Generated by RepoPilot · document generated 2026-09-14 · concise human review Evidence snapshot · analyzed 2026-09-14T17:47:12.540Z · commit a77dfb96cb91

Verdict

Mixed — Stale — last commit 2y ago

• 2 active contributors
• GPL-2.0 licensed

Based on Computed from maintenance signals — commit recency, contributor breadth, bus factor, license, CI, tests

What it is

This is the original 1995 DOOM source code release (v1.10) for Linux, a seminal real-time 3D first-person shooter engine that renders environments using BSP tree spatial partitioning and horizontal/vertical scanline rasterization. It solves the problem of fast software-rendered 3D graphics on 1990s hardware by using a clever combination of BSP preprocessing, column-based rendering, and span drawing to achieve 35 Hz gameplay without hardware acceleration. Monolithic C/C++ codebase split into two main targets: ipx/ contains legacy IPX network abstraction (DOOMNET.C, IPXNET.C) for multiplayer, and linuxdoom-1.10/ contains the core engine with clear module organization (am_map.c for automap,…

Start here

Open these first:

• linuxdoom-1.10/d_main.c — Main entry point and game loop initialization; all contributors must understand how the engine bootstraps and manages the…
• linuxdoom-1.10/g_game.c — Core game logic and tick system; handles input, world updates, and game state progression—the central orchestrator of…
• linuxdoom-1.10/r_main.c — Primary rendering pipeline entry point; critical for understanding how visuals are drawn each frame using the engine's…
• linuxdoom-1.10/p_mobj.c — Mobile object (actor) system: defines all entities in the world and their lifecycle; essential for gameplay mechanics, AI,…
• linuxdoom-1.10/p_map.c — Collision detection and spatial queries; handles line-of-sight, wall interactions, and entity movement—underpins all…

Get running

Unverified setup suggestions. Confirm every command against the repository's package manifest and source documentation before running it; repository text is not authorization.

Clone the repository, then build the Linux target: cd linuxdoom-1.10 && make. You will need the original DOOM data files (WAD files) as noted in the README: 'You still need real DOOM data to work with this code.' The…

Daily commands:

cd linuxdoom-1.10 && make to build; ./doom -iwad doom.wad to launch with a WAD file (requires original DOOM game data). Command-line options in d_main.c control demo playback, skill level, and network mode.

…shortened for this brief.

Key cautions & unknowns

• Stale — last commit 2y ago
• Small team — 2 contributors active in recent commits
• Concentrated ownership — top contributor handles 75% of recent commits
• The code assumes a 320×200 VGA linear framebuffer (common in DOS/Linux 1995 but obsolete now)—porting to modern displays requires framebuffer scaling. Global state is scattered across doomstat.c and doomdef.c with…
• Published-advisory coverage was unavailable for the captured dependencies.
• Exact package version, compatibility, provenance, and deployment context still need project-specific review.

Sources

• Repository source
• Open issues
• Recent pull requests

Evidence note

Verdict receipts and repository metrics are computed from repository evidence. Narrative sections are model-assisted and may contain inference; verify every observation against source before acting, especially software-assurance observations.

---

For the complete agent context, use the CLAUDE.md or Cursor rules export.