LEGENDS(tm) 7 Sysop's Handbook
Authored by Jeffrey D. Hoffman.  Copyright (c) 1995.  All rights reserved.
http://www.sharbor.com/rpgSoft/index.html

Rave acclaim for the latest release
From TBBS sysops world-wide!

"I realize the full wizardry of your Legends software and I personally think
its genious, pure genious!"

"With Legends ... all my BBS lines are busy almost all afternoon and evening.
[It] is the pinnacle of excellence in online RPG games."

"This version goes beyond anything I've seen before."

"You'll find Legends to be the best ever."


Reflections from the creator
Forward

A lot of work has gone into this software.  With the support of a dedicated
design team, I am able to release this software of which the employees of
rpgSoft and I are extremely proud.  I would like to extend my thanks to both
Sysops and players alike.  First, to the players of this software, thank you
for your continued enthusiasm  and dedication to this game.  Your excitement
has spurred many of the new features highlighted in this version.  And to
Sysops, thank you for making LEGENDS the best selling entertainment package for
TBBS for the seventh straight year.  My dedication to enhancing your systems is
unwavering.  So, without further ado, I proudly unveil the seventh version of
this incredible software.

Table of contents
Chapter I       An introduction to LEGENDS
Chapter II      Installation
Chapter III     Configuration and customization
Chapter IV      Technical support
Chapter V       Demonstration version vs. registration version
Chapter VI      How to purchase LEGENDS
Chapter VII     Warranty
Chapter VIII    License agreement


An introduction to LEGENDS
Chapter I

This entertainment package for TBBS has been the uncontested best selling
third-party product for the past seven years.  In 1995 alone, over 150 new
features were added.  No other software package has been improved with such
relentless drive in such a short time frame.  Since its release, this software
has always achieved our vision of being the best product money can buy for
TBBS.  The rpgSoft mission changed in 1995.  The intention of this software is
to be the most powerful, easy-to-use entertainment package for any bulletin
board system available.  You're already running the best BBS software and in
moments, you'll be running the best role- playing system for any BBS in the
world.

Let there be no doubt that LEGENDS is the finest software available. More
Sysops run LEGENDS than any other package available.  It has always been the
forerunner in attracting new members and keeping your existing user base
calling frequently.

LEGENDS
LEGENDS is an interactive role-playing environment which supports up to
sixty-four players in real-time.  Users become submerged within an epic realm
consisting of nearly 4000 locations encompassing towns, forests, mountains,
swamps, dungeons, cliffs, and crypts.  Spanning this incredibly detailed world
are nine epic quests that reset automatically when they are solved.  Players
can compete or work together to solve the puzzles, out- smart the traps, slay
the horrible monstrosities, and return victorious.  A powerful command parser
accepting over sixty commands makes exploration, communication, combat, and
role-playing easy.

LEGENDS is further enhanced by built-in, on-line editors that allow privileged
users (known as Implementors) to edit and create new areas. Implementors have
access to an additional thirty commands for monitoring and maintaining the
realm.  In addition, the entire system is backed by a object-oriented
programming language used to create interactive puzzles and resetting quests.
A built-in file architecture and operating system makes uploading, downloading,
and compiling source code a snap!

LEGENDSlite
With the exclusive resetting quest technology, the LEGENDSlite software was
created for Sysops who wanted all the benefits of LEGENDS without having to
worry about creating and monitoring Implementors.  This software is a
hands-off, less-expensive version of the LEGENDS software backed by the same
role-playing system but without the editors, file architecture, and on-line
compiler.  At any time, you can conveniently upgrade to the full version
without any loss of your current realm.


Installation
Chapter II

The LEGENDS and LEGENDSlite software are inclusive within one another.  The
software is unlocked when you purchase either one or the other.  Because
installation is identical, regardless of the software you are running (if you
intend to upgrade) or what you intend to run, consider the terms LEGENDS and
LEGENDSlite synonymous for the remainder of this documentation unless directly
specified.

Software is included in the distribution archive for installing LEGENDS 7.0 on
your system.  This chapter is divided into three sections.  These three
sections coincide with the three options that the installation software
presents you with.  In short, the first section deals with installation of
LEGENDS on a system that is not already running a registered, earlier version.
The second and third sections deal with the upgrade options you have if you are
running a registered, earlier version.

