ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng)/ProfitPress-MegaCDROM2.B6I/BBS/DOORS/GAMEST11.ZIP/GAMESTAT.CFG

Text File | 1991-10-08 | 5.8 KB | 161 lines

% GAMEstat Configuration file for v1.10
%
%
%                   Definitions of terms used in this file
%                --------------------------------------------
%
%    Declaration...  The identifying phrase of the configuration file.
%                    These are... INPUT, OUTPUT, ANSIBULL etc.  All
%                    Declarations MUST be in UPPER CASE!
%
%    Arguement.....  The data associated with the declaration.  The path
%                    to your input file would be an ARGUEMENT to the
%                    declaration INPUT.
%
%
%                             Important Notes
%                           -------------------
%    Lines beginning with '%' are commented out.
%
%    Spaces prior to a Declaration are filtered.
%
%    Spaces in between a Declaration and its Arguement are also filtered.
%
%    All declarations must be in UPPER case.  If your bulletin is showing
%    defaults then you have probably violated this!  Arguements may be in
%    either case, and will be displayed as entered in this file.
%
%    If you are getting an ERROR 199, you have a declaration without
%    supplying an arguement.  Comment that line out, dont just leave it
%    blank.
%
%
%                        Getting on with it!
%----------------------------------------------------------------------
% INPUT - input file. Make sure that this matches the echo statement in
%         your games batch files.
%
%         Default    C:\games.dat
%
  INPUT         c:\Games.Dat
%
% ---------------------------------------------------------------------
% OUTPUT - Output (ASCII) Bulletin name.
%
%          Default   Gamestat.bul in the current directory
%
  OUTPUT        e:\pb\bull5.bbs
%
%-----------------------------------------------------------------------
% ANSIBULL - Path and name for color output.
%
%            Default   NONE
%
  ANSIBULL  e:\pb\bull5.clr
%
% ----------------------------------------------------------------------
% SMALL_BULL - if the bulletin is scrolling off the screen on the user's
%              end, and the PREBULL string is not available to your bbs
%              then uncomment this line.  It will cause the "There were
%              XXXX uses" line to be ommitted shortening the output
%              bulletins (both ansi and ascii) by one line.  Note:  Error
%              199 isn't in effect as there is no arguement to this option.
%
%  SMALL_BULL
%
% ---------------------------------------------------------------------
% PREBULL - Some bbs's allow special strings in a text file that mean
%           things.  To Phoenix, a  causes a "hit any key to continue"
%           prompt after the file is displayed.  This option will put
%           characters you desire at the beginning of your output files.
%
%           Default    NONE
%
  PREBULL 
%
% ----------------------------------------------------------------------
% TITLE_NAME - This allows you to specify the title of your bulletin.
%              The text that appears after your System Name and Node
%              number is entered here.  I do not trap for the number
%              of characters so you can comment out the BBS_NAME and
%              NODE_NUMBER options to earn extra room.
%
%              Default   Online Game Summary
%
 TITLE_NAME        Top 15 door Summary
%
%-----------------------------------------------------------------------
% LISTALL - Path and file name for the complete listing
%
%           NOTE:  This file will NOT be written until you have 16 or
%                  more entries in your DATAFILE. (The first 15 are
%                  already shown in your bulletins!)
%
%           Default  NONE
%
  LISTALL e:\pb\allgames.txt
%
%----------------------------------------------------------------------
% DATAFILE - Path to the datafile that has ongoing history of the games
%            that have been played.  DO NOT confuse this with the
%            input declaration as they are two seperate files!
%            Combined with the /C option on the command line (see docs)
%            allows among other things, seperate reports per node!
%
%            Default  GAMESTAT.DAT in the current directory.
%
  DATAFILE e:\pb\gamestat.dat
%
%----------------------------------------------------------------------
% BBSNAME - Put your system name in.
%
  BBSNAME      RoyaLink BBS
%
%----------------------------------------------------------------------
% NODENUMBER - If desired. (May Be useful for future polls for national
%              averages.  Include Zone Number too!)
%
  NODENUMBER    1:206/2503
%
%----------------------------------------------------------------------
% Colors section:  Note...  if you do not specify an ANSI output, these
%                  do not matter
%
%    Values...  0 = Black       8 = Real dark white
%               1 = Dk Blue     9 = High Dark Blue
%               2 = Green      10 = High Green
%               3 = Cyan       11 = High Cyan
%               4 = Red        12 = High Red
%               5 = Purple     13 = High Purple
%               6 = Brown      14 = Yellow
%               7 = White      15 = High White
%
%
% COLOR_TITLE - the color the system name and node number line appears in.
  COLOR_TITLE       14
%
% COLOR_DATE  - The color the 'From and To dates' line appears in
  COLOR_DATE        11
%
% COLOR_STAT  - The color the ' There were xxx games ' appears in
  COLOR_STAT        13
%
% COLOR_BORDER - the frame color
  COLOR_BORDER       9
%
% COLOR_TEXT   -  the color the 'Game Name' and other text appears in
  COLOR_TEXT         7
%
% COLOR_FIRST - the color your #1 game appears in
  COLOR_FIRST       12
%
% COLOR_NEXT4 - the color the next 4 entries appear in
  COLOR_NEXT4       11
%
% COLOR_REST - the color the remaining entries appear in
  COLOR_REST         2
%
%
%   That's it.