pkg.soopen package index

cask

Install doomsday-engine with Homebrew Cask

Enhanced source port of Doom, Heretic, and Hexen. Version 2.3.1 via Homebrew Cask; verified from local package data.

Install commandSecurity notes

install

Additional install commands

macOS

Homebrew Caskverified · 100%
brew install --cask doomsday-engine

local Homebrew cask metadata

overview

Package summary

Enhanced source port of Doom, Heretic, and Hexen

Commands and aliases

No executable aliases were found in the local package database.

history

Project history and usage

Doomsday Engine is an enhanced, modular source port for Doom, Heretic, and Hexen on Windows, macOS, and Linux.

Project history

Jaakko Keränen began the project in May 1999 as JHexen, an OpenGL-enhanced Windows port of Raven Software's released Hexen source code. The first versions appeared in late 1999 and early 2000.

During 2000, study of the related Doom, Heretic, and Hexen codebases led the project to extract their common systems into a game-independent engine. The resulting Doomsday Engine uses game modules while sharing rendering, audio, input, networking, and other infrastructure.

Adoption history

Doomsday grew from a Hexen-focused OpenGL port into a shared engine for Doom, Heretic, and Hexen. Official distribution has included Windows and macOS applications, Linux packages, distribution repositories, and Flatpak builds.

Its audience includes players seeking enhanced graphics and modern controls as well as mod authors using packages, definitions, plugins, and the engine's scripting facilities.

How it is used

Players provide compatible Doom, Heretic, or Hexen game data, select a game profile, and launch it through Doomsday's frontend. Configuration covers controls, rendering, audio, data-file paths, packages, and persistent interface state; command-line response files support repeatable launch profiles.

Why package nerds care

Doomsday is a long-running example of the source-port ecosystem that followed commercial release of classic game-engine source code. Its modularization of several related games into one engine is especially relevant to maintainers packaging shared runtime code separately from copyrighted game data.

The project also spans several packaging eras: manually installed ports, distribution packages, automated development builds, a graphical frontend, and Flatpak delivery.

Timeline

  • 1999: Jaakko Keränen began JHexen in May; the first versions followed later that year.
  • 2000: The project broadened into the game-independent Doomsday Engine.
  • 2012: The 1.9 series moved major platform services from SDL to Qt and C++.
  • 2017: Doomsday 2 introduced a redesigned Home interface and package-oriented workflows.
  • 2019: Version 2.2 added further scripting and modding facilities plus Flatpak distribution.

Related projects

  • Doom
  • Heretic
  • Hexen
  • JHexen
  • jDoom
  • jHeretic

security posture

No protected-tool coverage found yet

No matching local secret-handling manifest was found for doomsday-engine. Package metadata is still published here so future coverage has a stable package URL.

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • No Homebrew bottle metadata was recorded.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

macOS
~/Library/Application Support/Doomsday Engine/runtime/persist.pack
Unix
~/.doomsday/paths~/.doomsday/defaults

executables

Installed executables

CommandKindExposureNote
No executable data was present.

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-11-04
manager version2.3.1
manager updated
local dataok
upstreamnot checked
latest detectednot detected

https://dengine.net/

  • infoNo package-manager update timestamp was available.low confidence
  • infoRelease/tag comparison is only available for GitHub repositories.https://dengine.net/none confidence

install metadata

Package metadata

Package keycask:doomsday-engine
Version2.3.1
Package managerHomebrew Cask
Package manager pagehttps://formulae.brew.sh/cask/doomsday-engine
Homepagehttps://dengine.net/
Upstream docshttps://dengine.net/
Source archivehttps://files.dengine.net/archive/doomsday_2.3.1_x86_64.dmg
SHA-2562966e93058969177005d6acf233c434fee9b82e6e92b34dfdda8ea0a7fcaa136
Bottlenot recorded
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew cask API
Taphomebrew/cask
Full Tokendoomsday-engine
Names
  • Doomsday Engine
Artifacts
App
2
Target
2
Zap
1
Deprecatedno
Disabledno

package graph

Links come from deterministic package relationships, av.db category and tag curation, ecosystem matches, and package hub membership.

Same workflow

  • crispy-doomLocal package facts share a topical domain. Shared terms: doom, engine, enhanced, heretic, hexen.
  • chocolate-doomLocal package facts share a topical domain. Shared terms: doom, engine, heretic, hexen, port.
  • dsda-doomLocal package facts share a topical domain. Shared terms: doom, engine, port, source.

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment