Last Updated on: 7th January 2024, 11:44 am
Web site: www.chocolate-doom.org
Category: Games
Sub-Category: FPS
Platform: Linux, OS X, Windows, BSD, Unix-like
License: GNU GPL
Interface: GUI
Wikipedia:
First release: 2005
Chocolate Doom – a FPS game for Linux, OS X, Windows and other Unix-like operating systems.
Ideally Chocolate Doom aims to recreate the behavior of the Vanilla binaries, but different aspects of Vanilla behavior are held to varying degrees of importance. It can be imagined as different “tiers” of compatibility:
* The game and gameplay itself is of central importance. Here, the Vanilla behavior ought to be maintained as accurately as possible. This includes the look, feel and sound, and things like demo compatibility.
* The surrounding aspects of the game that aren’t part of the central gameplay experience can be extended as long as there’s a good reason and Vanilla behavior is respected.
* The setup tool is not required to reproduce the behavior of the Vanilla setup tool, even though it reproduces its look and feel.
“Vanilla” is defined as:
* DOS Doom 1.9 (although there are actually multiple “1.9”s).
* DOS Heretic 1.3.
* DOS Hexen 1.1.
* DOS Strife 1.31.
* DOS Chex Quest.
Compatibility with older versions of the DOS binaries is also a secondary goal (though not pre-release versions). Other ports (either official or unofficial) are out of scope: this includes console ports, non-DOS ports, Doom 95 and Doom 3: BFG Edition.
Chocolate Doom has been designed around a careful and deliberate philosophy that attempts to recreate the original (“Vanilla”) DOS executables for Doom, Heretic, Hexen and Strife. This document describes some of that philosophy and the reasoning behind it.
Chocolate Doom is compatible with the DOS Doom configuration file (normally named `default.cfg`). Existing configuration files for DOS Doom should therefore simply work out of the box. However, Chocolate Doom also provides some extra settings. These are stored in a separate file named `chocolate-doom.cfg`.