*NOTE* Pkunzip is expected to be recognized at the command prompt. Either make
sure that the directory containing pkunzip.exe is among those in your PATH=
definition of your autoexec.bat file or copy the executable into the directory
in which you will be installing the LEGENDS software.

Recommended configuration
LEGENDS is a CPU-intensive product.  For superior performance, the lowest
recommended processor speed is a 486-25Mhz (faster preferred.)  In addition,
the follow equipment is required: 6MB free harddrive space, TBBS and TDBS
16-line version or larger, and a dedicated line for an environment-integrated
ghost-event.  We recommend a fast SCSI-II hard drive for improved performance.

Before running LEGENDS, confirm that your CONFIG.SYS contains a setting of
FILES=75 and BUFFERS=10,0.  We recommend a setting of at least 150 for
allowable open files if memory permits. Installing the demonstration version

The archive you have downloaded contains a fully playable demonstration of the
LEGENDS software.  The following steps outline the process of installing this
demonstration.

1.  Create a new directory for the LEGENDS software within your TBBS directory.
    During this section, the software will be installed into a directory called
    LEGENDS7.  The completed path would be:

C:\TBBS\LEGENDS7

2.  Extract the LEGENDS 7.0 archive into the new directory.  In addition to
    this documentation, the directory will now contain INSTALL7.EXE and
    INSTALL7.DAT files.

3.  Type INSTALL7.EXE to initiate the installation program.  This menu-driven
    software will prompt you to select from the following menu:

Select from the following installation options:
 1) Install demonstration version of LEGENDS 7.0
 2) Upgrade existing, registered software to version 7.0
 3) Upgrade registered version of LEGENDSlite to 7.0
 4) Exit installation program

4.  Select the first option by pressing [RETURN] or pressing the 1 key. Upon
    confirming your action, the screen will immediately switch to a progress
    bar and status window.  The installation process could take several minutes
    on slower machines.  You will be returned to a DOS prompt when the
    installation has completed.

5.  Modify your .SDL menu file and add the following line:

Entry:
L -> LEGENDS 7.0 - Levolution
Priv=0 A1=-------- A2=-------- A3=-------- A4=-------- ANS=- IBM=-
Key=L Type=200 Opt Data=c:\tbbs\legends7\legends7.tpg /Q

6.  A high-scores listing can be generated nightly by the ghost task.  See
    chapter III for details on setting this up.  If you intend to do so, you
    will want to add a method for displaying the score listing on the same
    menu.

Entry:
S -> LEGENDS 7.0 - Champions of the Realm
Priv=0 A1=-------- A2=-------- A3=-------- A4=-------- ANS=- IBM=-
Key=S Type=1 Opt Data=c:\tbbs\legends7\txtfiles\scores.txt

7.  Compile your .SDL file.

8.  As previously mentioned, you need to add a ghost-event using CEDIT. Append
    a blank event to your system and fill in the following information: (See
    chapter III for information on the flags accepted by LegendTASK.)

Entry  #, Occurs on Line   16 at 23:60 on Sun,Mon,Tue,Wed,Thu,Fri,Sat
Type = 200 OptData = c:\tbbs\legends7\lgndtask.tpg /Q && /E=1

9.  Your AUTOEXEC.BAT file needs to be updated with a single line.  This line
    is required to make the executable LegendTASK maintenance software work
    properly.

set clipper=f99

    Be sure to either run your AUTOEXEC.BAT file or reset your system prior to
    running the LegendTASK software.

10. The final step to getting LEGENDS up and running is to add the external
    maintenance executable to your daily TBBS maintenance routine.  Somewhere
    within your maintenance file, you need to add the following lines of code.
    Again, these settings are covered in detail in the third chapter. For this
    example each daily the maintenance software will purge inactive players
    after twenty- five days.

rem Perform the daily LEGENDS maintenance by running the executable version of
rem LegendTASK.
cd \tbbs\legends7
lgndtask.exe -a:25

11.  Run your bulletin board.


Upgrading 6.5 software to 7.0 software
Regardless of whether or not you are running LEGENDS 6.5 or LEGENDSlite 6.5, a
single keyfile available from Safe Harbor allows you to upgrade your software
to the corresponding 7.0 software.  (i.e., LEGENDSlite 6.5 upgrades to
LEGENDSlite 7.0.)

