-.PP
-There are a plethora of options available for tweaking various aspects of the
-game. All options can be set either from a configuration file or by passing
-them as arguments. Some of the more common options can be set from within the
-game.
-.PP
-A
-.B yoink
-configuration file ("yoinkrc") consists of key-value pairs organized in a
-logical hierarchy. The format of the file is human-readable, so you can get in
-there with your favorite text editor if you like to work under the hood.
-.B yoink
-looks for configuration files and loads them in this order, with the options in
-prior configuration files taking precedence over the same options if they exist
-in multiple configuration files:
-.TP
-1. $YOINKRC
-This is an optional environment variable you can set to point to a configuration
-file.
-.TP
-2. $HOME/.yoinkrc
-This is a specific user's personal configuration file.
-.TP
-3. /etc/yoinkrc
-This is the system-wide configuration file.
-.TP
-4. @DATADIR@/yoinkrc
-This is the base configuration file which should be considered read-only. Look
-to this file as an example of the format used for configuration files.
-.PP
-Options that are passed as arguments take precedence over options loaded from
-the configuration file(s). This mechanism is good for running the game with a
-temporary setting which you do not intend to retain. Keep in mind that if you
-edit and save options in-game, any options you have passed as arguments during
-the invocation of the game will be saved to the
-.I $HOME/.yoinkrc
-configuration file. You may have to go into that file and remove any options
-you didn't intend to set. When passing options as arguments, you must use the
-fully qualified name of the option if it exists in a subgroup. For example:
-.PP
-.TP
-yoink video.fullscreen=true
-Set the option
-.I video.fullscreen
-to true. This will run the game in full-screen mode.
-.TP
-yoink video.maxfps=60
-Set the option
-.I video.maxfps
-to 60. This will cap the display rate at 60Hz.
-.PP
-You can also set options with array values. Arrays can be passed on the command
-line by surrounding all the parts with square brackets and separating each part
-by a comma. For example:
-.TP
-yoink video.mode=[1024,768]
-Set the option
-.I video.mode
-to an array with numbers 1024 and 768. The video size will be 1024x768.
-.PP
-Here is a list of some of the options available:
-.TP
-.B engine.rngseed
-The number value used as a seed for the random number generator. Set this to
-make the game more predictable. This is typically only useful for debugging.
-.TP
-.B engine.timestep
-The amount of time in seconds between each update of the physics state. A value
-of 0.01 or lower is ideal for accurate physics approximations. Values that are
-much higher cause the CPU to do less work, but accuracy will suffer. Errors
-could be introduced in the game with extremely high values.
-.TP
-.B game.detail
-The level of detail. Possible values are high, medium, and low. This effects
-the number of objects drawn to the screen. A high level of detail will draw
-everything but could cause poor frame rates if the graphics driver can't keep up
-with the load. Lower levels will omit certain details which aren't crucial for
-playing the game with the benefit of higher frame rates. See the Notes for more
-ways to get good performance.
-.TP
-.B input.grab
-Takes a boolean (true or false). If true, the cursor pointer will be "stuck"
-within the area of the window, and many key combinations which would otherwise
-be handled by the window manager will instead be dropped. This is a low-level
-option of limited usefulness.
-.TP
-.B video.colorbuffers
-This takes an array of four number values which represent the number of bits to
-use for red, green, blue, and the alpha channel. This is a low-level option of
-limited usefulness. The default value is almost always preferable.
-.TP
-.B video.showcursor
-This option effects the visibility of the cursor while it is "hovering" over the
-window. If the value is true, the cursor will be visible. Otherwise, the
-cursor will be hidden.
-.TP
-.B video.doublebuffer
-If true, double-buffering will be used to render animations with minimal
-distortions. Otherwise, a single buffer will be used. The recommended value is
-true.
-.TP
-.B video.fullscreen
-If true, the window will capture the display and render the game in full screen
-splendor. A value of false means the game will run in a window.
-.TP
-.B video.maxfps
-The maximum number of frames to be drawn per second. A value of 50 is pretty
-good. If your computer is pretty old, can get away with decreasing this value
-and still have reasonably smooth animation. You can set this to a very high
-number to effectively render as many frames as is possible, but the actual rate
-could be limited by vertical display synchronization, depending on the X11
-driver and settings used. You should not set this option higher than the point
-where the vertical synchronization effectively limits the draw rate or else the
-game may not be able to update the physics on schedule which could actually
-significantly lower the quality of the animation.
-.TP
-.B video.mode
-The resolution or size of the window. The value is an array with three number
-elements representing the width, height, and bits per pixel that make up the
-video mode. A typical value is [800,600] for a size of 800x600 pixels with
-millions of colors (the third number is optional).
-.TP
-.B video.multisamplebuffers
-The number of multisample buffers used.
-.TP
-.B video.multisamplesamples
-The number of multisample samples used.
-.TP
-.B video.printfps
-If true, the current number of frames being draw per second will be printed to
-the console. This is usually off by default, but you can set this to true if
-you're interested in the draw rate you're actually getting.
-.TP
-.B video.resizable
-If true, the window will be resizable by the window manager. This option is
-meaningless if the game is drawing to the full screen.
-.TP
-.B video.swapcontrol
-If true, drawing will take place at a time which will minimize distortion caused
-by the vertical refreshing of displays. The recommended value is true.
-.br
+You have a certain level of control over the operation of \fByoink\fP
+through options passed as program arguments or given in config files.
+\fByoink\fP looks for config files in several locations and in this order:
+.TP
+1. \fI@DATADIR@/yoinkrc\fP
+This is the base config file which should be considered read-only. Look to
+this file as an example of the format used for config files.
+.TP
+2. \fI/etc/yoinkrc\fP
+This is the system-wide config file.
+.TP
+3. \fI$HOME/.yoinkrc\fP
+This is your own personal config file.
+.TP
+4. \fI$YOINKRC\fP
+This is an optional environment variable you can set to the path of a
+config file at a non-standard location. See the \fBENVIRONMENT\fP section
+below for more information.
+.PP
+As usual, options that are passed as arguments take precedence over options
+loaded from any config file. Here is a list of some of the options
+available at your disposal:
+.TP
+.B detail
+The level of detail. Possible values are 1, 2, or 3 where 1 means the
+least amount of detail and 3 means the most. This effects the number of
+objects drawn to the screen. A high level of detail will draw everything
+but could cause poor frame rates if the graphics driver can't keep up with
+the load. Lower levels will omit certain details which aren't crucial for
+playing the game with the possible benefit of higher frame rates. See the
+Notes for more ways to increase the game's performance. The default value
+is 3.
+.TP
+.B doublebuffer
+If true, double-buffering will be used to help minimize distortion and
+artifacts caused by the animation of the game. Otherwise, a single buffer
+will be used. The default value is true.
+.TP
+.B framerate
+The target number of frames to be drawn per second. If your computer is
+really old, you can get away with decreasing this value and still have
+reasonably smooth animation. You can set this to a very high number to
+effectively render as many frames as is possible, but the actual rate could
+be limited by vertical display synchronization, depending on the X11 driver
+and settings used. The default value is 50.
+.TP
+.B fullscreen
+If true, the window will capture the display and render the game in full
+screen splendor. A value of false means the game will run in a window.
+The default value is false.
+.TP
+.B resizable
+If true, the window will be resizable by the window manager. This option
+is meaningless if the game is drawing to the full screen. The default
+option is true.
+.TP
+.B showfps
+If true, the current number of frames being drawn per second will be
+printed to the console every second. The default value is false.
+.TP
+.B timestep
+The number of times per second the simulation state will be updated. A
+value of 100 or higher is ideal for a better physical simulation. Values
+that are much lower cause the CPU to do less work, but accuracy will
+suffer. Errors could be introduced in the game with extremely low values.
+The default value is 80.
+.TP
+.B videomode
+The resolution or size of the window. The value is an array with three
+number elements representing the width, height, and bits per pixel that
+make up the video mode. The third number is optional. The default value
+is {800,600}. If passing on the command-line, you may need to escape the
+curly braces so the shell doesn't parse them.
+.PP
+This is only a list of the more useful options. You'll have to use the
+source to find out about the more esoteric options, but you probably won't
+need to.
+.SH EXAMPLES
+Here are some examples of typical usage:
+.TP
+$ yoink detail=2
+Set the level of detail to 2 so that less stuff is drawn to the screen.
+.TP
+$ yoink fullscreen=true videomode=\\{1024,768\\}
+Run \fByoink\fP at full screen with a resolution of 1024x768. Notice the
+escapes for the curly braces so the shell doesn't parse them.