Scroll to navigation

chocolate-hexen(6) Games Manual chocolate-hexen(6)

NAME

chocolate-hexen - historically compatible Hexen engine

SYNOPSIS

chocolate-hexen [options]

DESCRIPTION

Chocolate Hexen is a port of Raven Software's 1995 game Hexen that aims to behave as similar to the original DOS version of Hexen as possible.

GENERAL OPTIONS

Load main configuration from the specified file, instead of the default.
Load additional configuration from the specified file, instead of the default.
Load the specified PWAD files. Each succeeding argument is treated as a PWAD file name until one starts with a dash or the argument list is exhausted.
Specify an IWAD file to use.
Disable music.
Disable substitution music packs.
Disable sound effects.
Disable all sound output.
Take screenshots when F1 is pressed.
Load extra command-line arguments from the given response file. Arguments read from the file are inserted into the command line, replacing this argument. A response file can also be loaded using the abbreviated syntax '@file.rsp'.
Specify a path from which to load and save games. If the directory does not exist then it will automatically be created.
Print the program version and exit.

GAME START OPTIONS

Load the game in savegame slot s.
Disable monsters.
Monsters respawn after being killed.
Set the game skill, 1-5 (1: easiest, 5: hardest). A skill of 0 disables all monsters.
Start a game immediately, warping to MAPx.

DISPLAY OPTIONS

-1
Don't scale up the screen. Implies -window.
-2
Double up the screen to 2x its normal size. Implies -window.
-3
Double up the screen to 3x its normal size. Implies -window.
Specify the display number on which to show the screen.
Run in fullscreen mode.
Specify the dimensions of the window. Implies -window.
Specify the screen height, in pixels. Implies -window.
Disable blitting the screen.
Don't grab the mouse when running in windowed mode.
Disable the mouse.
Specify the screen width, in pixels. Implies -window.
Run in a window.

NETWORKING OPTIONS

Automatically search the local LAN for a multiplayer server and join it.
Specify player class: 0=fighter, 1=cleric, 2=mage, 3=pig.
Connect to a multiplayer server running on the given address.
Start a deathmatch game.
Reduce the resolution of the game by a factor of n, reducing the amount of network bandwidth needed.
Send n extra tics in every packet as insurance against dropped packets.
Autostart the netgame when n nodes (clients) have joined the server.
Use original network client sync code rather than the improved sync code.
Use the specified UDP port for communications, instead of the default (2342).
When running a server, don't register with the global master server. Implies -server.
In deathmatch mode, change a player's class each time the player respawns.
Start a multiplayer server, listening for connections.
When starting a network server, specify a name for the server.
Start the game playing as though in a netgame with a single player. This can also be used to play back single player netgame demos.
For multiplayer games: exit each level after n minutes.

DEHACKED AND WAD MERGING

Equivalent to "-af <files> -as <files>".
Simulates the behavior of NWT's -af option, merging flats into the main IWAD directory. Multiple files may be specified.
Simulates the behavior of NWT's -as option, merging sprites into the main IWAD directory. Multiple files may be specified.
Load the given dehacked patch(es)
Simulates the behavior of deutex's -merge option, merging a PWAD into the main IWAD. Multiple files may be specified.
Disable auto-loading of .wad files.
Ignore cheats in dehacked files.
Simulates the behavior of NWT's -merge option. Multiple files may be specified.

DEMO OPTIONS

Record or playback a demo without automatically quitting after either level exit or player respawn.
Record or playback a demo with high resolution turning.
Specify the demo buffer size (KiB)
Play back the demo named demo.lmp.
Record a demo named x.lmp.
Load a game from the given savegame slot and record a demo from it. Equivalent to -loadgame <save-num> -record <demo-name>.
Smooth out low resolution turning when recording a demo.
When recording or playing back demos, disable any extensions of the vanilla demo format - record demos as vanilla would do, and play back demos as vanilla would do.
Play back the demo named demo.lmp, determining the framerate of the screen.

COMPATIBILITY

