chocolate-hexen(6)

πŸŽ€ chocolate-hexen(6) β€” the Games Manual, but make it slay πŸŽ€

okay so bestie, this is chocolate-hexen(6), straight out of the Games Manual section. Buckle up, it's a long one β€” grab a snack πŸ“.


✨ NAME ✨

chocolate-hexen β€” a historically compatible Hexen engine. Yes, the Hexen. The 1995 Raven Software one. We're keeping it vintage, no cap πŸ’œ

🌈 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. Like, obsessed with accuracy. That's the whole vibe. πŸ¦‹

πŸ‘‘ GENERAL OPTIONS πŸ‘‘

  • -config file β€” load the main configuration from the file you picked, instead of the default one.
  • -extraconfig file β€” load additional configuration from the file you picked, instead of the default.
  • -file file ... β€” load the PWAD files you list. Every argument after this one gets treated as a PWAD file name β€” right up until one of them starts with a dash, or you just run out of arguments.
  • -iwad file β€” specify an IWAD file to use.
  • -nomusic β€” music? off. πŸ’€
  • -nomusicpacks β€” substitution music packs? also off.
  • -nosfx β€” sound effects? gone.
  • -nosound β€” all sound output, disabled. Silence, but make it fashion.
  • -ravpic β€” take screenshots whenever you press F1.
  • -response file β€” load extra command-line arguments from the given response file. The arguments read from the file get inserted into the command line, replacing this argument. You can also pull in a response file with the abbreviated syntax '@file.rsp'.
  • -savedir directory β€” specify a path to load and save games from. If that directory doesn't exist, it gets created automatically. She's self-sufficient πŸ’…
  • -version β€” print the program version and bounce.

πŸ”₯ GAME START OPTIONS πŸ”₯

  • -loadgame s β€” load the game sitting in savegame slot s.
  • -nomonsters β€” monsters? disabled.
  • -respawn β€” monsters respawn after being killed. chaotic energy honestly.
  • -skill skill β€” set the game skill, 1-5 (1: easiest, 5: hardest). A skill of 0 disables all monsters.
  • -warp x β€” 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.
  • -display x β€” specify the display number on which to show the screen.
  • -fullscreen β€” run in fullscreen mode.
  • -geometry WxH β€” specify the dimensions of the window. Implies -window.
  • -height H β€” specify the screen height, in pixels. Implies -window.
  • -noblit β€” disable blitting the screen.
  • -nograbmouse β€” don't grab the mouse when running in windowed mode.
  • -nomouse β€” disable the mouse.
  • -width W β€” specify the screen width, in pixels. Implies -window.
  • -window β€” run in a window.

πŸ¦‹ NETWORKING OPTIONS πŸ¦‹

  • -autojoin β€” automatically search the local LAN for a multiplayer server and join it.
  • -class n β€” specify player class: 0=fighter, 1=cleric, 2=mage, 3=pig. (pig. icon behaviour, honestly.)
  • -connect address β€” connect to a multiplayer server running on the given address.
  • -deathmatch β€” start a deathmatch game.
  • -dup n β€” reduce the resolution of the game by a factor of n, which cuts down the amount of network bandwidth needed.
  • -extratics n β€” send n extra tics in every packet as insurance against dropped packets.
  • -nodes n β€” autostart the netgame when n nodes (clients) have joined the server.
  • -oldsync β€” use the original network client sync code rather than the improved sync code.
  • -port n β€” use the specified UDP port for communications, instead of the default (2342).
  • -privateserver β€” when running a server, don't register with the global master server. Implies -server.
  • -randclass β€” in deathmatch mode, change a player's class each time the player respawns. main character energy, constantly ✨
  • -server β€” start a multiplayer server, listening for connections.
  • -servername name β€” when starting a network server, specify a name for the server.
  • -solo-net β€” start the game playing as though in a netgame with a single player. You can also use this to play back single player netgame demos.
  • -timer n β€” for multiplayer games: exit each level after n minutes.

πŸ’œ DEHACKED AND WAD MERGING πŸ’œ

  • -aa file ... β€” equivalent to "-af <files> -as <files>".
  • -af file ... β€” simulates the behavior of NWT's -af option, merging flats into the main IWAD directory. Multiple files may be specified.
  • -as file ... β€” simulates the behavior of NWT's -as option, merging sprites into the main IWAD directory. Multiple files may be specified.
  • -deh file ... β€” load the given dehacked patch(es).
  • -merge file ... β€” simulates the behavior of deutex's -merge option, merging a PWAD into the main IWAD. Multiple files may be specified.
  • -noautoload β€” disable auto-loading of .wad files.
  • -nocheats β€” ignore cheats in dehacked files.
  • -nwtmerge file ... β€” simulates the behavior of NWT's -merge option. Multiple files may be specified.