*Important*  Do not delete your old LEGENDS 6.5 software until after you have
received and properly installed the permanent keyfile which you receive from
Safe Harbor ten days after your original date of purchase.

1.  Create a new directory for the LEGENDS software within your TBBS directory.
    Do not overwrite your existing 6.5 software.  During this section, the
    software will be installed into a directory called LEGENDS7.  The completed
    path would be:

C:\TBBS\LEGENDS7

2.  Extract the LEGENDS 7.0 archive into the new directory.  In addition to
    this documentation, the directory will now contain INSTALL7.EXE and
    INSTALL7.DAT files.

3.  Copy your UPGRADE7.KEY file into the LEGENDS7 directory.

4.  Type INSTALL7.EXE to initiate the installation program.  This menu-driven
    software will prompt you to select from the following menu:

Select from the following installation options:
1) Install demonstration version of LEGENDS 7.0
2) Upgrade existing, registered software to version 7.0
3) Upgrade registered version of LEGENDSlite to 7.0
4) Exit installation program

5.  Select the second option by moving the high-light bar with the arrow keys
    and press [RETURN] or select the 2 key.  Upon confirming your action, you
    will be prompted for the complete path to your registered 6.5 software.
    Fill in the path when this prompt appears:

Please enter the path of your registered 6.5 software:
C:\TBBS\LEGENDS6\

6.  The installation software will compare the keyfiles necessary to perform
    the upgrade and if there are no problems, a keyfile for the 7.0 software
    will be automatically generated.  Immediately after, a new menu will
    appear:

Select from the following upgrade options:
1) Install 7.0 world.
2) Install 7.0 world and include 6.5 players.
3) Upgrade 6.5 world to 7.0 compatibility.
4) Exit installation program

7.  If you are upgrading LEGENDS 6.5 to 7.0 all three options are available to
    you from this menu.  LEGENDSlite upgrades do not allow the third option
    since access to the editors and the compiler software are required in order
    to make a functioning realm.  Select the option that best suits your
    intentions with the new version and press [RETURN].  *IMPORTANT*  If you
    intend to use option three, read the section below on this upgrade process.
  
8.  The software will now be installed, and in the case of option two and
    three, the upgrade will be performed.  This could take several minutes.
    When the installation is completed, you will be returned to the DOS prompt.

9.  Modify your .SDL menu file and change your existing LEGENDS menu item to
    the following:

Entry:
L -> LEGENDS 7.0 - Levolution
Priv=0 A1=-------- A2=-------- A3=-------- A4=-------- ANS=- IBM=-
Key=L Type=200 Opt Data=c:\tbbs\legends7\legends7.tpg /Q

10.  A high-scores listing can be generated nightly by the ghost task.  See
     chapter III for details on setting this up.  If you intend to do so, you
     will want to add a method for displaying the score listing on the same
     menu.

Entry:
S -> LEGENDS 7.0 - Champions of the Realm
Priv=0 A1=-------- A2=-------- A3=-------- A4=-------- ANS=- IBM=-
Key=S Type=1 Opt Data=c:\tbbs\legends7\txtfiles\scores.txt

11.  The LegendTASK software no longer has built-in editors since many of those
     features are accessable within LEGENDS.  Furthermore, a log is kept of the
     output of LegendTASK so both of the LegendTASK menu items you may have can
     be removed from your .SDL file.

12.  Compile your .SDL file.

13.  Update your ghost events through CEDIT to reflect the new directory for
     the LegendTASK software.  (See chapter III for information on the flags
     accepted by LegendTASK.)

Entry  #, Occurs on Line   16 at 23:60 on Sun,Mon,Tue,Wed,Thu,Fri,Sat
Type = 200 OptData = c:\tbbs\legends7\lgndtask.tpg /Q && /E=1

14. Your AUTOEXEC.BAT file needs to be updated with a single line.  This line
    is required to make the executable LegendTASK maintenance software work
    properly.

set clipper=f99

    Be sure to either run your AUTOEXEC.BAT file or reset your system prior to
    running the LegendTASK software.

