home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
BBS_GAME
/
RTP190A.ZIP
/
SYSOP.DOC
< prev
next >
Wrap
Text File
|
1994-02-22
|
20KB
|
416 lines
RISE TO POWER Version 1.90 -- Program & Design by Robert A. Dalton
Based on original source code by Chris R. Tynes
Copyright (C) 1993
Final Compile Date: 02-22-94
Compiled using SCOTT BAKER's Door Driver Routines (Registered)
and Borland Pascal 7.0 (Professional).
INTRODUCTION:
------------
RISE TO POWER is a on-line door game of intrigue based in 15th
Century Germany. The goal is to advance from a land holding
Knight to King and unite the 10 provinces of Germany. To do
this you will have to use treachery, guile and force of arms.
DISCLAIMER:
----------
To the extent of this SysOp's knowledge, this software will cause not
damage whatsoever to your system. HOWEVER, no warranty is given or
implied. By running this software, you hereby submit to the rules and
limitations imposed by the author. NEITHER THE AUTHOR, NOR ANY OF THE
TEST SITES, SUPPORT BOARDS, OR ANYONE OF ANY RELATION TO THE GAME MAY
BE HELD RESPONSIBLE FOR ANY OF THE VARIOUS POSSIBLE PROBLEMS THAT MAY
OCCUR. IF YOU DO NOT AGREE WITH ANY OF THE RULES OR REQUIREMENTS
STATED, DO NOT USE THIS PACKAGE!
REQUIREMENTS:
------------
At this point in time the only requirements are FILES=10
(or more) in your config.sys file. The game is RIP aware
but NOT a RIP Game at this time. In this version a FOSSIL
is NO longer required to run the game.
Files Included
--------------
Below is a listing of all files for the RISE TO POWER Game.
If you are missing ANY of these files (except for the DOC and
FRM files), the game will NOT function. Feel free to give out
copies of the ENTIRE archive package of RTP but please make sure
all the files below are in that package:
ASSASSIN.ANS - Assassin ANSI Menu Screen
ATTACK.ANS - Attack Player's Keep ANSI Menu Screen
BARON.ANS - Baron's Keep ANSI Menu Screen
DUEL.ANS - Duel ANSI Screen
KING.ANS - King's Keep ANSI Menu Screen
MAPMENU.ANS - Large Screen ANSI Map Display
PLAYER.ANS - Player's Keep ANSI Menu Screen
RTOPEN.ANS - ANSI Opening Screen for RISE TO POWER
RTP_1.ANS - ANSI Keep with Drawbridge Open
RTP_2.ANS - ANSI graphic of Keep with Drawbridge Closed
RTP_3.ANS - ANSI graphic of Addition to Keep
RTP_6.ANS - ANSI Graphic of constructed church
RTP_7.ANS - ANSI Graphic of meeting another player
RTP_8.ANS - ANSI Graphic of assassin attacking player from behind
RTP_10.ANS - ANSI Graphic of message being delivered
RTP_11.ANS - ANSI graphic of player being promoted
RTP_12.ANS - ANSI Graphic of King Giving hand of women in marriage
RTP_13.ANS - ANSI Graphic of treasure chest
RTP_15.ANS - ANSI graphic of meeting brigands
RTP_16.ANS - ANSI graphic of a monk
RTP_17.ANS - ANSI graphic of a challenge
RTP_18.ANS - ANSI graphic - You become King
STAT.ANS - ANSI Player Status Screen
TREACH.ANS - Treachery ANSI Menu Screen
VISIT.ANS - Visiting Players ANSI Menu Screen
WMAIN.ANS - RISE TO POWER Main ANSI Menu Screen
SAMPLE.BAT - A sample BAT file for Door.sys used on my BBS (WILDCAT)
RTP.CTL - Control file for setting up RISE TO POWER
KEY.DAT - Dummy Key for RISE TO POWER (Good forever!)
MAPDATA.DAT - ASCII game map for RISE TO POWER-DO NOT ALTER!
FILE_ID.DIZ - ASCII Description File for BBS Sysops on RTP
HISTORY.DOC - RTP Version History information file
SYSOP.DOC - This text file you are reading
UPGRADE.DOC - If you are upgrading - read this first!
MAINT.EXE - Nightly maintenance program for RISE TO POWER
RTP.EXE - RISE TO POWER Main Program
RTPEDIT.EXE - RISE TO POWER Game Editor Program
RTPINIT.EXE - RISE TO POWER Game Initializing Program
REGISTER.FRM - Preprinted registration form and mailer
BUGRPT.FRM - Preprinted bug report/suggestion/comment form and mailer
INSTRUCT.TXT - Game Player Instructions for RISE TO POWER
*RTP.ZIP - Compressed copy of the above instructions to make
available on your BBS for download by players of the game.
Files created by RISE TO POWER upon initialization:
COUNTRY.DAT - Province Information file
GEN.DAT - General Information file
GLOB.DAT - Global variables Information File
MAP.DAT - Map Information File
MESSAGE.DAT - Message Storage File
NEWS.DAT - News and Player Log Information File
PLAYER.DAT - Player Information File
Files created by RISE TO POWER when first played:
RTPSCORE.DAT - ASCII Scores information Bulletin
KILLEM.DAT - Created to store deleted players temporarily.
Installation
------------
1. Create a directory for the game (example: "WC30\DOORS\RTP")
2. Make sure that ALL files listed above from the RTP190.ZIP file
are moved into that directory.
3. Edit the control file (RTP.CTL) for your type of BBS software,
user name, etc. The control file should be self-explanatory.
4. Edit the Key.DAT file. Line #1 should be the sysops name, Line
#2 should be the name of the using BBS, do NOT change or edit
line #3.
5. Install the door into your BBS software (see your BBS software
documentation for more information). A batch file is normally
used to do this. To run the program just have your batch file
change to the RTP directory and run RTP.EXE - That's all there
is to it! A sample DOOR.SYS type batch file (SAMPLE.BAT) has
been included with the game for editing and your use. For
dorinfo systems use the following:
Sample Batch File
-----------------
COPY DORINFOx.DEF \RBBS\DOORS\RTP\*.*
CD \RBBS\DOORS\RTP
RTP x <-=- NODE number !!DO NOT USE "x"!!
del dorinfox.def
CD \RBBS
-=*=- Please note that you replace the "x" with the appropriate node
number. Ex: Dorinfo1.def ; Dorinfo2.def ; etc...
6. Run RTPINIT.EXE to initialize the game and create required game
data files. This file automatically initializes the game with
default values. If you are a REGISTERED user and want to run a
custom game use the RTPEDIT.EXE program instead of the RTPINIT.EXE
program. The RTPEDIT program will NOT function unless you are
registered.
7. Manually run MAINT.EXE to initialize quests and other required game
information. Thereafter make sure your BBS Software runs the
MAINT.EXE program on a daily basis as an event. One note on
maintenance: Players will be automatically deleted after 10 days
of inactivity.
8. If you would like a score bulletin just have the game batch file
copy the RTPSCORE.DAT file to wherever you have your bulletins.
Example:
Copy C:\WC30\DOORS\RTP\RTPSCORE.DAT C:\WC30\BULL\BULL11.BBS
9. If you would like the news file to become a bulletin just have the
game batch file copy the NEWS.DAT file to wherever you have your
bulletins. Example:
Copy C:\WC30\DOORS\RTP\NEWS.DAT C:\WC30\BULL\BULL12.BBS
RESTRICTIONS ON THE UNREGISTERED GAME
-------------------------------------
Until the game is registered the following restrictions
are in effect:
a. Game time is limited to less then 10 minutes per player.
b. The Game editor (RTPEDIT.EXE) cannot be used.
c. The game is limited to 10 players.
d. There will be a slight delay experienced by players at the
beginning of the game.
Local Mode
----------
"RTP/L" will get you there.
Glossary of Terms
-----------------
Here is a brief guide to a few terms that I will be using in this
document:
BAUD - The speed at which the user is calling.
DOOR.SYS - Common drop file used by a variety of BBS programs. It is
the one I use on my BBS to run RTP, and therefore, the
most reliable.
DROP FILE - The file that is created by the bbs program when it goes to
execute the door. It contains the baud rate, com port,
name of the user on-line, etc. Common drop files are
DORINFO.DEF, DOOR.SYS, PCBOARD.SYS, EXITINFO.DAT, etc.
LOCKED BAUD - In order to get the most efficiency out of a high speed
error correcting modem (9600 baud or above), you must
lock the baud rate to a speed higher than what the caller
is actually using. By locking the baud to 38,400, the
modem can actually compress the data that is being sent
and achieve a baud rate much higher than the actual
transmission rate.
RTP - "Rise To Power", the name of this game.
MAINT - Maintenance mode. RTP must perform maintenance once per day to
do various things with it's data files.
MULTINODE - A BBS system with either more than one computer attached
or using a multi tasker (desqview, windows) that allows
more than one person to call at a time.
NODE - Refers to a member of a multinode system.
Command Line Switches
---------------------
/L Load in Local mode.
/Nx Specifies node number. (i.e. /N1 for node 1, /N2 for node 2,
etc.)
/Pyy Specifies path to drop files. (i.e. /PC:\BBS, for c:\bbs, etc.)
/Bxxxx Specify lock baud rate. For example "/B38400" would force the
comport to be 38,400 baud no matter what the drop file says
the baud is (i.e.; like door.sys). Only use IF the RTP.CTL
locked baud section does NOT work.
Multinode use
-------------
RTP does NOT allow multinode use. I have no plans at this time to
develop a version of RTP that does.
Common Problems (Locked Bauds, High Speed modems, etc.)
------------------------------------------------------
1. The game does NOT require a fossil driver to run.
2. If you are running a high speed modem (9600 baud or above), then I
suggest you run your bbs/mailer/doors at a locked baud rate. On high
speed error correcting modems, locking the baud rate will have a
noticeable increase on the speed of text that is sent. It's beyond
the scope of this document to discuss configuring your BBS and
mailer for a locked baud rate; you may wish to consult those docs
for information on that. Here are a few things to keep in mind when
setting up RTP with a locked baud rate:
a. When using a locked baud rate, I highly recommend using a FOSSIL
driver. RTP will work at high speeds without one though. BNU is a
good fossil driver which can even be loaded and unloaded before/after
you run RTP.
b. If you are using a fossil, then make sure to tell the fossil
that the port is locked. For BNU, to lock com1: at 38,400, you
would use something like "L0=38400" on BNU's command line.
c. If you lock the baud for one program, it must be locked
for everything. You can't lock the baud for just RTP, but not
your BBS/mailer.
d. You may need to use the /B switch on the RTP Command line to
specify the locked baud rate. For 19,200 this would be "/B19200"
and for 38,400 this would be "/B38400". Please note there is no
space between the "/B" and the baud rate.
3. What follows is some information on possible strange situations
that may occur:
a. Low speed users can play RTP, but high speed users get garbage.
- If you are not using the DORINFOx.DEF or DOOR.SYS drop file
then you may wish to find a converter program to convert
whatever drop file your BBS produces to the DORINFOx.DEF
or DOOR.SYS format and tell RTP to use that.
Several converter programs are readily available on most
BBS systems. CallDoor is a good one if you can find it.
b. RTP hangs up when a user enters the game.
- Sounds like RTP is getting the wrong baud rate somehow.
Try switching over to the DORINFOx.DEF drop file method
if possible.
c. Text and screens are getting cut off.
- If you are running with a locked baud, then this could
be caused by some sort of FLOW CONTROL problem. Try using
a fossil if you aren't already.
d. If you're using something other than the DOOR.SYS drop file,
then I always suggest trying to use DOOR.SYS if possible. It is
the most reliable method and has had the most testing. If that
is not possible try DORINFOx.DEF as an alternative.
Restarting the Game
-------------------
1. Run RTPINIT.EXE to initialize the new game files. If the old
ones are still in the directory, don't worry, the program will
simply overwrite them. It is not necessary to delete any files
before running the RTPINIT.EXE program. If you are a REGISTERED
user and want to run a custom game use the RTPEDIT.EXE program
instead of the RTPINIT.EXE program. The RTPEDIT program will NOT
function unless you are registered.
2. Run MAINT.EXE to setup the first quest.
3. That's it!
"Corrupted" data files
----------------------
It is possible that something could happen to your RTP data files. A
power outage, RTP crash, or other event could damage one of the data
files. If you get one of these messages, then the best thing to do is start
the game over with a clean copy of RTP.
CREDITS:
This relatively small section is just to recognize the GOOD people
who have made this door a possibility.
Chris R. Tynes -=*=- The original author of the source code on
which this game is based and who very
graciously allowed me to use it to make
this game.
Violet Stymacks -=*=- For her generous donation of the custom
ANSI art in this game.
Scott Baker -=*=- The author of the door driver package which
made this game possible. Great job Scott!!
Steven Lorenz -=*=- The author of the enhanced add on package
to Scott Bakers DoorDriver. Thanks to his
allowing me to use his modifications I
was able to delete the fossil requirement
and add many new communication enhancements
to the latest version of RTP. Thanks
Steve!
Charles Halsey, Marjorie Scofield, Adam Grandon, Hal Borland,
Titus Campbell, and many others for play testing the game on
the TANSTAFL BBS - Thanks guys!
Where to reach me
-----------------
I can usually be reached at my BBS system, which should be listed in the
section entitled "registration" which is below.
Registration
------------
If you or your users enjoy this game, then please register it.
Registration is $20.00 and you get a key code by mail or posted on my
BBS which will disable the delay, allow more players, allow more playing
time, allow use of the Game Editor and entitle you to life time support
through my BBS. BBS Support includes free updates through my BBS and
access to the RTP support conference on my BBS. To register this game
just print out the registration form (REGISTER.FRM) file included with
the game and send it with your check or money order for $20.00 to:
Robert A. Dalton
203 Old Farm Road
Harrison, AR 72601
HOW TO REACH ME BY MODEM
---------------------------
The TANSTAFL BBS (USA)
(501) 741-5699 (USR Dual- 2400 to 14400 baud)
Fidonet 1:391/1400
Reminder: You will be mailed a letter with your registration code.
Just allow an appropriate amount of time (a week or two) after dropping your
check in the mail for it to arrive to me and the code to be sent by mail
back to you. If you need it sooner log onto my BBS, leave me a message
telling me you mailed the registration and when I receive your check or
money order I will post a private message on the BBS giving you the key
code. If you do it this way please allow at least a week from the time
you mail it to the time you call and get your code. If you go the BBS
route you will NOT also receive a key code by mail.
Bug Reports/Comments/Suggestions
--------------------------------
I have made every attempt to make sure the game is free of bugs, BUT the
possibility always exists that one may have been missed by me or the
playtesters. If you find a bug, or have a suggestion or comment to make
which would make future versions better please print out the BUGRPT.FRM and
mailer, fill it out, and send it to me. I read ALL of them and those people
that lead me to find a bug or generate a better game will receive credit in
the game documentation.
FUTURE PLANS
------------
I intend to add more events, more weapons, more KING options, etc. to future
versions of RTP. Also I hope to add a RIP version someday soon. Once you
are registered any future updates can be obtained free through my BBS and
my upgrades are ALWAYS easy to implement!
FIDO INFORMATION
----------------
My BBS supports file "freq"ing at 9600 baud or above. Just call 1:391/1400.
I also carry a door library of over 250 of the all time best door games which
I try to keep current. For a list of these doors just freq "DOORS". I am
always adding new things to my games so most likely there will be a later
version of the program available on my BBS then the one you have. For
a current version of RTP just freq "RTP". For a list of ALL my files just
freq "TANSTAFL.ZIP". If you are a door game/program writer why not send me
a copy of your game/program? If you have a more current version of a door
then I have, please consider sending me a copy as a token of your
appreciation for the service I offer at NO cost to you. Thanks!