Emulate a specific version of Hexen. Valid values are "1.1" and "1.1r2".
Specify DOS version to emulate for NULL pointer dereference emulation. Supported versions are: dos622, dos71, dosbox. The default is to emulate DOS 7.1 (Windows 98).
If provided, the check for the v1.0 IWAD file is disabled, even though it will almost certainly cause the game to crash.

OBSCURE AND LESS-USED OPTIONS

Don't allow artifacts to be used when the run key is held down.
[windows only] Save configuration data and savegames in c:\hexndata, allowing play from CD.
Read all MIDI files from loaded WAD files, dump an example substitution music config file to the specified file, and quit.
Specify the heap size, in MiB.
Use the OS's virtual memory subsystem to map WAD files directly into memory.
If specified, don't show a GUI window for error messages when the game exits with an error.
Development option to specify path to level scripts.

IWAD SEARCH PATHS

To play, an IWAD file is needed. This is a large file containing all of the levels, graphics, sound effects, music and other material that make up the game. IWAD files are named according to the game; the standard names are:

Doom, Doom II, Final Doom
Heretic, Hexen and Strife (commercial Doom engine games).
Hacx and Chex Quest - more obscure games based on the Doom engine.
The Freedoom open content IWAD files.

The following directory paths are searched in order to find an IWAD:

Any IWAD files found in the current working directory will be used in preference to IWADs found in any other directories.
This environment variable can be set to contain a path to a single directory in which to look for IWAD files. This environment variable is supported by most Doom source ports.
This environment variable, if set, can contain a colon-separated list of directories in which to look for IWAD files, or alternatively full paths to specific IWAD files.
$HOME/.local/share/games/doom
Writeable directory in the user's home directory. The path can be overridden using the XDG_DATA_HOME environment variable (see the XDG Base Directory Specification).
/usr/local/share/doom
/usr/local/share/games/doom
/usr/share/doom
/usr/share/games/doom
System-wide locations that can be accessed by all users. The path /usr/share/games/doom is a standard path that is supported by most Doom source ports. These paths can be overridden using the XDG_DATA_DIRS environment variable (see the XDG Base Directory Specification).

The above can be overridden on a one-time basis by using the -iwad command line parameter to provide the path to an IWAD file to use.This parameter can also be used to specify the name of a particular IWAD to use from one of the above paths. For example, “-iwad doom.wad” will search the above paths for the file doom.wad to use.

ENVIRONMENT

This section describes environment variables that control Chocolate Hexen's behavior.

See section “IWAD SEARCH PATHS” above.
When running in PC speaker sound effect mode, this environment variable specifies a PC speaker driver to use for sound effect playback. Valid options are “Linux” for the Linux console mode driver, “BSD” for the NetBSD/OpenBSD PC speaker driver, and “SDL” for SDL-based emulated PC speaker playback (using the digital output).
When using OPL MIDI playback, this environment variable specifies an OPL backend driver to use. Valid options are “SDL” for an SDL-based software emulated OPL chip, “Linux” for the Linux hardware OPL driver, and “OpenBSD” for the OpenBSD/NetBSD hardware OPL driver.
Generally speaking, a real hardware OPL chip sounds better than software emulation; however, modern machines do not often include one. If present, it may still require extra work to set up and elevated security privileges to access.

FILES

$HOME/.local/share/chocolate-doom/hexen.cfg
The main configuration file for Chocolate Hexen. See hexen.cfg(5).
$HOME/.local/share/chocolate-doom/chocolate-hexen.cfg
Extra configuration values that are specific to Chocolate Hexen and not present in Vanilla Hexen. See chocolate-hexen.cfg(5).

SEE ALSO

chocolate-doom(6), chocolate-heretic(6), chocolate-server(6), chocolate-setup(6)

AUTHOR

Chocolate Hexen is part of the Chocolate Doom project, written and maintained by Simon Howard. It is based on the Hexen source code, released by Raven Software.

COPYRIGHT

Copyright © id Software Inc. Copyright © Raven Software Inc. Copyright © 2005-2013 Simon Howard.

This is free software. You may redistribute copies of it under the terms of the GNU General Public License <http://www.gnu.org/licenses/gpl.html>. There is NO WARRANTY, to the extent permitted by law.

2017-11-27 Chocolate Doom 3.1.1