15. The final step to getting LEGENDS up and running is to add the external
    maintenance executable to your daily TBBS maintenance routine.  Somewhere
    within your maintenance file, you need to add the following lines of code.
    Again, these settings are covered in detail in the third chapter. For this
    example each daily the maintenance software will purge inactive players
    after twenty- five days.

rem Perform the daily LEGENDS maintenance by running the executable version of
rem LegendTASK.
cd \tbbs\legends7
lgndtask.exe -a:25

16.  Run your bulletin board.


The difficulties of upgrading a 6.5 world to 7.0
If you are running the full version of LEGENDS and decide to upgrade your
existing world, including all the items, spells, rooms, etc. to 7.0, you should
be prepared for a lot of work ahead of you.  This installation software can not
upgrade the events of 6.5 into source code used by 7.0. As a result, the
resetting quests must be individually coded to operate properly.
 
Additionally, since the stores are no long handled through responses, each
store needs to be upgraded individually.  Fortunately, source code for each of
the stores is located in the EXAMPLES\ directory.  You and your Implementors
can copy the code out of that directory, compile it, and link it to the
appropriate store in MidDraaven.

Most importantly, however, is the quests.  As mentioned before, the quests will
no longer reset and all the puzzles will be inoperative.  Your Implementors
will have to piece together the original quests if you want to continue having
them available for your players.  If you purchased additional quests for your
system, consult Appendix A for further information.

Upgrading LEGENDSlite 6.5 (or 7.0) to LEGENDS 7.0
With a special keyfile from Safe Harbor, you can upgrade LEGENDSlite to the
full version of LEGENDS using this installation system.  If you are installing
LEGENDS 7.0 for the first time and want to upgrade directly from LEGENDSlite
6.5, you can do so by following the steps detailed in the previous section.
Remember, however, that the resulting software will instead be the full version
instead of the lite version.  Additionally, instead of an UPGRADE7.KEY file you
will have an EVOLVE_7.KEY

If you are already running LEGENDSlite 7.0 and want to upgrade, follow these
steps:

1.  Move the new EVOLVE_7.KEY into your LEGENDS7 directory.

2.  Copy your LEGENDS7.KEY and place it into a subdirectory called OLDKEY
    within your LEGENDS7 directory.  The complete path will read:

C:\TBBS\LEGENDS7\OLDKEY\

3.  Run the installation software.  You will be presented with the following
    menu:

Select from the following installation options:
1) Install demonstration version of LEGENDS 7.0
2) Upgrade existing, registered software to version 7.0
3) Upgrade registered version of LEGENDSlite to 7.0
4) Exit installation program

4.  Select the third option with the arrow keys and press [RETURN] or press the
    3 key.  The software will prompt you for the complete path to your existing
    LEGENDSlite software.  Change your path to the temporary directory in your
    LEGENDS 7 directory like this:

Please enter the path of your registered 6.5 software:
C:\TBBS\LEGENDS7\OLDKEY\

5.  After you have entered the correct path, the installation software will
    generate a new key in your current LEGENDS 7 directory.  It is important to
    save your old keyfile until you have received your permanent keyfile from
    Safe Harbor Computers ten days after your original purchase.


Configuration and customization
Chapter III

This section describes, in detail, the layout of the LEGENDS7 directory and
what important files you will need to familiarize yourself with in order to
properly customize the LEGENDS 7.0 software to your liking.  If you are running
the demonstration version of this software, this section can be skipped since
external configuration is ignored by the demonstration.

LEGENDS7\
The main databases and executable software is stored in the root directory. The
software controls these files and no maintenance is required except when
re-indexing is required.  You can delete all of the index files (*.NDX) from
this directory and the LegendTASK software will rebuild the indexes when it is
executed next.

SYSTEMS\
This directory contains important files that relate directly to the
configuration and current set-up of the game.  These files are extremely
important should not be made available for public use or access by your
Implementors.  The index files in this directory can be deleted also and
LegendTASK will regenerate them automatically.

Other files of extreme importance are listed below.

COMMANDS.LST    The file that is displayed when a player types COMMANDS.
L7GLOBAL.L      The .L source code for global procedures executed by LEGENDS.
L7GLOBAL.LC	The compiled result of the L7GLOBAL.L file.
LEGENDS7.CFG	The LEGENDS configuration file.
LEVOLUTN.LST    The file that is displayed when a Levolution user types
                COMMANDS.
