macOS
Homebrew Caskverifiziert · 100%
brew install --cask doomsday-enginelocal Homebrew cask metadata
cask
doomsday-engine mit Homebrew Cask installieren
Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für doomsday-engine in AI-Agent-Workflows.
Installation
Weitere Installationsbefehle
Überblick
Paketzusammenfassung
Enhanced source port of Doom, Heretic, and Hexen
Projektlinks
Befehle und Aliase
In der lokalen Paketdatenbank wurden keine Executable-Aliase gefunden.
Verlauf
Projektgeschichte und Nutzung
Doomsday Engine is an enhanced, modular source port for Doom, Heretic, and Hexen on Windows, macOS, and Linux.
Projektgeschichte
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.
Adoptionsgeschichte
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.
Wie es verwendet wird
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.
Warum Paket-Nerds sich dafür interessieren
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.
Zeitleiste
- 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
Quellen
Sicherheitslage
Noch keine Protected-Tool-Abdeckung gefunden
Für doomsday-engine wurde kein passendes lokales Secret-Handling-Manifest gefunden. Paketmetadaten bleiben hier veröffentlicht, damit künftige Abdeckung eine stabile Paket-URL hat.
Installationsverhalten
- In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
- Es wurden keine Homebrew-Bottle-Metadaten erfasst.
Empfohlene Prüfung
Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.
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
Installierte Executables
| Befehl | Art | Sichtbarkeit | Hinweis |
|---|---|---|---|
| Es waren keine Executable-Daten vorhanden. | |||
Aktualität
Version und Aktualität
Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.
Seite generiert2026-11-04
Manager-Version2.3.1
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt
- InfoNo package-manager update timestamp was available.niedrig Konfidenz
- InfoRelease/tag comparison is only available for GitHub repositories.https://dengine.net/none Konfidenz
Installationsmetadaten
Paketmetadaten
| Paketschlüssel | cask:doomsday-engine |
|---|---|
| Version | 2.3.1 |
| Paketmanager | Homebrew Cask |
| Paketmanager-Seite | https://formulae.brew.sh/cask/doomsday-engine |
| Homepage | https://dengine.net/ |
| Upstream-Dokumentation | https://dengine.net/ |
| Quellarchiv | https://files.dengine.net/archive/doomsday_2.3.1_x86_64.dmg |
| SHA-256 | 2966e93058969177005d6acf233c434fee9b82e6e92b34dfdda8ea0a7fcaa136 |
| Bottle | nicht erfasst |
| Homebrew post-install | nicht definiert |
| Dienst | keiner deklariert |
Registry-Fakten
Details aus der Quelldatenbank
| Source Database | Homebrew cask API |
|---|---|
| Tap | homebrew/cask |
| Full Token | doomsday-engine |
| Names |
|
| Artifacts | |
| Deprecated | no |
| Disabled | no |
Quellspur
Aus Repository-Daten generiert
Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.
Combined YAML source
View the package source record on GitHub.
Verwendete Quellen
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- package relationship graph
- package version freshness
- package-page enrichment