Beijing Paradise BBS Backup/PARADISE.ISO/software/BBSDOORW/MBANK214.ZIP/MAXIBANK.CFG

Text File | 1993-03-27 | 13.6 KB | 378 lines

%  eliminating all these comments will save diskspace and initialization
%  overhead. Comments start with "%" and blank lines are comments.
%
%  If your system is using ALIAS names instead of real names and
%  you want the bank accounts to use the alias names instead of the
%  real names, then use this next variable. This may be important if
%  users want to transfer time and they only know other users by their
%  alias names and not their real names.
%

%   Alias_Name

%
%
%  This option allows users to transfer time in their accounts to anybody
%  else's account. User's will be asked whom they wish to transfer time
%  to and can also search the users names for word fragments. Newusers,
%  that is users who have never made any deposits or withdrawals will
%  not have access to this function because they don't actually have
%  an account till they withdraw or deposit some time in an account.
%  If you are not allowing users to transfer time, then edit the included
%  MaxiBank.Hlp file and delete the section about transferring time. Item
%  number "5".

   Transfer-OK

%
%  Minimum Length of a search string when searching through user
%  names for a match.  This can prevent users from wasting a lot
%  of online time searching for single letter matches. Optional.
%  NOTE: Don't set this variable too high, 3 is a good value.
%

   MinSearch 3

%
%
%
%  By default MaxiBank allows a total of 60 minutes of transfers per
%  day, if the Transfer-OK variable is in use. You can set a transfer limit
%  with this next variable if you want allow less than 60 minutes per
%  day. NOTE: You cannot set this value larger than 60 minutes.
%

   MaxTransfer 45

%
%
%  Maximus has been fixed, it correctly writes out accurate timeOnToday
%  but now it subtracts the users real online time from that value when it
%  reloads. Unfortunately this is different from any previous method used
%  by Maximus. This new option informs Maxibank that you are using version
%  Maximus v2.01. Stating 'Version Max2.01' (the 2.01 is the important part)
%  will overide any Start_file_time kludges left over from v2.00 config
%  statements.
%

   Version Max2.01

%
%  A new option, MAXILOG. This points to a Maximus style logfile. It
%  can be pointed at Max.Log if desired. It will dump specific
%  information from the lastus??.Bbs file, as well as the calculated
%  real time the user has been online. Also keeps track of any bank
%  transfers (withdrawals or deposits, transfers and balance). This
%  is optional but informative. I don't recommend that you use the
%  Maximus (Max.Log) on multi-node systems. This might cause mass
%  confusion.
%

   Maxilog c:\max\max.log