LEVOLUTN.TRE    The file containing the initial directory tree for new
                Implementors.
LGNDTASK.CFG    The LegendTASK configuration file.
LGNDTASK.LOG    The log file (if private) from the latest run of LegendTASK.
LGNDTASK.SYS    The file containing the last date that LegendTASK ran.
PRIVILGE.LST    The file that is displayed when an Implementor types COMMANDS.

All of the above listed files are available for you to configure and change.
Primarily you will want to focus your attention on the LEGENDS7.CFG and
LGNDTASK.CFG files initially.  These will influence the global feel of the
game.  Sections below discuss how to configure these files.

TXTFILES\
This directory, aside from containing all the .TXT files referenced by LEGENDS,
and documentation.  These files may be referenced throughout the remainder of
this document.

EXAMPLES\, PUBLIC\, QUESTS, WORLDSLC\, and remaining directories
These directories are addressed inside the Implementor's Guide which is
available in the TXTFILES\ directory.  Consult that document for details on
these directories.

Modifying the SYSTEMS\LEGENDS7.CFG file
The LEGENDS configuration file comes complete with commented-out lines
detailing each of the flags you can specify to alter the environment in which
your users play.  This section will offer expanded definitions for each of the
flags you can use.  In order to establish the global defaults you want LEGENDS
to abide by, you need the following statement within this file:

#DEFINE DEFAULTS   = (FLAGS)

/CQ
When present, players can string multiple commands together in one command
entry by seperating the commands with a semi-colon (;).  Since it is possible
for players to string up to 90 commands, space permitting, together, a Pentium
processor is recommended for systems making use of this flag.

/DT:n
This setting allows you to override the natural destination of resurrection for
a a player to a specific location n.  This flag is normally not included unless
your system falls into one of two situations.  The majority of the systems that
will use this flag are systems that upgraded an existing realm from 6.5 to 7.0.
A few systems may want their players to resurrect to a place other than the
healers.

/IU
This flag allows LEGENDS to modify your userlog and make any user invisible if
they enter the game.  When they leave by normal means, the userlog is once more
updated and the user becomes visible once more. This flag protects alias
identity while the user is in the game.

/LY
This flag causes the YELL command to be limited to the zone that the player is
standing in.  The game is more realistic when this flag is used and likewise it
discourages use of this CPU-intensive command.

/MC:n
If you include this flag, players are able to have multiple characters.  The
total number of characters they are allowed to have is specified by the numeric
value n.  (*Note* It is important to realize that allowing players to have
multiple characters permits a form of cheating - mischievous players could
spend hours making alternate characters, suiciding them, and collecting the
gold left behind by the dead character.)

/MS
This flag makes it possible for a user to enter the built-in message base.  

/RF
If you add this flag, when players die there will be a chance that their
characters will not survive the resurrection process.  Without this flag, death
means nothing to a player and makes it possible for them to come back to life
infinitely.  With this flag, death becomes something that players want to avoid
at all costs.

/RT
This flag allows you to define an on-line teleconference using another #define
line.  This line is referenced by LEGENDS whenever the player uses the RTABLE
command.  LEGENDS will not recognize that command if this flag is missing.  The
line you need to define is:

#DEFINE ROUNDTABLE = TYPE=(TYPE) OPTDATA=(OPTDATA)

/SF:n
This is the spell failure flag.  Without it, spells will never fail and players
master a spell immediately upon learning it.  With this flag, you can specify a
numeric value n that represents the failure percentage of the spell when it is
initially learned.  The recommended value for this setting is 75%, meaning that
players have a 25% chance of the spell casting successfully.

/SL
This flag makes it impossible for players who have suicided their last
character to re-enter the game and make a new character until the LegendTASK
software has run and removed suicided characters from the database.  (*Note*
This flag helps in reducing cheating from players making characters, killing
them off, making a new character and getting the gold left behind.)

/SY
When added, the yell command becomes anonymous by substituting the name
'Someone' in place of the user's name when the message is broadcast.

/WH
This flag makes it possible for players to use the WHISPER command. This
command is a global, private message sending system that, if abused, can be CPU
intensive.

