Event_1.CFG

All event fields MUST be formatted as shown and in the order shown.
Keywords are not case sensitive. Event fields must all be preceeded
by the # symbol. Everything else will be ignored.

Generally, format is:

...#EVENT <DAY> <START-END> <SERVICE> <COST> <SCRIPT DEFINITIONS> 

*******************     *******************

<DAY> Options:

ALL , MON , TUE , WED , THU , FRI , SAT , SUN

These are the days for which events are defined.
Days should be sequential. Make sure all time is accounted for
and that there are no time gaps.

*******************

<START-END> Options:

Every hour of the week must be accounted for. No overlapping is permissible.
Smallest unit of measurement is the minute. There is only one requirement
for your scheduling.  You must not have mail only as the first event in
the schedule.  See examples below.

*******************

<SERVICE> Options:

BBS CRASHMAIL MAILONLY NOFREQ OKFREQ NO_NETWORK

BBS and CRASHMAIL may be used together. MAILONLY is exclusive.
NOFREQ and OKFREQ govern whether your system will permit file requests.

If NO_NETWORK is used, the system will run as a BBS only. There will be
no display of the 'Press ESCAPE to enter the BBS' and there will be no
attempt made to handle network calls.

*******************

<COST> Options:

COST=X , COST<X , COST>X

The BBS will call out if the processed nodelist costs meet the specified
criteria.

*******************

<SCRIPT DEFINITIONS> Options:

Path and filename of scripts which will be executed are defined with the
script definition field.  Each of the four scripts must be defined. It is
permissible to use the same script for each number but all four must be
defined. Event transitions occur when a scheduled event begins as
defined by the <START-END> fields.

 TRANSI at event transitions.
 LOGOFF after user logoff.
 FIDOIN after Fido inbound.
 FIDOUT after Fido outbound.

The number of definable numbered scripts is 64000. Each script defined will
cost 260 bytes of memory so keep it lean and mean to conserve memory.

******************* 

Sample event definition....


EVENT MON WED FRI 00:00-01:59 BBS CRASHMAIL COST<21 TRANSI=2 LOGOFF=3 FIDOIN=1 FIDOUT=4
EVENT MON WED FRI 00:00-01:59 NO_NETWORK TRANSI=2 LOGOFF=3 FIDOIN=1 FIDOUT=4
EVENT SUN TUE THU 00:00-01:59 CRASHMAIL COST<21 TRANSI=2 LOGOFF=3 FIDOIN=1 FIDOUT=4
EVENT SAT 00:00-01:59 BBS COST<21 TRANSI=2 LOGOFF=3 FIDOIN=1 FIDOUT=4
EVENT ALL 02:00-02:59 MAILONLY NOFREQ COST<21 TRANSI=3 LOGOFF=1 FIDOIN=1 FIDOUT=4
EVENT ALL 03:00-23:59 BBS CRASHMAIL COST<21 TRANSI=7 LOGOFF=6 FIDOIN=8 FIDOUT=11

EVENT MON WED FRI 00:00-01:59 BBS CRASHMAIL COST<21 TRANSI=2 LOGOFF=3 FIDOIN=1 FIDOUT=4
EVENT MON WED FRI 02:00-23:59 NO_NETWORK TRANSI=2 LOGOFF=3 FIDOIN=1 FIDOUT=4
EVENT SUN TUE THU 00:00-01:59 CRASHMAIL COST<21 TRANSI=2 LOGOFF=3 FIDOIN=1 FIDOUT=4

Note that the above control lines do not have the preceeding pound (#)
symbol.  They will be ignored by the event processor.

The control lines below, preceeded by the pound (#) symbol, will
be processed by the event processor.

#EVENT ALL 00:00-00:59 BBS OKFREQ CRASHMAIL COST<21 TRANSI=1 LOGOFF=2 FIDOIN=3 FIDOUT=4
#EVENT ALL 01:00-01:59 BBS OKFREQ CRASHMAIL COST<21 TRANSI=2 LOGOFF=2 FIDOIN=3 FIDOUT=4
#EVENT ALL 02:00-02:59 MAILONLY NOFREQ COST<21 TRANSI=2 LOGOFF=2 FIDOIN=3 FIDOUT=4
#EVENT ALL 03:00-23:59 BBS OKFREQ CRASHMAIL COST<21 TRANSI=2 LOGOFF=2 FIDOIN=3 FIDOUT=4

#1=MEBBSNET:scripts/Transi.SCP
#2=MEBBSNET:scripts/LogOff.SCP
#3=MEBBSNET:scripts/FidoIn.SCP
#4=MEBBSNET:scripts/FidoOut.SCP
#5=MEBBSNET:Scripts/Script5
#6=MEBBSNET:Scripts/Script6
#7=MEBBSNET:Scripts/Script7
#8=MEBBSNET:Scripts/Script8
#9=MEBBSNET:Scripts/Script9
#10=MEBBSNET:Scripts/Script10
#11=MEBBSNET:Scripts/Script11

Note the sequential numbering of scripts. Scripts MUST be numbered
sequentially with no out-of-sequence scripts.  Numbering must start
at 1. No spaces are permissible in the script fields.