Oneliner V1.3, Freeware BBS door, By D. Tyler Barnes
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This is a simple Oneliner door that will work on any BBS that can create a
DOOR.SYS drop file. 
The archive you got should contain the following files:

AUTOLINE CFG <--- Edit this and type in some line to appear automatically
BBS      BAT <--- Batch file that is run when Oneliner door is exited
DROP     BAT <--- Batch file that is run when Oneliner door is exited
INIT     EXE <--- Used for initializing data files
OLCOUNT  DAT <--- Data file used by Oneliner door. Do not edit.
ONELINER ANS <--- Ansi screen that you can use in the Oneliner door
ONELINER CFG <--- Configuration file! Edit this before starting!
ONELINER DAT <--- File that oneliners are stored in
ONELINER EXE <--- Oneliner Door
ONELINER TXT <--- ASCII screen that you can use in the oneliner door.
POSTERS  TXT <--- Users in order that posted in the oneliners
README   TXT <--- This file

Autolines
~~~~~~~~~
Ok, now to explain "Autolines" ... you can turn them on or off in the
configuration file. All they do is that after a certain amount of posts on
the oneliners (that you set in the ONELINER.CFG), A random line is taken from
the AUTOLINE.CFG file and is put on the autoposts. Edit the AUTOLINE.CFG to
put in an unlimited amount of Autolines, but the LAST line on this file must
say:
** END **

Also, after editing the AUTOLINE.CFG, there is a place in the ONELINER.CFG
where you have to set how many Autolines you have in the file.

BBS.BAT and DROP.BAT
~~~~~~~~~~~~~~~~~~~~
One of these files is run when the oneliner door is exited depending on your
settings in the Oneliner.cfg file. If you have it set so it drops carrier
when the user is done in the door, it will run DROP.BAT. If it is set so it
will just exit the Oneliner door and keep the user online, BBS.BAT is run. If
You do not need these batch files, you can not delete them. You can however
leave the file blank so that when it is run, nothing happens.

Oneliner.CFG file
~~~~~~~~~~~~~~~~~
This is explained inside the actual ONELINER.CFG file. Edit it before
starting to use the oneliner door.
I guess I should mention one thing about the CFG though incase you miss it
because it is VERY important! .... There is a setting in the ONELINER.CFG
that controls how many lines of text will be kept on the oneliners. Every
time you change this number, INIT.EXE MUST BE RUN!!!

POSTERS.TXT file
~~~~~~~~~~~~~~~~
This file is so that the Sysop can find out who wrote what on the wall incase
something is written that is not allowed. The names of the posters will
appear in the text file in the same order as their posts on the wall.

So if the oneliners said:

Hi my name is bob
Hey everyone I'm cool
f*ck off!!!!
What a loser huh?
Etc Etc....

And the POSTERS.TXT file said:

Bob Smith
Bill Gates
Jane Brown
Shirley Mcdonald
Etc Etc....

you'd know that it was Jane Brown that told people to "F" off.

Oneliner.ANS & Oneliner.TXT
~~~~~~~~~~~~~~~~~~~~~~~~~~~
One of these file is shown when in the oneliner door depending on if the user
has ANSI or not. If the user has ansi, ONELINER.ANS will be shown, if not, 
ONELINER.TXT will be shown. There are some settings in the ONELINER.CFG
that you'll want to look at that will affect these files greatly :)
First of all there is a setting for whether you want the screen shown before
the oneliners, or underneath the oneliners. If you make it so the screen is
before the oneliners, the screen inside the ONELINER.ANS file (We'll assume
the user has ANSI from now on) will be shown as soon as the oneliner door
loads up, and a "Press any key to continue" prompt will come up. Then when the
user hits a key, the screen is cleared and the oneliners are shown. If it
is set so that the screen is shown underneath the oneliners, then as soon as
the oneliner door opens, the screen will be shown and the Oneliners will be
put over top of the screen. This is so that you can have pictures around the
oneliners if you want. If you don't want any pictures I suggest you just set
it so the picture is shown underneath the oneliners, and then leave the
ONELINER.ANS file and the ONELINER.TXT file empty. When putting pictures
around the oneliners, you will want to adjust a few settings. First of all
you can set how many spaces it leaves before writing every line. This is
for justification purposes so that pictures can be put on the lefthand side
of the writing if you want. Remember though, that when moving the oneliner
text to the right, you will want to lower the text-limit that the user can
type on the wall otherwise you'll get some word wrapping. This setting is
also in the oneliner.cfg. You should have this setting set at 78 minus the
number of spaces you've moved the wall text. And finally, there is a setting
in the ONELINER.CFG file that you can adjust to put some carriage returns
before it starts displaying the wall. This is again, for justification
purposes.
NOTE!: If the user has ANSI then moving the text to the right and putting
       pictures on the left of the oneliner text will not be a problem, but
       if the user does not have ANSI, anything on the left of the oneliner
       text will be deleted. Also I haven't really tested it, but I don't
       think UP & DOWN justification will work very well for Non-ANSI users.

Init.EXE
~~~~~~~~
Read section on ONELINER.CFG

Sysop Functions
~~~~~~~~~~~~~~~
While the user is in the Oneliner door, you may perform any of the following commands:

   F5     -  Shell to DOS.
   F8     -  Twit user and return to BBS.
  F10     -  Initiate chat with user.
  Home    -  Main user stats.
  PgDn    -  Secondary user stats.
Up Arrow  -  Increase user's time remaining.
Dn Arrow  -  Decrease user's time remaining.


Future Additions
~~~~~~~~~~~~~~~~
Well, I don't really have many more ideas, so if you have some I'd like to
hear from you :) ... here is something that I will be putting in
soon though. 
* RIPterm graphics. (All this basically will be is an auto-RIP detect, and
                    a file where the sysop can put a RIP screen.... just like
                    how the .TXT and .ANS screens are done in this version)

If you feel like contacting me for some reason, you'll have to phone one
of the local BBSes I call because I don't have an internet address anymore.
So E-Mail Kaptain Krunch at:

Smokey's Den - (604)9232386
Funny Farm   - (604)2873963
ByteBucket   - (604)2866249
               (604)2868316
               (604)8300491
               (604)8300492

Legal Crap
~~~~~~~~~~
I have tested this door throughly, but if there turns out to be some error,
and any damage or loss of data is caused, it isn't my fault! .. I can
assure you however that there probably isn't even any coding IN this program
that could possibly do too much damage no matter how badly I screwed up
the code.