You also have complete control over the player generator with respect to the
point distribution system. The configuration file must include a line which
reads:

#DEFINE NEWPLAYER  = (FLAGS)

/AP:n
This flag determines the number of adjustment points available to the user that
they can use to modify their attributes.  The recommended value is 10.

/DR:dd+n
This flag defines the dice that is rolled and the adjustment that is added for
each of the base attributes.  The recommended setting is 2d8+2.

/MP:n
When present, this flag over-rides the default value of 18 as the maximum value
that players can adjust their character's attributes to.  LEGENDS supports a
value up to, but not exceeding, 99.

/RR
This flag, if present, allows the player to re-roll their spread of attributes
infinitely until they get a set that they like.  Attribute re-rolling is
extremely CPU intensive and it is recommended that this flag not be included.

Adding Implementors to LEGENDS
(Changes made in this section have no effect on a LEGENDSlite system.) If you
are running the registered version of LEGENDS, you can add Implementor
definitions directly into the LEGENDS7.CFG file in the section labeled #STRUCT
IMPLEMENTORS.  Within this structure, there is a specific format in which
Implementors are defined:

(USER NAME)       = (PRIVILEGE FIELDS)          HOMEPATH:(DIRECTORY)

USER NAME
This is the name of the user as it appears on your BBS.  Implementor privileges
follow a player regardless of the name of the character they have.

PRIVILEGE FIELDS
This is a string of periods (.), X's, and dashes (-) which allow you to specify
the exact abilities that the Implementor will have.  Each position of the
string represents a specific skill.  These positions are detailed in the chart
below.  Placing an X in a position grants that ability to the Implementor.  A
period (.) makes that ability impossible for the Implementor to use.  Reserved
fields should remain a dash.  Positions that have nothing associated with them
must be left as a space.

Pos     Description
 1      Signifies that the Implementor can edit anything no matter who
        made it.*
 2  
 3 	Can create/edit exits.
 4 	Can create/edit items.
 5 	Can create/edit and summon non-playing characters.
 6 	Can create/edit responses.
 7 	Can create/edit rooms and zones.
 8 	Can create/edit spells.
 9 	Can edit and summon players*
10 	Can create/edit quests.
11 	Can use the REPLACE command to directly edit player attributes 
        and fields.*
12 	Reserved.
13
14 	Reserved.
15 	Can broadcast environmental messages via the %E, %LE, and 
        %ZE commands.
16 	Can see the extended "who's on-line" listing including location of 
        players.
17 	Can see the real name of users who are inside of LEGENDS on 
        the "who's online" listing.
18 
19 	Can enter the Levolution operating system.
20 	Can use the MAP and ATTRIB commands within Levolution-OS.*
21 	Can protect and unprotect files with the +F and -F commands.*

*Positions marked with the asterisk should be reserved exclusively for your
master Implementor or yourself.

If you have marked position 19, making it possible for the Implementor to use
the SHELL command to reach the Levolution Operating System, you must establish
a home directory for the Implementor to store her work within.  In most cases,
I would suggest that you name the directory after the name of the Implementor,
or at least the first eight characters.  You need to physically make the
directory within the LEGENDS7 directory and then specify that name within the
LEGENDS7.CFG file.  For example, establishing a home directory for a Thaliant
the Implementor would encompass creating a directory called LEGENDS7\THALIANT\,
and then the specification in this file would be:

HOMEPATH:\THALIANT\

(Although a backslash is required as the prefix, Levolution-OS interprets it as
off the root of the LEGENDS7 directory.)  A completed line defining an
Implementor would look like this:

JEFF HOFFMAN      = X XXXXXXXXX- -XXX XXX       HOMEPATH:\THALIANT\


Configuring LGNDTASK.EXE
The executable version of LegendTASK accepts several parameters at the command
line to customize the daily maintenance of the realm.  This brief section will
describe the flags as they are accepted by the executable program.  Do not
separate parameters with spaces!!

-?
Passing this flag to LGNDTASK.EXE will cause a brief definition of all of the
flags to be displayed.

-A:n
This flag causes LGNDTASK.EXE to purge players who have been inactive for more
than n-days.  The recommended setting is -A:25 to purge users after twenty-five
days of not playing.