%
%  use command line option '/NL' to shutoff logging, when running in
%  local mode (if you don't want the logfile updated). Logfile not
%  updated if you run Maxibank in local editor mode.
%
%
%  This next option is now obsolete, but remains for backward
%  compatibility
%
%  New for Maximus v2.00,                      the TimeOnToday value
%  increases by twice the amount of time the user has been online this
%  call.  Way to go Maximus....  Anyways this option points to a file
%  that contains an accurate timestamp of the users logon time. It may
%  become redundant, if Scott fixes Maximus. Till that happens you
%  Must specify the full pathname to the Active??.Bbs files.
%  Any overriding `/T??' task command line options will be used to
%  determine correct filename, same as with Lastus??.Bbs.
%
% /T6    =  <path>Lastus06.Bbs and <path>Active06.Bbs    etc.....
%
%  This KLUDGE will keep the TimeOnToday variable relatively accurate,
%  and will allow users to withdraw time, otherwise Maximus will be
%  reporting to Maxibank that the user has been on twice their current
%  logon time plus any other time previous time today. If a user has been
%  on 44 minutes, Max will be reporting that they have already been on for
%  88+ minutes in previous logons this day.
%

   Start_Time_File c:\max\active01.bbs

%
%
%  Returns to Maximus if the user has not pressed a key in this
%  amount of time. The default is set at 60 seconds. Carrier is
%  also being monitored at all times. INACTIVITY is not checked
%  when using the online Sysop Editor functions.
%
%  Note: Users get twice the normal inactivity time when reading
%  help file. Users are returned to Maxibank if they exceed the
%  inactivity time while reading the help file.
%

   Inactivity 60

%
%  These are the only users who can access the ONLINE editor
%  functions. These names are not case sensitive.
%
%  NOTE: If you are using ALIAS_NAME then make sure you
%  put the ALIAS names here instead of the real names.
%

   Manager Rodney Fraser
   Manager Dallas Hinton

%
% filename and path for the Bank accounts.
%

   Bank_File c:\max\maxibank.dat

%
%  filename and path of the user information file.
%  task info can be overriden by command  line parameter /T#
%
%  /T2    reads <path>\lastus02.bbs
%                           --
%  /T255  reads <path>\lastusFF.bbs  etc...
%                           --

   User_File c:\max\lastus01.bbs

%
%  Com port for Revision 5 FOSSIL communications.
%  can be overridden by command line parameter , /P#
%
%  port 1 = com1, port 2 = com2 etc....
%

   Port 1

%
%
%  First time accounts gets this amount of bonus account time.
%  Account Not actually opened till a non zero transaction.
%  Looky Lues don't clutter up the bank file.
%

   NewAccount 15

%
%  Interest per day on time in bank, 3 = 3% etc...
%
%  Interest can be a whole number, a fraction or a decimal number.
%
%  Interest is a per day thing,  so  10.25/365  would be 10.25 percent
%  per year. Maxibank will display your interest value as the smallest
%  value on a per day, per week, per month or per year basis.
%
%  Note about interest: A user's accumulated interest is added to the MAXIMUM
%  time in Maximus (*), so if users don't call regularly then they can get
%  LARGE amounts of withdrawl time. Events can prevent HUGE withdawls, but
%  somebody who rarely calls with never stay online for too LONG.
%
%  (*) Maximum time in Maximus - see below.
%
%     Interest  0.0274      =     10% per YEAR
%     Interest  10/365      =     10% per YEAR
%     Interest 8.25/365     =   8.25% per YEAR
%     Interest 1.25/30.5    =   1.25% per MONTH (approximate).
%     Interest 15/365       =   1.25% per MONTH (approximate).
%
%     etc...
%

      Interest 9.25/365            =  9.25 % per year.

%
%
%  If you are allowing interest payments and want to set a maximum number
%  of days used to calculate interest, NOTE: the interest in the bank
%  account is not effected by this setting. This only effects the Maximum
%  number of minutes a user will be allowed to withdraw. Incurred interest
%  exceeding any account Maximums is LOST. If interest is paid on a per
%  day basis then set this number small, usually less than ten. If interest
%  is being paid on a per year basis then set this number much higher, 365
%  days or greater. If MaxiBank reports interest is being paid on a weekly
%  or monthly basis then adjust this number accordingly. Just remember that
%  a user can withdraw the reported accumulated interest over and above
%  any maximum daily online limit specified as the Maximum time in Maximus
%  for their specific privilege level.
%
%  eg.  incurred interest = Bank Account Time *  Interest * days since
%       last call.
%
%       If days since last call > DaysofInterest then
%       incurred interest = Bank Account Time *  Interest * DaysofInterest
%
%       if interest is very small, shows up as per year then use 365 days.
%

   DaysOfInterest 365

%
%
%  Simple ASCII text file. If configured and exists then
%  user can ask for help. INSTRUCTIONS. Be creative !
%

   Help_file c:\max\maxibank.hlp

%
%  Controling withdrawl amounts based on user privileges.
%
%
%  I suggest you set the Maximus time in Maximus (*) amounts to 10 - 15
%  minutes more than the total accumulative times in Max.Ctl otherwise
%  withdrawls will never be allowed! (except the incurred interest amount).
%
%  (*) Maximum time in Maximus - see below.
%   ---------+-------+--------------------
%            | mins. |
%           +---------+
%  Privil   | Maximum |   Maximum
%  level    | time in |   time in
%           | Maximus |   bank account.
%  ------   +---------+   --------------
%
   Twit         15         60
   Disgrace     35         120
   Limited      45         180
   Normal       60         300
   Worthy       75         300
   Privil       90         360
   Favored      90         420
   Extra        120        0
   Clerk        120        0
   AsstSysOp    120        0
   SysOp        180        0
%  Hidden       1          1
%
%  zero's don't mean 'zero' they mean unlimited time in Maximus
%  and unlimited time in bank, there is of course a limit of about
%  30,000 minutes, a 2 byte signed integer. The defaults are all 'zero' so
%  make sure you specify privilege levels and amounts, else people will
%  attempt to withdraw maximum amounts, (everything in their accounts).
%  program runtime errors will occur if bank account extremes are allowed
%  and interest and inactive days are large. The maximum amount that
%  can be rentered from the editor menu is 9999 minutes, so perhaps you
%  should set maximum limits of 10000 minutes instead of allowing any
%  unlimited values for deposits.
%
%  Withdrawls will never overun declared events. The only time events
%  are allowed to be overrun is if the Maximum time in Maximus has been
%  set at unlimited "0". Be careful which privilege levels you set to
%  unlimited. I would reccomend you avoid the use of unlimited Maximus
%  time in Maximus amounts and set that value to 1440, a whole day. This
%  way NOBODY can overrun any events.
%
%
%  Maximum Withdrawl = (incurred interest) + (Maximum Time in Maximus) -
%                     (user time remaining) - (previous time on today).
%
%
%  an account with 300 minutes maximum and 2% per day interest and 60 days
%  inactivity would allow the withdrawl of 360 minutes! I doubt anybody
%  would actually do this unless they intended to use all 6 hours! Who?
%  DaysofInterest can solve this but people who withdraw more time than
%  they use are not getting any refunds!
%
%
%
%
%  Don't allow time withdrawls during these hours, start time is an
%  EVENT, withdrawls won't overrun the EVENT.
%

   Deposit_only  19:00   22:00

%
%  Don't allow withdrawls to over run these scheduled events.
%

   Event  24:00
   Event  00:01
   Event  00:02
   Event  00:03
   Event  00:04
   Event  00:05
   Event   1:00
   Event   9:00

%
%  Just a note about EVENTS. MaxiBank has no way of forcing these
%  events to occur. If the EVENT is going to occur in 30 minutes
%  and Maximus gives the user 45 minutes of logon time, then the
%  user may still be online when the event occurs. Of course the
%  user will not be allowed to withdraw time before the event, but
%  the user will still have 15 minutes after the event to withdraw
%  time. These EVENTS work best if they correspond to non bbs mailer
%  events. The kind that restrict the amount of logon time the user
%  gets because the event is pending. Then the user will not be able
%  to withdraw any time and will be logged off with a TIME LIMIT when
%  the mailer event is scheduled to start. Mailers will pass a caller
%  to the bbs with only seconds to go before an event, and since
%  Maximus allows 2 minutes for the user to logon, there is the rare
%  possibility that a user logged on after the REAL event. In the above
%  example of events, I have set up a few right after the crtical event
%  to prevent a user from withdrawing time immediately after the big
%  event at midnight and before they get the TIME LIMIT.
%
%
%  If you have accounts marked as HIDDEN, so that they do not get
%  Marked or Purged, and this inactive account is accessed then
%  use the following command to change the account back to normal.
%  a hidden account will have a green asterick before the user name.
%

   REMOVE_HIDDEN_STATUS

%
%
%  Optional colours, use numeric Colour or ANSI codes, the following are the
%  defaults. If you are unsure of an ANSI sequence use the numeric. If your
%  avatar users get strange output, then your ANSI codes are the reason. Put
%  the appropriate numeric colour code instead of your ANSIs.
%
%  COLOUR1  7    =        {normal GRAY}
%  COLOUR2  141  =        {blink LIGHTmagenta}
%  COLOUR3  13   =        {lightmagenta}
%  COLOUR4  3    =        {cyan   menu-rest chars!}
%  COLOUR5  10   =        {lightgreen}
%  COLOUR6  14   =        {yellow menu-first char!}
%  COLOUR7  15   =        {white}


%  COLOUR1          {normal GRAY}
%  COLOUR2          {blink LIGHTmagenta}
%  COLOUR3          {lightmagenta}
%  COLOUR4          {grey}
%  COLOUR5          {lightgreen}
%  COLOUR6          {lightred}
%  COLOUR7          {white}


%  if you don't like blinking ANSI in the display then shutt off all
%  blinking characters. !  (replaces COLOUR2 with COLOUR3).
%

%  NOBLINK

%
%

%  MONO   -  DON'T USE ansi COLOUR! must be after colour statements.

%
%  if you don't like the beeping sounds then use NOBEEP, the beeps are
%  attention getting, and only generate pauses during execution.

%  NOBEEP

%
%
% the end. comments lines begin with `%'....   RAFware (C) 1992.