home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
bbsdoor
/
ironox10.zip
/
SAMPLE.CFG
< prev
next >
Wrap
Text File
|
1994-01-06
|
3KB
|
73 lines
// IRONOX.CFG -- Sample config file for Iron Ox
// This is a sample configuration file that would work on many single and
// multinode systems. Note that blank lines and comment lines (like this
// one!) are ignored. Keywords (like "Timeout" and "BBSName") must
// be flush left on a line, followed by blank space and the value you would
// like to assign to them.
// The name of the sysop who owns this game. If the game is not registered,
// this field will be ignored.
// SysopName UNREGISTERED
// The BBS on which the game is running. If the game is not registered, this
// field will also be ignored.
// BBSName UNREGISTERED
// Game registration code. See "REGISTER.FRM" for details!
// RegCode 01234567890123456789
// This value determines how long (in seconds) Iron Ox will wait for a
// keystroke before it decides that a user is "sleeping at the keyboard."
// Timeout value does not apply to local players, only to remote users.
// Note: a value of zero disables timeout. 360 (6 minutes) is the
// recommended value (Iron Ox is a game that requires some thought!).
Timeout 360
// This value determines the maximum number of games any given player can
// be involved in at one time. When you set this value, keep in mind that
// each game is likely to take three to ten minutes a day. The recommended
// setting is ten.
MaxGames 10
// This value determines whether players will be allowed to start new games.
// You will almost always want to set this value to "TRUE". The only time
// you are likely to want to use "FALSE" is if you are winding down a
// tournament with a fixed duration.
StartGames TRUE
// Determines whether the game will blank the local display during remote
// play in games in which the sysop and other local mode players are
// participating. Very useful option if you are planning to play
// competitively in games on your board, but it does make
// monitoring and maintaining the game more difficult. Change to TRUE
// to enable the feature.
Secure FALSE
// Bulletin names. Insert a name and path by the tag for a bulletin to
// indicate that you want a bulletin of that kind. Leaving a field blank
// indicates that you *do not want* to create that kind of bulletin.
// Example: WC_Records C:\WC30\BULL\BULL34.BBS
// ANSI bulletins
ANSI_Score
ANSI_Records
// ASCII bulletins
ASCII_Score
ASCII_Records
// Wildcat-style bulletins using "@" codes.
WC_Score
WC_Records