-L:n
If any of your Implementors use private variables in their reset files and have
been doing so since the 7.0 version of LGNDTASK.TPG, this flag maintains
compatability by forcing the executable to think it is running on a specified
line number.  If your ghost event used to come up on line 64, you would set
this parameter with -L:64.

-P
This flag causes the maintenance software to ignore database purging and
packaging.  Use of this flag is highly discouraged because filtering out unused
records greatly speeds up the game.

-T
This flag initiates the in-game tag competition between players.  If the tag
sequence is already active, a new player is picked to be it by this flag.

The default and recommended command line is:

LGNDTASK.EXE -A:25-T


Modifying the SYSTEMS\LGNDTASK.CFG file
LegendTASK is the ghost event that has been integrated into the gaming
environment of LEGENDS.  It performs three important tasks; First it confirms
the existance of and generates any missing index files.  Second, it resurrects
monsters at a specific rate through-out the day.  Third, it issues atmospheric
messages to add to the mood of the game for players.

/E=n
When you establish your ghost event in CEDIT, the only flag that LegendTASK
accepts is the /E=n flag.  This flag specifies the event definition that will
be used to customize this session of LegendTASK.  Customization means a
specific shut-down time, a specific rate of resurrection, and another for
issuing messages.  There is no limit to the number of events you can define.

Events are defined within the SYSTEMS\LGNDTASK.CFG file.  Like the LEGENDS7.CFG
file, the accepted flags are listed at the top of the file.  The actual
definition of an event is done with a line like this: (Where n is the event
number referenced by the ghost event.)

#DEFINE EVENTn = (FLAGS)

There are three flags which LegendTASK accepts:

/S=hh:mm
This flag passes the time at which LegendTASK will shut down.  This time is
kept in military time, so shutting down the event at 11:30 at night is
represented as /S=23:30.  This flag must be present for LegendTASK to function
properly.  If you start LegendTASK at 07:00am and want it to shut down at
06:00am the next morning, the setting would still be /S=06:00.  LegendTASK is
intelligent enough to understand the start and end times and how they relate to
one another.

/R=nn
This flag defines the number of minutes in between resurrection cycles.  When
monsters are killed by players (which happens very frequently) the monster must
be resurrected by the ghost event to be active again.  A pool of dead monsters
builds up during the nn-minutes and then they are all resurrected at the end of
the time limit.  Not adding this flag causes monsters not to be resurrected for
the duration of the LegendTASK run.

/A=nn
This flag determines the number of minutes in between atmospheric messages
being issued.  The time is kept in nn-minutes.  Leaving this flag out causes
atmospheric messages to be ignored for the duration of the LegendTASK run.

Shutting down LegendTASK when it is running
Whether you are running LegendTASK from a menu item to monitor its progress or
it is operating as a ghost task in the background, you may need to shut it down
for one reason or another.  To terminate LegendTASK, you need to press F3 while
its operations are on screen.  (When it is running as a ghost task, you need to
press F2, move to the ghost task line, press [return] and then press F3.)  Upon
signaling LegendTASK to terminate it will automatically shut down at the
nearest convenient process.


Technical support
Chapter IV

The author of this software can be reached in a variety of ways.  The fastest
method for support is through Safe Harbor Computers BBS.  This system is also
the first place on which new releases, bug-fixes, and new product announcements
are posted.  Error reporting and troubleshooting assistance is readily
available on-line.

(414) 548-8140 for 14.4k connections
Safe Harbor Computers BBS - 24hrs a day, seven days a week.

Electronic mail the programmer at jeffrey.hoffman@teldta.com.  

Registered users receive the direct phone number for the rpgSoft offices and
can call for voice assistance with any questions or concerns that they have.

The rpgSoft, inc. world wide web page can be reached at
http://www.sharbor.com/rpgSoft/index.html.

The demonstration version vs. The registered version
Chapter V

As mentioned above, this archive consists of a playable demonstration of the
LEGENDS package.  As little as possible has been disabled so that you can
experience every aspect of the software before you decide to register. The
following restrictions have been placed on this demonstration:

1.  Players are limited to only one play per day.
2.  You can not customize the configuration of LEGENDS or LegendTASK.  By
    default, suicide lock-out is active, resurrection failure is active,
    yelling is limited, the whisper and roundtable commands are disabled, and
    users are not turned invisible when they enter the game.