πŸŽ€ DEMO OPTIONS πŸŽ€

  • -demoextend β€” record or playback a demo without automatically quitting after either level exit or player respawn.
  • -longtics β€” record or playback a demo with high resolution turning.
  • -maxdemo size β€” specify the demo buffer size (KiB).
  • -playdemo demo β€” play back the demo named demo.lmp.
  • -record x β€” record a demo named x.lmp.
  • -recordfrom save-num demo-name β€” load a game from the given savegame slot and record a demo from it. Equivalent to -loadgame <save-num> -record <demo-name>.
  • -shortticfix β€” smooth out low resolution turning when recording a demo.
  • -strictdemos β€” 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. no extra frills, periodt.
  • -timedemo demo β€” play back the demo named demo.lmp, determining the framerate of the screen.

⭐ COMPATIBILITY ⭐

  • -gameversion version β€” emulate a specific version of Hexen. Valid values are "1.1" and "1.1r2".
  • -setmem version β€” 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).
  • -v10override β€” if provided, the check for the v1.0 IWAD file is disabled.
bestie, listen to me: that -v10override one will almost certainly cause the game to crash. It's right there in the manual. You've been warned πŸ’€

🧚 OBSCURE AND LESS-USED OPTIONS 🧚

  • -artiskip β€” don't allow artifacts to be used when the run key is held down.
  • -cdrom [windows only] β€” save configuration data and savegames in c:\hexndata, allowing play from CD.
  • -dumpsubstconfig file β€” read all MIDI files from loaded WAD files, dump an example substitution music config file to the specified file, and quit.
  • -mb mb β€” specify the heap size, in MiB.
  • -mmap β€” use the OS's virtual memory subsystem to map WAD files directly into memory.
  • -nogui β€” if specified, don't show a GUI window for error messages when the game exits with an error.
  • -scripts path β€” 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.wad, doom1.wad, doom2.wad, tnt.wad, plutonia.wad β€” Doom, Doom II, Final Doom
  • heretic.wad, hexen.wad, strife.wad β€” Heretic, Hexen and Strife (commercial Doom engine games).
  • hacx.wad, chex.wad β€” Hacx and Chex Quest: more obscure games based on the Doom engine.
  • freedm.wad, freedoom1.wad, freedoom2.wad β€” The Freedoom open content IWAD files.

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

  • Current working directory β€” any IWAD files found in the current working directory will be used in preference to IWADs found in any other directories.
  • DOOMWADDIR β€” 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.
  • DOOMWADPATH β€” 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.

  • DOOMWADDIR
  • DOOMWADPATH

See section "IWAD SEARCH PATHS" above.

  • PCSOUND_DRIVER β€” 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).
  • OPL_DRIVER β€” 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 🌸

ok so here's where all your lil settings live bestie, and yes they're tucked away in your home directory like the little secrets they are πŸ’–

  • $HOME/.local/share/chocolate-doom/hexen.cfg β€” this is the main character of config files, the one and only main configuration file for Chocolate Hexen. go read hexen.cfg(5) if you wanna know more, iykyk πŸ“–
  • $HOME/.local/share/chocolate-doom/chocolate-hexen.cfg β€” and this one? this is the extra lil stash of configuration values that are specific to Chocolate Hexen and not present in Vanilla Hexen. it's giving bonus content. check chocolate-hexen.cfg(5) for the deets ✨

🫢 SEE ALSO 🫢

go read these too, bestie, they're all part of the family:


πŸ‘‘ AUTHOR πŸ‘‘

Chocolate Hexen is part of the Chocolate Doom project, and it was written and maintained by Simon Howard β€” absolute legend behaviour, no cap πŸ’…

It's based on the Hexen source code, which was released by Raven Software. iconic lineage fr fr πŸ¦‹


ok legal moment, pay attention:

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. (yeah, all caps NO WARRANTY, that's them yelling it, not me 😭)


and that's the whole page, bestie!! πŸŽ€

this was Chocolate Doom 3.1.1, dated 2017-11-27, and the page itself is chocolate-hexen(6). slay, go frag some things, drink water, and don't forget to save your config πŸ’–βœ¨πŸŒΈ