Can It Run Doom? The Ultimate Doom Port Archive. Devices running Doom.

Archive filters

Tags

Counts show projects with this tag added, before any legacy result limit.

Selected tags
Popular tags
More filters
Authors (match any)

Esoteric Doom ports

10 projectsShowing 1–10

  • Preview of Doom Without Headers as port for Turing Complete game

    Doom Without Headers as port for Turing Complete game

    Doom is compiled without using the C standard library or any header files, relying solely on compiler built-ins and manually defined interfaces. The project demonstrates an extreme minimalist approach to building a fully functional Doom executable while eliminating traditional C dependencies.

  • Preview of SQLDoom

    SQLDoom

    The original Doom's game logic and renderer, both implemented as SQL queries.

  • Preview of DuckDB-DOOM

    DuckDB-DOOM

    DuckDB-DOOM runs Doom entirely inside DuckDB by expressing the game loop as SQL queries executed through DuckDB-Wasm in the browser. It demonstrates that a modern analytical database engine can serve as an unconventional runtime for a classic game.

  • Preview of Regex find-and-replace (a 544-rule Markov machine)

    Regex find-and-replace (a 544-rule Markov machine)

    A computer whose only instruction is a global regex substitution. The entire machine is one 96.6 MB string: registers, RAM, the framebuffer and the DOOM engine all live in it as plain text. A driver applies a fixed, ordered set of 544 find-and-replace rules in a loop; the first rule that matches fires once, and that is one step. Nothing else computes. DOOM is compiled onto the machine via doomgeneric and ELVM. One frame of E1M1 is 13,994,067 substitutions and comes out byte-identical (SHA-256) to natively compiled DOOM.

  • Preview of Constexpr Doom

    Constexpr Doom

    Constexpr-Doom is a C++20 project that interprets a WebAssembly (WASM) build of Doom entirely inside a constexpr evaluation — meaning the game executes at compile time, and the rendered ASCII art frame is baked into the binary as a compile-time constant.

  • Preview of Doom running inside a TrueType font

    Doom running inside a TrueType font

    It’s a DOOM-style raycaster where the font’s TrueType hinting bytecode does all the 3D wall rendering - JavaScript just handles input and paints pixels The whole font is 6,580 bytes. 13 functions. No WebGL, no Canvas API for the math - just the hinting instruction set that was designed for adjusting serif widths in the 90s Live demo (Chrome/Edge): https://4rh1t3ct0r7.github.io/ttf-doom/ Press Tab for debug mode - you can watch the font-variation-settings axes update as you move around

  • Preview of DNS TXT records

    DNS TXT records

    A compressed Doom WAD was stored in the freeform TXT field of DNS queries stored on Cloudflare and read into memory. TXT records are usually meant for data about a website domain.

  • Preview of DOOM in pure SQL

    DOOM in pure SQL

    DOOMQL: A DOOM-like multiplayer shooter in pure SQL

  • Preview of Doom Bookmarklet

    Doom Bookmarklet

    DOOM original C (1997) wrapped in Rust, compiled to Wasm, embedded in TypeScript which is transpired to JS, polyfilled, minified, wrapped in some scaffolding, and saved to the bookmarks/favourites bar of a browser.