3.  You can view each of the creation/editing screens but your changes are not
    saved.
4.  You can not access Levolution or the on-line compiler.
5.  Delay-messages are displayed upon entry and exit of the game.


How to purchase LEGENDS
Chapter VI

LEGENDS, LEGENDSlite, and all related products are distributed exclusively by
Safe Harbor Computers.  A convenient on-line order system allows you to
purchase any of these products via their bulletin board.  You can use your
visa, mastercard, or discover cards to instantly download the keyfiles which
unlock this software.

(414) 548-8140 for 14.4k connections
Safe Harbor Computers BBS - 24hrs a day, seven days a week.

If you have never called before, please use your real name and when prompted by
the first menu, select the rpgSoft TDBS product support area. Make sure you
select the next menu item which allows you to register as a Sysop to gain
immediate access to the board.  With this access, you'll be able to download
bug fixes, new products, and expansion systems for the game.

Warranty
Chapter VII

LEGENDS is distributed on as "AS IS" basis only, without warranty. Neither
Jeffrey D. Hoffman, rpgSoft, nor the authorized dealers of LEGENDS shall have
liability or responsibility to any person or entity with respect to liability,
loss, or damage caused or alleged to be caused by this software.  This
included, but is not limited to, any interruption of service, loss of business
or anticipatory profits, or consequential damage resulting from the use of this
software.

License agreement
Chapter VIII

Purchasers of LEGENDS are expected to honor their license agreement. This
software is copyrighted, and licensed to the purchaser for your individual and
exclusive use on a single CPU at a time.  Any reproduction for use by other
persons is a violation of our copyright and your license agreement.

Carefully read the following terms and conditions.  Use of this product
constitutes your acceptance of the terms and conditions, and your agreement to
abide by them.

1.  THIS IS AN END-USER LICENSE.  You, the original purchaser, are granted this
license for the use of LEGENDS software under the terms stated in this
agreement.  You may not assign or transfer the software or this license to any
person without the express written consent of Jeffrey D. Hoffman.  Any attempt
to sublicense, assign, or transfer any of the rights, duties, or obligations
hereunder is void.

2.  THE LEGENDS SOFTWARE IS COPYRIGHTED MATERIAL. Once you have paid the
required single copy license fee, you may use the software as long as you like
provided you do not violate the copyright or any of the following conditions.

3.  SINGLE CPU LICENSE.  You may use the software on any computer for which it
is designed as long as it is not in use on more than one computer at the same
time.  You must pay for additional licenses if you want to use this software on
more than one computer at the same time.

4.  BACKUP COPIES.  You may make as many backup copies of the software as you
require to avoid loss.  You are responsible for all backup copies you make, and
must assure that they do not result in any use of the software which would
conflict with the provisions of paragraph 2 above.

5.  SOFTWARE MODIFICATION.  You may not make any changes or modifications to
the Licensed software not expressly authorized by Jeffrey D. Hoffman.  This
includes but is not limited to disassembly and reverse engineering the
software.

6.  FEDERAL GOVERNMENT.  This Software is Commercial Computer Software under
the Federal Government Acquisition Regulations and agency supplements to them.
The Software is provided to the Federal Government and its agencies only under
the Restricted Rights Provisions of the Federal Acquisition Regulations
applicable to commercial computer software developed at private expense and not
in the public domain.

7.  LIMITATION OF LIABILITY.  In no case shall the Liability of Jeffrey D.
Hoffman exceed the license fees paid for the right to use this software or One
Hundred Dollars ($100.00), whichever is greater. 8.  THIS AGREEMENT MAY NOT BE
MODIFIED.  This agreement may not be modified except by a written instrument
signed by Jeffrey D. Hoffman.  This license constitutes the entire agreement
and understanding between you and Jeffrey D. Hoffman, and supersedes any prior
agreement or understand whether oral or written relating to the subject of this
License.

(r)rpgSoft, LEGENDS, LEGENDSlite, LegendTASK, and Levolution are registered
   trademarks of Jeffrey D. Hoffman.
(c)Copyright 1995 by Jeffrey D. Hoffman.  All rights reserved.
