Differences between Vanilla Doom and Chocolate Doom

Jump to: navigation, search

A number of differences between Vanilla Doom and Chocolate Doom. This page details such differences.

[edit] Removed functionality

This is a list of features which are present in Vanilla Doom, but not in Chocolate Doom.

Feature	Justification
DOS version	Obsolete OS
IPX networking	Obsolete protocol; multiplayer functionality is provided using UDP.
Null modem (sersetup) support	Functionality is available by using PPP to tunnel TCP/IP
Dial-up modem (sersetup) support	Dial-up modems obsoleted by broadband connectivity; functionality is available by using PPP to tunnel TCP/IP
Statistics driver	Unused feature of Vanilla Doom. Relies on DOS's lack of memory protection.

This is a list of features which, while present in Chocolate Doom, behave differently to Vanilla Doom.

Feature	Notes
Multiplayer connectivity	Chocolate Doom uses client/server multiplayer architecture instead of peer to peer as Vanilla Doom does. This means that the server must stay up for the duration of the game or all the players will get disconnected upon server shutdown.

This is a list of DOS utilities which have alternate functionality in Chocolate Doom.

Utility	Chocolate Doom alternative	Notes
novert	novert option in chocolate-doom.cfg	Disables vertical mouse movement
dehacked	Dehacked functionality built in to the engine	Allows modification of game behavior
Doom 'v1.91' hack	Doom 1.91 demo format support built in	Allows demos to be recorded without reducing turning resolution.
deutex/deusf	Command line options to support WAD merging capability	Used by some TCs to merge WADs into the main IWAD.
nwt	Command line options to support WAD merging capability	Used by some TCs to merge WADs into the main IWAD.