No description
Find a file
2019-01-22 19:12:59 +02:00
.github ISSUE_TEMPLATE: Add intro comment with useful links. 2018-01-28 02:00:46 -05:00
cmake cmake build fix 2018-10-29 20:21:21 +00:00
data Install icons to PREFIX/share/icons/hicolor/128x128/apps 2017-12-09 15:37:37 -08:00
man man: Generate Markdown versions of CMDLINE 2018-09-16 05:28:25 -07:00
midiproc Makefile.am: add CMakeLists.txt and win32 to EXTRA_DIST 2018-06-05 10:41:38 -07:00
opl opl: Use SDL_mixer post-mix hook for OPL output. 2018-10-24 20:03:34 -04:00
pcsound Makefile.am: add CMakeLists.txt and win32 to EXTRA_DIST 2018-06-05 10:41:38 -07:00
pkg osx: Use PACKAGE_TARNAME for autoload path. 2018-12-24 01:12:54 -05:00
src setup: Make CalibrationLabel return value const 2019-01-22 19:12:59 +02:00
textscreen textscreen: Add API to change color palette. 2018-12-28 16:27:23 -05:00
win32 Strife now boots 2018-05-09 20:07:59 -04:00
.gitignore Ignore CMake build directories 2018-05-01 21:20:44 -04:00
.lvimrc Add textscreen Doxyfile to dist. Add .desktop file to svn:ignore. Add 2010-04-30 19:38:24 +00:00
.travis.sh travis: Treat warnings as errors 2018-01-27 16:46:04 +02:00
.travis.yml travis: Remove sdl2-branch 2018-09-16 20:32:21 -04:00
AUTHORS Add Alexey to AUTHORS 2016-03-24 02:34:32 +09:00
autogen.sh build: kill redundant boilerplate in autogen.sh 2013-12-10 17:07:22 +01:00
ChangeLog Update URLs to Chocolate Doom Github project. 2014-03-16 02:43:12 -04:00
CMakeLists.txt cmake build fix 2018-10-29 20:21:21 +00:00
CODE_OF_CONDUCT.md Add Contributor Covenant as Code of Conduct. 2016-02-28 20:02:10 -05:00
configure.ac Add system-specific globbing API. 2018-10-27 17:50:14 -04:00
COPYING.md Replace COPYING with COPYING.md Markdown version. 2018-01-14 23:26:54 -05:00
HACKING.md doc: update the HACKING document with a rule for casts 2018-05-06 13:44:01 +02:00
Makefile.am Remove the codeblocks project 2018-06-13 10:56:48 -07:00
NEWS.md Remove the codeblocks project 2018-06-13 10:56:48 -07:00
NOT-BUGS.md Convert the rest of the doc files to Markdown. 2016-06-08 04:42:29 -07:00
PHILOSOPHY.md PHILOSOPHY: Minor formatting fixes 2016-11-26 21:35:08 -05:00
README.md Fixed grammer error in README.md 2017-08-04 12:44:26 -04:00
README.Music.md README.Music: add gusgonna.wad reference 2018-05-27 10:06:15 -04:00
README.Strife.md Convert the rest of the doc files to Markdown. 2016-06-08 04:42:29 -07:00
rpm.spec.in Install icons to PREFIX/share/icons/hicolor/128x128/apps 2017-12-09 15:37:37 -08:00
TODO.md Convert the rest of the doc files to Markdown. 2016-06-08 04:42:29 -07:00

Chocolate Doom

Chocolate Doom aims to accurately reproduce the original DOS version of Doom and other games based on the Doom engine in a form that can be run on modern computers.

Originally, Chocolate Doom was only a Doom source port. The project now includes ports of Heretic and Hexen, and Strife.

Chocolate Dooms aims are:

  • To always be 100% Free and Open Source software.
  • Portability to as many different operating systems as possible.
  • Accurate reproduction of the original DOS versions of the games, including bugs.
  • Compatibility with the DOS demo, configuration and savegame files.
  • To provide an accurate retro “feel” (display and input should behave the same).

More information about the philosophy and design behind Chocolate Doom can be found in the PHILOSOPHY file distributed with the source code.

Setting up gameplay

For instructions on how to set up Chocolate Doom for play, see the INSTALL file.

Configuration File

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.

The configuration can be edited using the chocolate-setup tool.

Command line options

Chocolate Doom supports a number of command line parameters, including some extras that were not originally suported by the DOS versions. For binary distributions, see the CMDLINE file included with your download; more information is also available on the Chocolate Doom website.

Playing TCs

With Vanilla Doom there is no way to include sprites in PWAD files. Chocolate Dooms -file command line option behaves exactly the same as Vanilla Doom, and trying to play TCs by adding the WAD files using -file will not work.

Many Total Conversions (TCs) are distributed as a PWAD file which must be merged into the main IWAD. Typically a copy of DEUSF.EXE is included which performs this merge. Chocolate Doom includes a new option, -merge, which will simulate this merge. Essentially, the WAD directory is merged in memory, removing the need to modify the IWAD on disk.

To play TCs using Chocolate Doom, run like this:

chocolate-doom -merge thetc.wad

Here are some examples:

chocolate-doom -merge batman.wad -deh batman.deh vbatman.deh  (Batman Doom)
chocolate-doom -merge aoddoom1.wad -deh aoddoom1.deh  (Army of Darkness Doom)

Other information

  • Chocolate Doom includes a number of different options for music playback. See the README.Music file for more details.

  • More information, including information about how to play various classic TCs, is available on the Chocolate Doom website:

    https://www.chocolate-doom.org/

    You are encouraged to sign up and contribute any useful information you may have regarding the port!

  • Chocolate Doom is not perfect. Although it aims to accurately emulate and reproduce the DOS executables, some behavior can be very difficult to reproduce. Because of the nature of the project, you may also encounter Vanilla Doom bugs; these are intentionally present; see the NOT-BUGS file for more information.

    New bug reports can be submitted to the issue tracker on Github:

    https://github.com/chocolate-doom/chocolate-doom/issues

  • Source code patches are welcome, but please follow the style guidelines - see the file named HACKING included with the source distribution.

  • Chocolate Doom is distributed under the GNU GPL. See the COPYING file for more information.

  • Please send any feedback, questions or suggestions to chocolate-doom-dev-list@chocolate-doom.org. Thanks!