WizTerm32 Config File Format

Some of WizTerm32's less essential features do not have configuration commands. Anyone wishing to modify settings like colors, fonts or the logging feature needs to manually edit WizTerm32's configuration file. This file is not part of the download; rather, WizTerm32 creates this file when it is first run, if it can't find such a file.

Don't be afraid to fiddle with this file. The worst that can happen is that WizTerm32 won't work right, in which case you can restore sanity by simply deleting the configuration file.

The default name for WizTerm32's configuration file is WizTerm32.ini . You will usually find it in the same directory as WizTerm32.exe . Its structure is very simple, and you can edit it with Notepad (included with every version of Windows) or a text editor of your choice. If you use a text processing program like Microsoft Word, be sure to save the file as ASCII text, not in Word format.

Here's a WizTerm32 config file with default values, broken up and explained in sections:


These control the window position (in pixels) and state, as well as a few other things. You don't need to mess with the first five of these because dragging and pulling the window will change it just fine.
WindowState is:
  • 0 for normal (occupying part of the screen),
  • 1 for minimized (just an icon) and
  • 2 for maximized (full screen).
but again, it's much easier just to use the buttons at the top right of the window.

HorizontalSplit, if set to 1, allows you to split the screen top-to-bottom instead of left-to-right when snooping on other players.

SplitOnSnoop, if set to 0, will prevent WizTerm32 from automatically splitting the screen ($HALF) when you start to snoop on someone.

CleanScroll affects the way scrolling is done. If set to 0 and WizTerm is open but not the top window, then text scrolling in WizTerm will duplicate part of any overlying window. This looks funny but is harmless. For those who really care about such things, you can set CleanScroll to 1 and force WizTerm to use a slower but cleaner method.

LineSpacing controls how far displayed lines are apart. I find that, with settings below 2, underscores get wiped out. You may want to increase this value to space lines out more.


These are the colors for:
the status bar,
the main screen
the left side (your side) of the split screen
the right side (snooped player's side) of the split screen
the input line
and the text in most of these areas.
The mysterious 6 character strings are hexadecimal representations for the colors, with one byte (= 2 characters) for each of the colors red, green and blue. It's exactly the same system used in HTML pages. If hex is all witchcraft to you, just look up your favorite colors in this table! Just don't put any space between the digits, they need to be a solid group of 6.
FontName=Courier New

The font name needs to be one that your system knows, and it needs to be spelled exactly right. Look up your favorite font in Microsoft WordPad or some other program that gives you a choice. Be aware that if you choose a proportional font type (and most of them are, alas), the output from map and exits will look terrible. Common suitable non-proportional fonts are: 
  • Courier New and
  • Lucida Console.
FontSize is whatever you like, but be aware that not all fonts come in all sizes.

FontStyle =

  • 0 for normal,
  • 1 for bold,
  • 2 for italic,
  • 3 for bold italic.

  • WriteLogs=1 turns logging on, 0 turns it off.
  • DateLogs=1 causes today's date (YYMMDD) to be built into the log file name, e.g. BL010430.log
  • You can change LogFileName and LogExtension if you like. Stick with "normal" characters.

  • KeyPadDirs, if set to 0, will prevent WizTerm from interpreting the keys from the numeric keypad (at the very right of your keyboard) from acting as directional movement keys.
  • BareNames, if set to 1, will cause WizTerm not to put a space before or after a name inserted by an F key.
  • BreakChar is the character (or actually, the character sequence) on which WizTerm will break command sequences.
  • AlwaysBreak causes WizTerm to break input strings on the BreakChar even if those inputs are SAYs (") or other commands which WizTerm usually breaks up on BreakChar.
Sample WizTerm32.ini file

Foolproofing: If you completely mess up your .ini file and WizTerm32 won't start up any more, you can fix everything by just deleting the file. WizTerm32 will create a new one if it can't find the file.

Advanced useage: If you want to use several different configurations, copy WizTerm32.ini to another name and specify that name on the command line.

Back to Sirsloth's Wizterm Page