home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
PC-Online 1998 February
/
PCOnline_02_1998.iso
/
filesbbs
/
dos
/
stupd190.exe
/
ARCHIVE
< prev
next >
Wrap
Text File
|
1996-10-14
|
1MB
|
16,664 lines
─────────────────────────────┬────────────────────┬────────────────────────────
│ │
│ VGA Planets Door │
│ │
└ ┘
▓▓▓▓▓▓▒
▒▒▒▒▓▓▒▒▒▒░
▒▒▒▒▒▒▒▒▒░░░░
▒▒░░░░▒▒▒▒▒░░░░
▒░░░░░░░▒▒▒░░░░
▒░░░░░░▒▒▒▒░░
▒▒▒░▒▒▒▒▒░░
▒▒▓▓▓▒▒
┌ ┐
│ by │
│ Weird Al Walker │
│ │
│ Documentation │
│ Weird Al │
│ and │
│ Dragonlord Valheru │
─────────────────────────────┴────────────────────┴────────────────────────────
1.0 Disclaimer
1.1 -=( Why S.T.U.P.I.D.? )=-
2.0 Introduction to VGA Planets
3.0 Features of this Door
4.0 System Requirements
5.0 Archive Contents
6.0 "Quick and Dirty" door installation
7.0 Configuring the Door
7.1 RIP compatibility
7.2 Language File
7.3 Custom Game List Files
8.0 Using Custom Maps with VP-DOOR
8.1 Using Custom Ships with VP-DOOR
8.2 Using WORMHOLE.EXE with VP-DOOR
9.0 Hosting a Game
10.0 How to "Do" Remote Games with this Door
11.0 Switching from Other Planets Doors
12.0 Door Maintenance
13.0 The Menus
13.1 -=( Main Menu )=-
13.2 -=( Help Menu )=-
13.3 -=( Host Menu )=-
13.4 -=( Host.Configure Menu )=-
13.5 -=( Remote Menu )=-
13.6 -=( Stars! Menu )=-
14.0 Support Files
15.0 Multi-Node Operation
16.0 Stars! Support
17.0 StupidFix Internet Interface
Table A : Color Codes
Table B : Definitions
Table C : Command Line Options
Table D : Registration & "Adopting the Door" NOW ACCEPTING VISA!
Table E : Reporting Bugs
Table F : Extra Utilities for S.T.U.P.I.D.
1.0 Disclaimer
───────────────────────────────────────────────────────────────────────────────
Hmmm.... Legal stuff... Bah humbug.
Properly configured, this door should do nothing bad to your system. It
won't format your harddrive, it won't delete your root directory, or anything
like that, even if you *do* decide to use it past the 30 day trial time...
But if it does (and it hasn't on my system), I take no responsibility...
Works fine on my system. It's only guaranteed to take up space on whatever
form of media it's on.
1.1 -=( Why S.T.U.P.I.D.? )=-
Well, one of the big reasons I haven't released my door until now is that,
simply put, with all the VGA Planets doors out there, all the names are taken!
When I started working on it, there was no "VP-DOOR" (at least, not that I
knew of). And there were very few other doors out there.
Also, my BBS was put up for the express reason of testing my own BBS doors.
I have written many of them, and I only allow Doors written in my area to be
put online.... No BRE, SRE, L.O.R.D, TW2002, etc etc etc... So I couldn't
put anyone elses online...
S.T.U.P.I.D. stands for: Simply The Ultimate Planets Interface Door.
And that's what I think of it.
2.0 Introduction to VGA Planets
───────────────────────────────────────────────────────────────────────────────
VGA Planets is a game of interstellar conquest, generally managed by a bbs
but played offline. You are playing one (or more) of eleven races, each with
it's own combination of strengths and weaknesses, ships and racial abilities.
You must gather your resources together and push out among the 500 stars in
your cluster and, through either conquest or trade, be the strongest race.
On the hosts side, the bbs, turns are collected and processed to be down-
loaded by the players when maintenance is done. The player downloads their
result file, plays the game, and then uploads the turn file for the cycle
to repeat itself until the game ends.
VGA planets requires a minimum 286 IBM compatible computer,approximatly
1 MB of hard drive space free, and 16 colour hi resolution VGA capability.
Oh yeah, having at least 2 thirds of your lifespan on earth to spend on
this addictive game helps too.
3.0 Features of this Door
───────────────────────────────────────────────────────────────────────────────
* Full RIP graphics support! Customizable ASC, ANS & Rip screens
* Full protection for .TRN & .RST files from unauthorized users
* "Offline Mail Door"-like interface that allows user to get their files
in less than a minute!
* Automatic stale turn detection (local & remote games)
* SHARE & Multinode safe (plus -RA switch to force DORINFO1.DEF usage)
* 100 games maximum (but who'd want more?) (per game list!)
* Completely separate lists of games using the same copy of the door
* Built in ZModem routines, or allows use of External routines
* Customizable "Language" file (edit ANY text for the "custom look")
* StupidFix - built in Internet/UUCP mail interface to allow Internet players
to join, quit, request Score & Turns In logs, resend packet, etc
* STARS! Support menu, including StarsFix Internet access
* Full featured remote-hosting, including:
- Remote MASTER2.EXE, RCONFIG.EXE, KILLRACE.EXE, BLANK.EXE, CRACK.EXE
SPLITVH.EXE, CPLAYER.EXE, WORM.EXE, VPC.EXE (VPMovie recorder), HOSTFIX.EXE
(These utilities must be in the Planets Directory, to use them)
- Direct support for RAGNAROK "armageddon" program
- Complete control of days played, and configurable .BATs
- Automatically makes daily or full week's backup of game files
- How many races a player can play
- If new players can join in ("Game Locking")
- Viewing .VCR files of all players (through SPLITVH.EXE)
- Ability to upload custom universes (VPCEW or others)
- Difficulty Level of the CPlayer
- Complete, built-in Wormhole editor
- Specific users can be given Sysop/Host access to door
* Single or Multiple HOST runs per day (configurable by game host)
* "Fuzzy Logic" - runs host only when all .TRNs are in (Host can set maximum
number of skipped turns)
- Game starts automatically after X players join
- Automatically removes players who drop out
* Built-in Message writing capability to Players or Host
* Complete Custom Map & AltShip support
* User can have CPU play for missed turns, after preset number of missed turns
* "Other BBS" lister, with area-code search
* Specific user hosting access or "no join" access
* Custom race names, editable by player or host
* In-door access to download Planets utilities & files
* Full logging of Users (and Hosts) activities
* Logging of TRNs turned in on time/missed turns/cplayed turns/dead players...
in ASCII & ANSI versions...
* ASCII & ANSI Score files, plus High Score list & Who's playing
* Archived .RST packets, containing RACE.NM, .RSTs for that player, and if
that game is using a custom Starmap, a copy of the map. If custom
ships are being used, *SPEC.DAT and TRUEHULL.DAT
will be included as well, automatically,
unless "Include Data Files" off...
* User can view his in-game password (in case he forgets it, or someone
quits & leaves an unknown password on it...)
* Users can view the configuration (HCONFIG.HST) online! Upgradable for
future Host releases!
* Full "remote" game support, in whatever format you use...
- File attach/request utility (VP-MAIL.EXE) included...
* "Team Password" - Allows everyone in Team to download & upload packets
4.0 System Requirements
───────────────────────────────────────────────────────────────────────────────
This door does not require much in the way of a host sytem. It uses the
text version of MASTER.EXE to setup a VGAP game within the door, so the host
does not need a VGA card.
This (and all of my doors) uses a FOSSIL for output to the modem. BNU is
the one that I use, and have had little problem with it.
In the default setup, I use PKZIP as an archiver; I have the program swap
to EMS (or Disk if EMS not available), so I am not sure how much memory the
door needs. If the program is unable to create the game packets, increase
the memory available...
5.0 Archive Contents
───────────────────────────────────────────────────────────────────────────────
The VP-DOOR archive contains the following files. If any are added, or
missing, a proper archive can be obtained from Crazy Train ][ at
(604) 383-2201... All files will have the date of 10-14-96, 12:00 pm.
!READ.ME
ARCHIVE
DESC.SDI
FILE_ID.DIZ
INSTALL.EXE
OFFER.TXT
Q&A.TXT
REG-FORM.TXT
UPDATE.TXT
These files are explained further on in this file...
6.0 "Quick and Dirty" door installation
───────────────────────────────────────────────────────────────────────────────
All you need to do to set up the door "default" is to create a separate
directory for the door, dearchive the STUPID archive in it, run INSTALL.EXE,
change a few things in VP-DOOR.CFG & PID.BAT and make your BBS run PID.BAT
when someone wants to use the door, and VP-MAINT.EXE /B when it's time to run
HOST. You will also want to edit "FILES", which is the list of files available
in the "Files" menu... (be sure to have a blank line at the end of the list)
Do *NOT* put this door in the same directory as HOST.EXE or any other
planets files. This door was designed to be in a completely separate area
from the planets files!
You may also want to edit *.VP to give the door your own look.
Your "midnight" batch file must also execute RUNGAMES.BAT, that VP-MAINT
creates.
You can then, if you wish, start your own game in the door, and then
delete the one that comes with the door.
7.0 Configuring the Door
───────────────────────────────────────────────────────────────────────────────
Edit VP-DOOR.CFG... Just about everything you need to change is in there.
Edit FILES... Change the files available for downloading from the door, or
at least change the paths to point to your Planets file area.
(Be sure to leave a blank line at the end of the list)
Edit PID.BAT... to conform to your path setup...
You can also edit VP-DOOR.LNG, which contains all of the text in the door.
See 7.2 "Language File" below for more details...
You can basically edit any of the files in the Door Directory, but if you
screw something up, re-install it...
If you want to use the Team Password option, the team must choose a password
for their .RSTs. Any team member with a Team Password matching the rest of
the Team's passwords will get those team member's .RSTs in addition to his
own in his Game Packet.
If you want the game to start after a certain number of people join, set it
in the Host/Configure/Play Days menu. The next day that the game is due to
run, it will check to make sure the required number have joined. Once the game
has started this option will do nothing.
7.1 Rip Compatibility
In this version, I've added .RIP support. You can configure whether it
will be available to users with the AllowRip keyword in VP-DOOR.CFG. If it
is allowed, the door will auto-detect Rip and enable it if available.
The door will look for .VPR files for the Welcome screen and the Exit screen,
and also put up "quick pick" menu bars for 99.9% of the options in the door.
If you use the -R command line option, the door won't bother detecting
Rip and assume it's available. (You've been warned... <g>)
When the door is done and returns to the BBS, it will TURN OFF RIP. Be
sure, if you want the BBS to stay in Rip mode, that you turn it back on with
the {esc}[2! sequence (or that the BBS does this automatically)...
7.2 Language File
New in version 1.7 is COMPLETE text configurability, in the form of a
"language file". This allows you to go through and configure the door to
look exactly like you want it to. If you don't like the way I explain that
"Forced HOST is Unavailable... Contact the Sysop", change it!
In the language file is a couple of tags:
[#] : The index number of the text being replaced
[key] : Used to denote that the door is going to wait for input of the keys
following [key] and before the first [opt]
[opt] : First letter after [opt] is the key that the option will display for,
followed by the text displayed when the user presses that key
[end] : at the end of each definition
[comment ...] : Everything after "comment" and before the next ] is ignored
(I would not recommend that you use the character "[" anywhere in your changes.)
Basically, this replaces (completely) VP-DOOR.DAT. If you don't understand
what you are doing when modifying this file (VP-DOOR.LNG), *DON'T*...
Even if you DO understand how this language file works, DO NOT make
"fundamental" changes to this file, such as:
Deleting whole index numbers
Adding [key]...[opt]... 's when they aren't already there
Changing [key] statements (the door will be looking for them)
Adding new index numbers (the door won't look for them)
Any changes you make will then need to be compiled with the VP-MAINT /L
command.
7.3 Custom Game List Files
Say you were to want to have a list of games for new players, and a list
for "old pros"... You would want to have the Pro games separate from the new
players, so they wouldn't "accidently" join. Until now this meant having a
separate copy of the door for each "batch" of games you wanted to run. Not
any more.
You can now use the -G{gamelist} command line option to have different lists
of games... For example:
Say you had an option from your BBS, that says "Novice Planets Games", and one
that's called "Advanced Planets Games". The "Novice" option would run
"NOVICE.BAT", which would be:
c:
cd \DOORS\STUPID
VP-DOOR -L38400 -GNOVICE
cd \BBS
... then the "Advanced" option would run, say, "ADVANCED.BAT":
c:
cd \DOORS\STUPID
VP-DOOR -L38400 -GADVANCED
cd \BBS
The list of games for the Novice players would be COMPLETELY separate from
the advanced players... (But you must remember to run VP-MAINT -B -G{gamename}
as well, because without the -G, "GAMES" is the file it looks for...)
8.0 Using Custom Maps with VP-DOOR
───────────────────────────────────────────────────────────────────────────────
Simply add a valid Map file to the MAPS directory, and a description of
it in the file MAPNAMES.
You can create maps with whatever program you like, but I recommend
MAKEMAPS, written by myself and William Barath...
8.1 Using Custom Ships with VP-DOOR
If you are using one of the ALTSHIPS editors or something similar, just
add the *SPEC.DAT and TRUEHULL.DAT files to the Game directory. If the
door detects ALL of these files, they will be included in the HOST run, and
given to all players in their .RST packets.
8.2 Using WORMHOLE.EXE with VP-DOOR
WORMHOLE.EXE is a program that allows you to create "holes" between one
spot in the universe and another, any distance away... You can even make the
wormhole 1-way (which would be a nasty way to warp some guy to 1000 LY OUT-
SIDE the known universe.... you could then engineer a planet way out there
[with MAKEMAPS, and the scenario editor...] ... maybe one that has the
Tantilus device on it?) The possibilities are endless.
To use WORMHOLE.EXE, you must have a formatted text file containing the
coordinates of the wormholes called WORMHOLE.TXT. Read the docs with WORM-
HOLE.EXE for more details on this format.
Fortunately, you don't have to understand wormholes to use them, now that
I have an integrated WORMHOLE.TXT editor built in to the Host menu. All you
have to do is create holes where you want them, and make sure WORMHOLE.EXE
is available in the Planets Directory.
9.0 Hosting a Game
───────────────────────────────────────────────────────────────────────────────
Once in the door, press (S) to start a new game. If you follow the prompts,
you should have the framework of a new VGAP game ready to go. Utilities
currently supported by the door include missions, custom starmaps, custom
scenarios, and any others that can be run in maintenance.
Races can be configured as being "CPU Only", in which they are unavailable
to players, and the "CPlayer" flag has already been set on them. Be sure the
sysop has set VP-DOOR.CFG to allow CPlayers...
If you wish to create a custom .BATch file to be run when it's time to
run your game, simply include "GAME.BAT" in the game directory. When it is
called, it will be called with the current gamename & CPlayer players (in
standard 123456789ab format) as parameters...
But, if you simply want to use the pre-built RUNGAMES.BAT, but you want
to add something like VPHOST.EXE to the run, you can create "BEFORE.BAT"
and/or "AFTER.BAT", which will run immediately before & after HOST.EXE,
within RUNGAMES.BAT. BEFORE & AFTER.BAT will also be called with the 2
parameters mentioned above...
If you would like to customize the CPlayer being used, you can make it a
batch file. For example:
CPLAYER.BAT:
DOMINATE %1
... would use DOMINATE with the /123456789ab (or whatever races were
configured to run) instead of the CPLAYER program (but be sure that there is
a CPLAYER.BAT, but *not* a CPLAYER.EXE file on the path, as DOS would use
CPLAYER.EXE before .BAT...)
Before starting a game, it would be a good idea to set up the host options
on your side, with the latest version of HCONFIG.EXE, modifying HCONFIG.HST
to your satisfaction. This file can be uploaded to the door once the new
game is setup. To upload them, access the host menu (press "X"), then press
"C"onfigure game.
Another option the door allows is for you to download a copy of the Universe
files and modify them with VPCEW.EXE, which is a universe/starbase editor.
You can then upload your new copy of the Universe (.ZIPped up).
This will allow you to create custom scenarios such as:
1. Each race owning 20 Planets, 3 Starbases, and 5 of each ship.
2. Each homeworld having a 10,000,000 Bovinoid Unity on it. (!)
3. Colonies of Man owns 12 BattleStars, 12 Planets, and lots of
little ships; The Robots own no planets, few support ships,
and at least 10 Instrumentality Class. Recreate
"Battlestar: Galactica"!
4. Create a planet waaaaaaaaaaaaaaay off in the distance, set it
up as having the Tantilus Device, and a wormhole (or a maze of
them) the only way to get to it...
5. ANY of the already pre-made scenarios.
6. A custom starmap not available within the door (if there are any!)
* REMEMBER * the universe is sent to you ZIPped. You *MUST* send
it back the same way!
Once the first turn is processed, the game files (other than HCONFIG.HST)
cannot be downloaded or uploaded, to prevent Host cheating.
Now you should go into the appropriate message areas on the bbs to make
the new game known and attract some players. Be helpful to everyone, even
new players. After all, it isn't much of a VGAP game with only the host
playing against 10 Cplayers (unless the difficulty is set high :) ).
If you want to use the Team Password option, the team must choose a password
for their .RSTs. Any team member with a Team Password matching the rest of
the Team's passwords will get those team member's .RSTs in addition to his
own in his Game Packet.
When you have enough players that you think it's worth starting the game,
go into the (X) or hosts' menu again and configure the game to run the
maintanence on the appropriate days. For example, if you set it to Sunday,
Monday, Thursday, then the turn files should be in by Saturday, Sunday, and
Wednesday nights so that the players may download their result files the
next day.
If you want the game to start after a certain number of people join, set it
in the Host/Configure/Play Days menu. The next day that the game is due to
run, it will check to make sure the required number have joined. Once the game
has started this option will do nothing.
Or, if you want to have the game run only if the player's .TRNs are in,
set the day(s) to "T" (fuzzy logic). You can also set the turns to run
multiple times per day (assuming the Sysop runs VP-MAINT /B more than once
per day). This way, with both "T" days and multiple runs per day, you
could have "Turbo" games where 2 or more people play as many turns in a day
as you can get your .TRNs in for! You will also be asked how many turns
to skip, maximum.
For example, you set the game to only run when the players have their turns
in, and one player drops out without telling anyone. If you've set the game
to skip 7 turns maximum, then the game will force a run after 7 skipped turns.
This allows you sort of a "dead man's switch" that will continue a game even if
people drop out.
If you find that you are short of players, or want to run Cplayer on
an empire, you may also configure this under the (C)onfigure game option in
the host menu, and set the difficulty level (1-3). (This gives the CPlayer
extra "turns", which increases the difficulty, but also the level at which
he "cheats"... You've been warned... 8) )
If you want to "force" HOST.EXE to run, you must make sure that there is
enough memory available, or one or more of the programs within RUNGAMES.BAT
will not run. Check with the Sysop.
If, for some reason, you don't want to have the game run for 1 turn, just
create a file (any file) in the game directory called "SKIPTURN". Processing
will be skipped for that game for *1* turn. "SKIPTURN" is then deleted, so
that the game will run the NEXT turn.
If you want to suspend the game indefinately, you just create a file
called "SUSPEND" in the game directory. The game will be suspended until that
file is deleted.
If there is someone (or lots of someones) who you don't want to give
access to the "Join Game" option, simply add his name to a file in the
door directory called "NOJOIN", in ALL UPPER CASE.
10.0 How to "Do" Remote Games with this Door
───────────────────────────────────────────────────────────────────────────────
The methods I am about to explain have already been tested on ShareNet,
and has worked flawlessly. It provides protection for both the .TRNs and
.RSTs from unauthorized access...
VP-MAINT /M{user_name} will create a Game Packet for "User Name",
including custom maps and AltShips, if neccessary.
Hosting Locally:
It's mostly done with .BATch files... For this example, we will
assume that you are hosting a game, and, say, "HammerTime BBS" has 2 people
who want to play in it, as the Fascists & the Borg.
1. Set up your "ALIAS" file (where you put your "Magic" filenames) with
a "password" that points to an archive containing all of the
.RSTs that must go to "HammerTime BBS".
(In FDSetup, "MAILER/FILE REQUESTS/ALIAS FILE"). Alternately, you
could make a separate directory (if you have lots of BBSs grabbing
.RSTs) that is only available through FREQ, and put all the .RST
archives in there ("MAILER/FILE REQUESTS/LIST FILE"). These examples
are for Front Door; if you are using a different mailer, you can do
something similar...
Now lets say for our example you've made it so that "HammerTime" can
FREQ "HT1234" and get "HT_RST.ZIP".
2. Set up your nightly batch file to make an archive called "HT_RST.ZIP"
containing "PLAYER4.RST" (Fascist) and "PLAYER6.RST" (Borg) from
the game, and put it where the Alias (or List) file expects it.
3. Set up your Front Door "Mail Recieved" .BAT to check for "HT_TRN.ZIP"
(Or whatever you tell the remote system to upload his .TRNs in).
If it finds it, de-archive it into a temporary directory, and copy
ONLY "PLAYER4.TRN" and "PLAYER6.TRN" into the game directory (you
can also check the .TRNs' staleness at this time, if you wish).
The .RSTs are now available for the Host when it normally runs.
Hosting Remotely:
...is even easier. Simply set up "REMOTE.DAT" (in the Door Directory)
as follows (reverse the previous example; you are sending to "Hammertime"):
NAME OF PLAYER (Uppercase)
Short, one line description of this game ("HammerTime BBS Game 6, The Borg")
FILENAME OF BULLETIN
FILENAME OF .RST
FILENAME OF .TRN
{blank line}
NEXT PLAYER....
So, for our example:
JOE BLOW
Hammertime BBS Game 6, The Fascists
CRASH.BUL
PLAYER4.RST
PLAYER4.TRN
JOHN SMITH
Hammertime BBS Game 6, The Borg
CRASH.BUL
PLAYER6.RST
PLAYER6.TRN
(I don't recommend that you use these .RST & .TRN names; with lots of remote
games, you are very likely to get conflicts between game filenames. For our
example, "HTG6P4.RST", "HTG6P4.TRN", "HTG6P6.RST" and "HTG6P6.TRN" would work.
Be sure that the player renames *HIS* "PLAYER4.TRN" to "HTG6P4.TRN" or the
door will reject his upload...)
BULLETIN can be any text file, usually included with the .RST "packet"
sent from the host system. It can contain anything that would apply to
players in that game, or even just a BBS ad...
You then set up your .BAT files to pack up the files in the REMOTE
directory, and your events to send them to the remote host ("Hammertime")
before he runs "HOST.EXE" for the turn. You also want to have an event that
will grab the .RST archive after "HammerTime" makes it, and toss the .RSTs
in it to the REMOTE directory.
If the "RemoteStale" keyword is enabled in VP-DOOR.CFG, the door will
use the .RST to find the "time stamp" of the game, and detect the Staleness
of the .TRN. If you are using "game packets", where the .RST file named
is NOT an actual .RST file but actually a .ZIP (etc), as long as the "RST"
file (in REMOTE.DAT) does not end in .RST, the door will skip that stale
check. For example: The user downloads "SHARENET.ZIP" as his "RST" file
(somewhere in the archive would be his .RST), and then uploads "SHARENET.TRN"
as his .TRN... The door, seeing that the .RST is actually a .ZIP, will skip
the stale check on "SHARENET.TRN"...
11.0 Switching from Other Planets Doors
───────────────────────────────────────────────────────────────────────────────
There are many different VGA Planets doors out there.
Duh. No kidding.
What they basically all have in common is that they usually have a
directory containing the door, with sub-directories for each game. This is
how VP-DOOR is layed out:
VPDOOR
├───BACKUPS
├───MAPS
├───REMOTE
├───GAME1
├───GAME2
├───GAME3
└───etc etc etc...
(Of course, they don't have to be called "GAME1" etc... They can be given
a descriptive name like "MAIMGAME", "BORGDOOM", etc)
Each "Game" directory contains all the files VGA Planets uses for a game,
plus a few extra files:
GAME.REC - List of players, and other data.
TIY, TIYDAT - Created by VP-MAINT to keep track of turns
turned in on time, as well as CPU Players.
MISSION - Description of the Mission, if any
DESCLINE - One line (60 chars max) briefly describing game
OPTIONS - Description of Setup, created by Start Game
So all you need to do is install the door, create "Game" subdirectories
for each of your established games, move all the files from each game into
it's new directory, and create GAME.DAT, MISSION (if the game has one),
DESCLINE, and OPTIONS (a short description will do). You also need to add
the name of the subdirectory to the list "GAMES".
To create GAME.DAT, type VP-MAINT -E{gamename} where {gamename} is the
directory you moved that game's files into. It will prompt you to see if
you actually want to create the file. You then can edit the names of the
players in the game. (You can find out who is playing which race in the
"old" door by whatever means necessary.) If a race is not available to be
played, perhaps because it was never created by the original "MASTER", put
"*" (an asterisk) as the name of the player.
If you want someone else to host this game, you can edit this too. The game
will now be added to the list of games available, and whoever is configured
to be playing the races in that game can download their .RSTs...
If "REFDATA.HST" exists with the game files, you must create MISSION,
which is the description of the mission in this game. Use whatever text
editor you want to.
Then create DESCLINE and OPTIONS. Again, use whatever text editor you
want. They are both in plain ascii.
Once GAME.REC has been created, plus these other files, for each game,
you are done with the translation. Theoretically you could use other
doors at the same time as this one (since I doubt other doors would use
the same filenames as I do), but why?
12.0 Door Maintenance
───────────────────────────────────────────────────────────────────────────────
The door is pretty much self-maintaining, as long as the Host of the game
does his job... Contacting players that don't play for a while to see if they
want to pass the race off to someone else...
You may want to delete the VP-DOOR.LOG file once in a while... Especially
if it's set to "Trace", which will fill up your HD pretty quickly...
Every time you want to run the HOST in the games (ie Midnight), you must
run VP-MAINT -B... This will create RUNGAMES.BAT and clear the flags for
each player for the day. You can then call RUNGAMES.BAT in your regular
nightly batch(s)...
13.0 The Menus
───────────────────────────────────────────────────────────────────────────────
13.1 -=( Main Menu )=-
╔═══════════════════════════════════════════════════════════════════════╗
║ (A)bout this door (G)ood-Bye! (L)ist all games (T)urns in Log ║
║ (C)onfiguration (H)elp! (N]ext Game (U)pload .TRN ║
║ (D)ownload .RST (I)mmortals [P)rior Game (V)iew Scores ║
║ (E)dit race names (J)oin game (Q)uit to Main (X)tra Options ║
║ (F)iles for VGAP (K)ill race (S)tart a game (R)emote Games ║
╚═══════════════════════════════════════════════════════════════════════╝
(1-9) - Switch to game 1 - 9 (if they exist)
(A)bout this door - Display version and support info for this door
(C)onfiguration - Display configuration of game, including HCONFIG.HST
(D)ownload .RST - Download result packets for this or all games User is in
(E)dit - Allows User/Host to edit Long/Med/Short Race names,
Team Password for that user, or whether the CPU plays
"missed" turns
(F)iles for VGAP - Menu for files available through the door for downloading
- Delete "FILES" to remove this feature
(R)emote Games - Remote Games menu, if any
(G)ood-Bye! - Return to BBS, with "GOODBYE" in root directory
NOTE: if you want this to hang up on the user, you must
have the BBS check for "GOODBYE" yourself!
(H)elp! - Help menu
(I)mmortals - "High Scores" list
(J)oin game - Join in this game, if not locked and races available.
(K)ill race - Quit game, with Killrace if user wishes.
(L)ist all games - List games and brief description
(M)essage Menu - Allows user to send messages to other players & the Host
(N]ext Game - Switch to Next Game ( "." and "]" works too)
[P)rior Game - Switch to Last game ( "," and "[" works too)
(Q)uit to Main - Quit to the BBS
(S)tart a game - Start a new Game, if you have access to this feature
(T)urns in Log - Log of TRNs in on time, dead players, CPlayer races, etc
(U)pload .TRN - Upload .TRN for any game you are in (auto-detect)
NOTE: You do NOT have to switch to the game you want to
upload to! It is all automatic!
(V)iew Scores - View scores in this game, if not BLANKed; also +- of each
(X)tra Options - Host menu, if User is Host of this game
13.2 -=( Help Menu )=- ┌────────┐
│ Help │
┌───────────────────────────────┴────────┴───────────────────────────────────┐
│ 1) Introduction to VGA Planets 3.00 │
│ 2) How to Play a Turn │
│ 3) Racial Advantages │
│ 4) Hints & Tips │
│ 5) Registering the Game - Only $15 for Tech 10 stuff, Maps, "Cheats" etc │
│ 6) About the VGAPlanets Player Interface Door │
│ 7) How to "Host" your OWN game │
│ 8) All about "Missions" │
└────────────────────────────────────────────────────────────────────────────┘
Help Topic (CR to Quit):
This menu is completely configurable. Change HELPLIST.VP* to let the users
know which "help options" are available (in this case, 1-8). You then make a
HELP-?.VP* to correspond with them. The program looks for HELP-{keypress}.VP
and displays it... So if the user presses "K", HELP-K.VP* will be displayed.
13.3 -=( Host Menu )=-
╔═════════════════════════════════════════════════════════════════════════╗
║ (T)urns in Log (M)emory Available (F)orce HOST run (*)Snoop VCRs ║
║ (C)onfigure Game (V)iew Logs (W)ho's Playing (P)revious Menu ║
║ (R)emove Game (Z)Crack Passwords (D)el OLDFIG.HST (E)dit Player ║
║ (@)Wormhole Editor (G)oodbye! (Q)uit to BBS ║
╚═════════════════════════════════════════════════════════════════════════╝
(C)onfigure Game - Switch to Host.Configure menu
(T)urns in Log - Same as main menu
(V)iew LOGs - Display HOST.LOG, REG.LOG, or VP-DOOR.LOG
(W)ho's Playing - Display who is playing which race in this game
(R)emove Game - Kills the game, and asks if you want to add to Hall of Fame
- Also asks if you want to download the .VPM movie
file (if it exists)
(*)Snoop VCRs - In local mode, run SHOWVCR.EXE; remotely, send archive of
all .SVRs for remote to run SHOWVCR on.
(Z)Crack Passwords- Uses CRACK.EXE to show all passwords in this game
(D)elete OLDFIG.HST - If OLDFIG.HST is not the same as HCONFIG.HST, or does not
exist, the 4-5 page configuration messages are sent
to the players by HOST.EXE automatically
(M)emory Available- For "Forcing HOST run", check available memory first
(F)orce HOST run - Create a "RUNGAMES.BAT" for that game and execute it
- be sure you have enough memory!
(E)dit Player - Game/Player editor
(@)Wormhole Editor- Invoke Wormhole Editor
(P)revious Menu - Return to main menu
(G)ood-Bye! - Same as main menu
(Q)uit to BBS - Same as main menu
13.4 -=( Host.Configure Menu )=-
A. Locked Game : No
B. Max Races per User : 1
C. Days Played : |SMTWTFS| (ONCE per day)
D. Blank (Invisible) Scores: No
E. Run CPLAYER on : 247 (Level 2)
F. Change game description
G. Download HCONFIG.HST
H. Upload HCONFIG.HST
I. Create/Modify Mission (Current mission: ---<<<<NO MISSION>>>>--- )
J. Download Universe Files
K. Upload Universe Files
Most of these options are pretty much self-explanitory... Blank Scores
must have BLANK.EXE available to use. CPLAYER must have CPLAYER.EXE avail-
able. Upload HCONFIG.HST will only allow host to upload HCONFIG.HST.
Download/Upload Universe files is only available BEFORE the game runs it's
first HOST.EXE... Days Played applies to when RUNGAMES.BAT is created...
In "Days Played", if you want the game to only play when all the .TRNs
are in for all "joined" players. You can also set the door to run more
than once per day (assuming the Sysop sets the BBS up to run VP-MAINT /B
more than once per day, and is willing to run RUNGAMES.BAT...). It can also
be set up to start once X players have joined in...
I was thinking of having an Upload/Download GAME.BAT, but since this has
such possibilities for security leaks, I suggest the Sysop should control
this feature...
13.5 -=( Remote Menu )=-
╔════════════════════════════════════════════════════════════════════════╗
║ (L)ist Remote Games (D)ownload .RST (U)pload .TRN (H)elp! ║
║ (B)ulletins (P)rev. Menu (G)oodbye (Q)uit to BBS ║
╚════════════════════════════════════════════════════════════════════════╝
(L)ist Remote Games - List all games user is in, with date of current file
(D)ownload .RST - Download .RST (or packet) configured in REMOTE.DAT
(U)pload .TRN - Upload .TRN (or packet) configured in REMOTE.DAT
(B)ulletins - View bulletin defined in REMOTE.DAT, if available
(H)elp! - Display HELP-R.VP
(P)rev. Menu - Return to main menu
(G)oodbye - Same as main menu
(Q)uit to BBS - Same as main menu
13.6 -=( Stars! Menu )=-
╔══════════════════════════════════════════════════════════════════════╗
║ (A)bout this door (H)elp! (L)ist all games ║
║ (U)pload Turn (J)oin Game (Q)uit to BBS (G)ood-Bye! ║
║ (D)ownload Turn (M)ap (Z)Novice On/Off ║
╚══════════════════════════════════════════════════════════════════════╝
(A)bout this door - Same as main menu
(H)elp! - Display HELP-S.VP
(L)ist all games - Displays S_GAMES.TXT
(U)pload Turn - Upload your {game}.Xn file(s)
(D)ownload Turn - Download your {game}.Mn file(s)
(J)oin Game - Join in game
(M)ap - Download {game}.XY file
(G)oodbye - Same as main menu
(Q)uit to BBS - Same as main menu
14.0 Support Files
───────────────────────────────────────────────────────────────────────────────
Files marked with "*" are included with the distribution archive.
* VP-DOOR.EXE - Main executable for door
* VP-DOOR.OVR
* VP-MAINT.EXE - Maintenance program for VP-DOOR. See "Maintenance".
* VP-MAINT.OVR
* VP-MAIL.EXE - Little utility for creating netmail FREQ/File Attach messages
* STUPDFIX.EXE - UUCP Internet "EMail" to S.T.U.P.I.D. interface program
* STUPDFIX.HLP - Sent by STUPIDFIX in response to empty or "help" messages
* HELPLIST.VP- Menu for Help files
* HELP-?.VP - Text files for the "Help" command (? is the menu option)
- *PAGE* to force a "Continue Y/N"
- *END* or end of file to end
* HELP-R.VP - Help file for Remote games.
* FILES - List of files available from the door, in the following format:
Full_Path_and_Filename(Wildcards_allowed)
Name/description/etc... Anything else you want; Blank line between entries.
Full_Path_and_Filename(Wildcards_allowed)
Name/description/etc... Anything else you want; Blank line between entries.
etc...
(BE SURE TO HAVE A BLANK LINE AT THE END OF THE LIST! IT USES THIS TO FIND THE
END OF A FILE DESCRIPTION!)
* GAMES - Made by door to hold list of games being played.
* MAPNAMES - Name and brief description of each map available.
- You *MUST* have this file, at least to use the Original
map! See example...
- First 13 characters of each line is the map filename.
* MAKEGAME - List of names, uppercase, who will have access to the
"Start a new Game" option. If this file is blank
or missing, only "SYSOP" has access.
COSYSOP - List of names, uppercase, who will have the same access in
the door as the Sysop of the BBS
* HALL - Created by the Door when running games are deleted.
Contains stats for the game (the "high score" list)
* VP-DOOR.CFG - See "Configuring the Door".
VP-DOOR.LOG - Created by door to log what happens in the door, and when.
* VP-DOOR.LNG - "Language" file for door. See Sections 7.0 & 7.2.
* VP-DOOR.LD & .LX - Compiled version of VP-DOOR.LNG
RUNGAMES.BAT- Created by VP-MAINT.EXE, to run all the games that are
due to be played that day.
GAME.BAT - If this file exists in the game directory, it will be run
INSTEAD of the "created" batch in RUNGAMES.BAT.
BEFORE.BAT, AFTER.BAT - If either of these exist in the Game directory,
it is run either before & after HOST.EXE, within RUNGAMES.BAT
* WELCOME.VP? - Shown to callers when they first enter the door.
"A" is Ansii version. "R" is Rip version.
* GOODBYE.VP? - Shown to callers after they press "G"oodbye, but before it
hangs up on them...
* BBSLIST.DAT - Renamed copy of BBS1995.DOC; any BBS list will work, as long
as the file is in the format:
(xxx) yyy-zzzz name...and...description...
(the area code must be wrapped in ()'s, and have a space after & before the
rest of the number for the search to work... also European numbers
must have the "+" before the country code)
* M-*.VP - Menu files (.VPA = Ansii version)
* BULLETIN.VP - "Bulletin" in door; shown between WELCOME.VP? and main menu.
* RETURN.VP? - Shown to callers when they exit the door.
"A" is Ansii version. "R" is Rip version.
* HCONFIG.LST - Taken from the HOST docs, it is the "Details of HCONFIG.HST".
Parsed to show users the setup of the current game.
* PKT_READ.ME - Included in the game packet sent to users for each game.
* SVR_READ.ME - Included in !*.zip file for "snooping" VCRs for game.
* LOCAL.BAT - Batch file to run door locally.
* PID.BAT - Sample batch to run VP-DOOR from the BBS.
* PLAY.BAT - Batch file users can use to play from packets made by door.
ZIP.LOG - Created whenever the archiver is run, for debugging lack
of memory or path problems
DEBUG.LOG - Created when the /DEBUG command line switch is used
* MAPS/*.MAP - Map files for "alternate" universes
BACKUPS directory - Directory where "backups" of games are kept before
HOST is run...
UPLOAD directory - Temporary directory where uploads are kept
REMOTE directory - Used for holding .TRNs and .RSTs for remote games.
See "Playing Remote Games".
The following files are used only if you want to run the Stars! Support part
of the door:
WELCOME.ST? - Shown to callers when they enter the door, in Stars! mode.
(Note: WELCOME.VP? shown if .ST? doesn't exist)
"A" is Ansii version. "R" is Rip version.
S_GAMES - List of games being played, one per line, uppercase
S_GAMES.TXT - List of games with their descriptions (in any format you
want to use)
{gamename}\WHO - List of all 16 players for this game, upper-case, one
per line. Even if there is not 16 players, all 16 lines *MUST* exist.
Fill non-human races with a ".", so nobody can join it
{gamename}\RACES - List describing races available. It should list all
races in the game, 1 to 16, with a "." for races not in game
Humanoid
Humanoid
Insectoid
Antetheral (Computer Player)
Rabbitoid (Computer Player)
.
.
.
.
[etc]
(in this case, the 4th through 16th line of RACES will have "." on them, so
someone doesn't join as them...)
15.0 Multi-Node Operation
───────────────────────────────────────────────────────────────────────────────
I have a single node BBS, and have no way (before I release this) to test
multi-node operation. But, unlike my other doors to date, I have attempted
to make this door as multi-node aware as possible.
If you specify the -N{node} option, all temporary files & directories
created by the door have the node number tagged on to the end of the name.
It will also be used to decide which DORINFO?.DEF to use (Default is
DORINFO1.DEF, if -N is <2 or >9...)
You can also use the /C{configfilename} switch to have the door use a
different .CFG file than VP-DOOR.CFG.
16.0 Stars! Support
───────────────────────────────────────────────────────────────────────────────
Stars! is a relatively new, Windows-based game similar to VGA Planets. Like
Planets, you start with a world & ships, and you have to take over the galaxy.
It has a number of features that Planets doesn't have, however.
Unfortunately, this is not an ad for Stars!, just a door that supports the
transfer of it's turn files. If you would like to try Stars!, it can be FREQ'd
or downloaded from my BBS as well as other Planets support BBSs.
If you don't know what Stars! is, you don't need this part of the docs. <g>
In order to play Stars! through this door, you must put the game files for
Stars! in their own directory (ie all of the player files, but NOT the .EXEs).
You need to create the game in a directory of the same name as the directory
(ie if you make a sub-directory of the door called "NUKE_EM" you need to have
the game files called NUKE_EM.XY, NUKE_EM.Mn, NUKE_EM.HST, etc, there...)
You also need a list in each game directory of WHO is playing (16 lines, each
with the name of who is playing it, upper case). This is in the file "WHO",
and even if a race is not being played, there *must* be 16 lines in this file.
To join in a game, there must be a list of the races available (one per
line, 16 lines, "." for races not in the game). This should be in a des-
cription file called "RACES", in the stars Game directory (the sub-directory
you put the *.XY, *.Mn etc files in). See the end of section 14.0 for an
example. If a race is NOT being played, put a "." as it's description so
nobody can join it.
Running the "host" is up to you. All this program does is send out the .XY
file, the *.Mn files and recieves the *.Xn files.
You can now use StarsFix, a sub-set of StupidFix, by simply sending message
to StarsFix instead of StupidFix...
17.0 StupidFix Internet Interface
───────────────────────────────────────────────────────────────────────────────
As of v1.8, I have created an interface to allow persons with a UUCP netmail
gateway to allow people to join, quit and play games via .UUEd files through
the internet.
Players access StupidFix by sending an Internet message to "StupidFix" with
commands in the message body. If they join in a game, they are assigned a
password (which can be changed at any time), which must then be included in
the Subject line of the message. This password is listed in STUPDFIX.PW (in
case they forget it and you need to tell them).
For example:
──────────────────────
To: StupidFix@f88.n340.z1.fidonet.org
Subj: password
Join killgame 6
──────────────────────
... would have the player join "killgame" as the Borg (if they are available,
and if the player isn't already playing too many races).
You must configure the keywords in VP-DOOR.CFG (NetmailID, MyAddress &
UUCPTo) correctly in order to use StupidFix.
Unfortunately (and I have thought *long* and *hard* on this one) STUPIDFIX
is unavailable to non-registered users of S.T.U.P.I.D... I am sorry, but
that is how it will have to be. I am saying this right now, in the docs, so
there will be no misunderstanding. If it is called, it will simply exit
without processing anything...
The following commands are available to players through the Internet:
JOIN gamename race#
Joins in Game "gamename" as race number "race#" (1-11), if it is
available. You will be told in a return message whether you got
the race or not.
QUIT gamename [race#]
Quits game "gamename" (if you are in it). If you run more than
one race and only want to quit ONE race, put the number of the
race after the name of the game. If "race#" is left off, all
races played in that game are dropped.
STATUS
Returns message describing your current status in the door.
TIY gamename
Returns a log of the .TRN files sent in on time, for all races. Also
logs CPU players and Dead players.
SCORE gamename
Returns the current Score for this game (if it hasn't been blanked by
the Host).
ABOUT gamename
Describes the setup of "gamename"; what days it plays, who the host
is, maximum number of races per player, whether it's locked or not,
how it is set up, and what the "mission" is, if any.
LIST
Sends list of all games available on this system, and what races
are available.
HELP
This list of commands.
RESEND gamename
Resends .UUE file(s) of your most recent .RST file packet(s).
You would also use this to get your first game packet from a game
that you have just joined but that has already started...
PASSWORD oldpassword newpassword
Changes your password for .UUE packets & STUPIDFIX commands. If
"oldpassword" does not match current password, this is ignored.
After you join in a game, you will be told when it starts (if it hasn't
already), and you will be sent a .UUE containing your .RST packet(s), a
copy of the packet's "read.me" file, a copy of the XYPLAN.DAT file (if the
game is using a custom map), a copy of RACE.NM, and if the game is using
custom *SPEC.DATs, they will be in the packet as well. Read the READ.ME
in the packet for more details.
When you have unpacked and played your turn, you then take the .TRN file(s)
and UUEncode them (one .TRN per message) and send them to StupidFix at the
address of the BBS you are playing on. (Be sure to include your password
in the Subject line of the message). The .TRN will be checked for staleness
when it arrives, and tossed into the appropriate game directory. (Don't
worry about if the Door will know which game you are playing in, it will
put the .TRN into the correct directory as long as it isn't stale...)
Note: For now, this program uses a very simple .UUE decoder, that does
NOT understand anything special in .UUEs (like extended checksums, compression
or anything "non-standard"). The best UUEncoder/Decoder that I have found
that works with StupidFix is "UU-DECODE 5.02 FOR PC. by Richard Marks". This
is available on Crazy Train ][ with the filename of "UU-ENDEC.ZIP".
Table A: Color Codes
───────────────────────────────────────────────────────────────────────────────
The following codes are supported wherever they are mentioned in the
documentation, such as in the "Files" menu, or in customizing the Menu options.
They are added so that people can "fancy up" their .VP files, without having
to go to the trouble of making an ANSI .VPA file.
Each letter must be preceded by the "~" symbol.
1 : {ANSI cleol} A : {ANSI foreground Black}
2 : {ANSI cls} B : {ANSI foreground Red}
3 : {ANSI Save Cursor Position} C : {ANSI foreground Green}
4 : {ANSI Restore Cursor Position} D : {ANSI foreground Brown}
5 : {ANSI ID String} E : {ANSI foreground Blue}
6 : {ANSI blink attribute} F : {ANSI foreground Magenta}
7 : {Clear all ANSI attributes} G : {ANSI foreground Cyan}
H : {ANSI foreground LightGray}
a : {ANSI background black} I : {ANSI foreground DarkGray}
b : {ANSI background red} J : {ANSI foreground LightRed}
c : {ANSI background green} K : {ANSI foreground LightGreen}
d : {ANSI background brown} L : {ANSI foreground Yellow}
e : {ANSI Background Blue} M : {ANSI foreground LightBlue}
f : {ANSI background Magenta} N : {ANSI foreground LightMagenta}
g : {ANSI background Cyan} O : {ANSI foreground LightCyan}
h : {ANSI background Gray} P : {ANSI foreground White}
! : "Press Any Key to Continue"
? : User's Name
$ : BBS Name
Color commands can be stacked, but remember to have the "~" symbol before ALL
color commands. (EG ~h~B~6 will change the color to Blinking Red on Grey.)
Table B: Definitions
───────────────────────────────────────────────────────────────────────────────
Throughout this file, you will be confronted by some terms that have nothing
to do with VGA Planets, and may be a bit confusing. Here is a list of some
of the terms I use:
"Game Directory" : The DOS directory containing GAME.REC, and all the files
for the game, created by the Start New Game procedure.
"Planets Directory" : The DOS directory containing MASTER2.EXE, HCONFIG.EXE,
HOST.EXE, and any other PLANETS programs & files needed
by this door. *MUST BE SEPARATE FROM DOOR DIRECTORY*
"Door Directory" : The DOS directory containing VP-DOOR.EXE, VP-MAINT.EXE and
all the other files contained in the Distribution Archive
that this door came in. (Other than the Maps)
"Game Host" or "Host" : The person who sets up and keeps track of game
Table C: Command Line Options
───────────────────────────────────────────────────────────────────────────────
VP-DOOR.EXE can be run with the following options, in any order:
-N{nodenumber} : Specify a nodenumber (0-99)
(If you use 2-9, the door will look for DORINFO2.DEF
to DORINFO9.DEF in current directory)
-RA : Forces door to use DORINFO1.DEF regardless of -N setting
-L{baudrate} : Lock baudrate
-D{path2dropfile} : Search for "Drop File" in {path2dropfile} directory
-DEBUG : Log everything to DEBUG.LOG (for finding bugs)
-R : Force the door to look for & display .VPR Rip files
-STARS! : Puts door into Stars! Menu (see section 15.0)
-C{filename} : Use {filename} instead of VP-DOOR.CFG
-G{filename} : Use {filename} instead of GAMES for list of games
VP-MAINT.EXE can be run with the following options, *1* at a time *ONLY*:
-B : Create "RUNGAMES.BAT" for today. (Also Clears
"Downloaded" flags.)
-T : Creates/Updates "Turns In Yet" bulletin. Runs
automatically in "RUNGAMES.BAT".
-S : Creates TIY.ASC, TIY.ANS, SCORE.ASC & SCORE.ANS. Runs
automatically in "RUNGAMES.BAT"
-E{gamename} : Create/Edit GAME.REC for "gamename"
-M{user_name} : Create Game Packets for "User name" (use _ for spaces)
-L : Compiles VP-DOOR.LNG into VP-DOOR.LX & VP-DOOR.LD
-FORCE : Forces game with "?"s to run regardless if all .TRNs
are in or not...
-DEBUG : Log everything to DEBUG.LOG (for finding bugs)
-C{filename} : Use {filename} instead of VP-DOOR.CFG
-G{filename} : Use {filename} instead of GAMES for list of games
-W : Create bulletin "WHOIS.ASC" in each game directory
of who is playing
╔═════════════════════════════════════════════════════════════════════════════╗
║ Please note: -C, -G and -DEBUG must be the LAST parameter on the line, ║
║ but can be combined with other options... ║
║ -FORCE is only valid when used with the -B switch. ║
╚═════════════════════════════════════════════════════════════════════════════╝
VP-MAIL.EXE is called in the following manner (exactly as shown):
VP-MAIL file_to_send_or_request from_node to_node msgareaid [-C]
Where node is in the format X:YYY/ZZZ.P (if X is not given, 1 is
default; if P is left off, 0 is assumed). See VP-DOOR.CFG for
a description of MSGAreaID. -C is optional and sets the CRASH bit on
the message.
For example:
VP-MAIL MYRSTS.ZIP 1:340/88.0 119/99 FC:\FD\MAIL\
will put a file request message in a *.MSG base at c:\fd\mail\
to 1:119/99.0, from 1:340/88.0, for the file MYRSTS.ZIP...
VP-MAIL C:\PLANETS\MYTURNS.ZIP 340/88 119/99 FC:\FD\MAIL\ -C
will send c:\planets\myturns.zip (if it exists) to 1:119/99.0,
with the CRASH bit set on the message.
Basically, if the file exists, it will be a file attach. If it doesn't,
it will be a file request message.
STUPDFIX.EXE is run as following:
STUPDFIX [-OUT gamename]
StupidFix should be run in your inbound mail event, to scan for mail to the
program. If you use the -OUT switch, StupidFix will send out all the
packets for all the Internet players in "gamename".
Table D: Registration
───────────────────────────────────────────────────────────────────────────────
I have spent over a year working on this door. If you use it, I would like
some kind of payment for my work.
If you use this door for more than 30 days, please register it.
If you register, you will recieve the following extras:
- Use of StupidFix (the Internet <-> Stupid interface)
- My everlasting gratitude
- Full technical support, including new features by request
- Notice of new major releases, when they come out
- A stop to the annoying "register me" messages...
- The return of some features that may tend to "disappear"
"Other Door Offer":
It has come to my attention that I have "competition" in creating the
Ultimate Planets Interface Door...
It has also been suggested that the $20 that I want for my door might be
too much for those people who are already satisfied with their registered
"other" planets door...
For these people, I wish to make an offer:
I will let you register my door for $10 (1/2 off the regular price), on
recieving proof of registering any similar Planets door with a registration
cost of $10 or more.
If you wish to make use of this deal, I must have an account on your system,
just long enough to see the registration of your door.
Create an account for me, under the name "Allen Walker", and let me know what
the password is. I will call to verify the registration.
Adopting the Door:
If a Sysop were to register all the software they use, including doors,
nobody would be able to afford to run a BBS. So I suggest an alternative:
Adoption.
The idea of adopting a door is that someone, usually a user of the BBS,
can pay for registering a door as a donation to the BBS... Simply contact
the Sysop of the BBS you want to adopt this door in. He can then give you
a copy of REG-FORM.TXT, which is the registration form for this door. Fill
it out and send it to me with payment for the door. Your name will appear
in the "Adopted By" slot...
Adoption of a door is also eligible for the "Other Door" discount.
You can send a check or MO, for $20 US (or $10), to (NOTE NEW ADDRESS!):
Allen Walker
P.O. Box 5874
Victoria, BC
Canada
V8R 6S8
Also, due to overwelming response from my fellow Canadians, Canadian
users may now pay $20 Canadian, instead of US.
┌┬┬┬┬────────────────────────────────────────────────────────────┬┬┬┬┐
│││││ Visa Visa Visa Visa Visa Visa │││││
│││││ Visa Visa Visa Visa Visa Visa Visa │││││
│││││ Visa Visa Visa Visa Visa Visa │││││
│││││ Visa Visa Visa Visa Visa Visa Visa │││││
│││││ Visa Visa Visa Visa Visa Visa │││││
│││││ Visa Visa Visa Visa Visa Visa Visa │││││
│││││ Visa Visa Visa Visa Visa Visa │││││
└┴┴┴┴────────────────────────────────────────────────────────────┴┴┴┴┘
* * * * * * * * Registration is now available by Visa! * * * * * * * * *
In order to register by Visa, I must have the following information:
Your VISA number
Expiration Date
Your name (EXACTLY as it appears on the card)
Note: Since the Visa will be in Canadian dollars, I must alter the charges
for the door as follows (this only applies to Visa payment, and is to
cover U.S. exchange rate):
Canadian Full Registration: $20.00
1/2 Price Registration: $10.00
U.S. Full Registration: $26.00
1/2 Price Registration: $13.00
Postage & Handling: $ 5.00
(for mail orders only, both countries)
VISA orders will be processed within 24 hours
Table E : Reporting Bugs
───────────────────────────────────────────────────────────────────────────────
In order to fix a bug, I have to be able to reproduce it. If I can
reproduce it, I can squash it in minutes... Use the -DEBUG command line
option to create a DEBUG.LOG...
I will need the following:
1. A copy of your VP-DOOR.CFG
2. A copy of your VP-DOOR.LOG
3. A copy of your DEBUG.LOG
4. If the error # and address isn't in the log, I will need that too.
5. A copy of your drop file (DOOR.SYS, DORINFOx.DEF, etc)
6. If it's a logic bug (something weird, but the program doesn't
crash), I need to know what the last thing you saw displayed,
and the circumstances. A screen capture would be ideal.
Bugs can be reported to the address above, or to:
Crazy Train ][ BBS (604)383-2201
1:340/88 - Fidonet
57:604/125 - VGAPNet
Allen_Walker@crazytrain.spydernet.com
http://vvv.com/~weirdal
Table F : Extra Utilities for S.T.U.P.I.D.
───────────────────────────────────────────────────────────────────────────────
Program (Current FREQ Filename) : Description
MASTER2.EXE (MASTER2.ARJ) : Allows you to create universes without having to
use Graphics. Essential for STUPID to have remote game creation
RCONFIG.EXE (EXP303.ARJ) : The Expansion Modules, written by Tim Wisseman.
"Missions" under Planets.
KILLRACE.EXE (KILLRACE.ARJ) : Removes a race's SHIPS, PLANETS and STARBASES.
Effectively deletes the player from the game.
BLANK.EXE (BLANK.EXE) : Removes scores from .RST files to make game more
interesting.
CRACK.EXE (CRACK02.ARJ) : Allows host of game to view passwords of players
(in game, that is...)
SPLITVH.EXE (VCRSHOW.ARJ) : Makes separate files of all the VCR ship battles
so host can "watch the fun"
CPLAYER.EXE (CP302.ARJ) : The Computer Player. Loved by some, hated by others
but fully supported by this door (including "difficulty level")
WORM.EXE (WRM034.ARJ) : Wormhole utility. Creates "wormholes" from one end of
the galaxy to the other, set up by the Host of the game.
VPMC.EXE (VPM2*.ARJ) : VGA Planets Movie Recorder. Records the whole game so
people can sit back and laugh at the antics of all the races at the end.
RAGNAROK.EXE (RAGNA200.ARJ) : Moves all capital ships to the center of the map
to have a huge "battle royal" to see who wins. Usually used at the
end of a big game, or when the ship queue gets clogged.
All of these utilities are available for File Request 24 hours a day from
Train ][, downloadable from my BBS, and on my Web Page at:
http://vvv.com/~weirdal
───────────────────────────────────────────────────────────────────────────────
VP-Door (c) 1995 by Weird Al Walker
Documentation by Weird Al Walker, with help from Dragonlord Valheru
Special thanks to all the Planets players on my BBS, who were very patient
while I worked on this door:
William Barath - Thanks for the Fixmaps code!
Jason George - Thanks for getting me started on the docs!
Rob Gillingham & The Trolls - for all the help with V1.x
Sean Ross
Brian Pinkerton
Graeme Newall
Allan Coats - My first Long Distance regular player!
Adam Noyce
Gordon Webster
Noel Mercer
Allen Cary - My first STUPIDFIX user!
And of course, Gerald Albion... the other half of Whirlwind... for
all the Comm routines...
───────────────────────────────────────────────────────────────────────────────
▀█▄ ▀█▄ ▀█▄ ▀█▄ ▀█▄ ▀███▀▀█▄ ▀█▄ ▀█▄ ▀█▄ ▀█▄ ▀██▄ ▀█▄ ▀██▀▀█▄
██ ▄██ ▄██ ▐██▄▄▐██ ▐██ ▐██ ▄██ ▐██ ██ ▄██ ▄██ ▐██ ▐████▄▐██ ▐██ ▐██
████████▀ ██▌▀▀██▌ ██▌ ██▀███▀ ██▌ ████████▀ ██▌ ██▌ ▀███▌ ██▌ ██
▄██▀ ██▀ ▐██ ▐██ ▐██ ▐█▌ ▀██▄ ▐██▄▄▄▄ ▄██▀ ██▀ ▐██ ▐██ ▐██ ▐██▄▄▄██▀
This is another fine software product of Whirlwind Software, Victoria, B.C.
───────────────────────────────────────────────────────────────────────────────
MZ└gÜiSô8∞/ÿ: ⌡"