home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Media Share 9
/
MEDIASHARE_09.ISO
/
bbsdoor
/
ffight32.zip
/
FOODFITE.DOC
< prev
next >
Wrap
Text File
|
1993-02-04
|
51KB
|
1,332 lines
╥─╖ ╓─╖ ╓─╖ ╥─┐ ╥─╖ ╥ ╓─╖ ╖ ╖ ╓╥╖
╟─ ║ ║ ║ ║ ║ │ ╟─ ║ ║─╥ ╟─╢ ║
╙ ╙─╜ ╙─╜ ╨─┘ ╙ ╨ ╙─╜ ╙ ╙ ╙
DOOR
version 3.2
by Michael Wilson
The Village
408-229-0706
USR Courier HST Dual Standard
2400/9600/16.8K
24 hours / 7 days
CONTENTS
════════
I. Introduction
a. Overview
b. Background
c. Tools
d. Restrictions in the unregistered version
e. Benefits of registering
f. Support
II. Setup
a. Supported BBS Systems
b. Customization of the Game
c. Configuration File
d. ITEM.DAT
e. DEFENSE.DAT
f. Sample door batch file
g. Local Mode
h. Optional Files
i. Created Bulletins
j. The Prize Option
k. Resetting the Game
l. Better DAT Files
m. Multi-Node Support
n. ANSI Screens
III. Use
a. FFUSER.DOC
b. Sysop Menu
c. On-Line Sysop Keys
d. The Prize option
e. Resetting the game
IV. FFMAINT - Nightly Maintenance
V. FFBULL - Bulletin Generator
VI. Compufax Software
VII. Registration Information and Form
VIII.Bug report form
IX. Revision History
INTRODUCTION
════════════
Overview
────────
FOOD FIGHT is a challenging game that your callers are sure to love. It
has few options, so is simple to play and easy to remember. It is,
however, rather addicting, so it should become a very popular door. The
object is to find money, buy food, and throw it at other players. When
these other players log on, they will do the same, and throw food at you.
* Fully configurable - most features can be disabled or
enabled as desired for your own "custom" game
* Support for all known and unknown comm ports
* Fossil driver support
* Complete monitoring of system time, time left, carrier and DTE
* Support for color and mono screens
* Nightly event to delete "aged" players
* Bulletins that supports ANSI and WC3 color codes listing the
top ten players in a sorted, single line format
Background
──────────
The idea for this door was originally David Clifford's at the Haunted
Castle BBS (408) 226-1052. It was inspired by the PIE SPLAT door, and
since no updates for that door have been seen in years, it was decided to
write a totally new door with the same concept, yet more colors, options
and fun.
Tools
─────
Language and Compiler: Borland C 3.1
Editor: Multi-Edit 6.10aP
Libraries: CKit Door Library 2.54
Version Control: Sage's PVCS
Beta Test: The Haunted Castle BBS (Spitfire)
408-226-1052
The Village (Wildcat)
408-229-0706
Tea: Earl Grey, Hot (Bigelow)
Restrictions in the unregistered version
────────────────────────────────────────
The game is fully functional in the unregistered state, however, there are
delays at the beginning and end to remind you to register, and a few
reminders throughout the program. They should not be too much of a bother,
and should give you ample time to test the door before registering.
You may also not change lines 8, 9, 15, 16 and 18 of the configuration
file.
Benefits of registering
───────────────────────
1. All delays and reminders are removed.
2. A 1 year membership in The Village BBS.
3. All future updates FREE, downloaded from The Village BBS.
4. Ability to change lines 8, 9, 15, 16 and 18 in the config file.
5. Can list sponsors for the game
Support
───────
Snail-Mail: Compufax Consulting Services
7145 Aptos Beach Court
San Jose, CA 95139
BBS: The Village
408-229-0706 or 408-229-0709 (2 lines with roll-over)
USR Courier HST Dual Standard 16.8k
Leave comment for the SYSOP in the Main Conference [000]
Voice Mail: 408-496-9045 (24 hours/day)
CompuServe: 76207,1673
Please include all available information including copies of your
ITEM.DAT, DEFENSE.DAT, FOODFITE.CFG, etc.
The latest version will always be available on the following boards:
The Village:
408-229-0706/408-229-0709
USR Courier HST Dual Standard 16.8
Michael Wilson, sysop
The Haunted Castle BBS:
408-226-1052
USR Courier HST Dual Standard 14.4
David Clifford, sysop
The Party Wherehouse:
510-256-8979 or 510-256-9809
Practical Peripherals 14.4k
Sean Andrade, sysop
CompuServe: IBM BBS Forum (GO IBMBBS), Doors Library
SETUP
═════
Supported BBS Systems
─────────────────────
FOODFITE will support any BBS that creates a DOOR.SYS file when
chaining to a door. Also, Wildcat 2.x (CALLINFO.BBS), DORINFOx.DEF
and PC Board - 12.0 through 14.5 (PCBOARD.SYS) are supported.
The following BBS systems have been tested, and shown to work:
PCBoard 12.0 through 14.5
Wildcat! (all versions)
GAP BBS
Spitfire 3.0
RBBS-PC
QuickBBS
Remote Access
MikeBBS (MBBS) v9.9 and above
If your BBS is not on the list, and works, let me know and I'll add it to
the list.
Customization of the Game
─────────────────────────
The following Food Fight Features are fully customizable by you so that
you can make your own distinct game:
Food Items: Names, Damage, Cost, Hit Chance (ITEM.DAT)
Protection Items: Names, Cost, Points, Percent (DEFENSE.DAT)
Bulletin Locations (FOODFITE.CFG)
Winning Score (FOODFITE.CFG)
Losing Score (FOODFITE.CFG)
Prize: Enable or disable, and what the prize is (FOODFITE.CFG)
Starting Money: Amount or disable (FOODFITE.CFG)
Do players get to look for money on their first day? (FOODFITE.CFG)
Lottery: Tickets per Login, or disable (FOODFITE.CFG)
Stealing: Enable or Disable (FOODFITE.CFG)
I have tried to make Food Fight a "plug and play" type door, but also give
you the chance to change everything if you want. So, either play Food
Fight with the default values, or have some fun, and make some changes.
Remember that if you make changes that you think are better than the
defaults, let me know...I might agree.
CONFIGURATION FILE
══════════════════
FOODFITE knows what type of system you are using, where to output
bulletins, Your system name, etc through a configuration file. The
configuration file can have any legal DOS filename. It consists of 15
lines as follows:
line 1: c:\door\door.sys
line 2: The Village
line 3: Michael Wilson
line 4: 0000000000
line 5: ANSI
line 6: c:\door\bull\bull99.scr
line 7: c:\door\bull\bull99.bbs
*line 8: 5000
*line 9: -5000
line 10: Prize line 1
line 11: Prize line 2
line 12: Prize line 3
line 13: Prize line 4
line 14: Prize line 5
*line 15: 20
*line 16: YES
line 17: NONE
*line 18: 5
line 19: YES
line 20: -2
*line 21: YES
*line 22: 5
*These items cannot be changed in the UNREGISTERED version.
NOTE: The line numbers are only listed for clarity. Your configuration
file will have no line numbers listed
LINE 1: This is the complete drive letter, path and filename of your
BBS door system file. This can be either DOOR.SYS,
CALLINFO.BBS or PCBOARD.SYS.
LINE 2: This is the name of your BBS. It must EXACTLY match the name
of the BBS you put on the registration form. Upper and lower
case make a difference here. This name will be displayed
EXACTLY as entered here when the door is registered.
LINE 3: This is the name of the sysop. This name must EXACTLY match
the name entered on the registration form. Upper and lower
case make a difference. This name will be displayed as the
sysop when the door is registered.
LINE 4: The registration number obtained when you register.
LINE 5: This line can have 1 of two values. Put WILDCAT3 here if you
are using Wildcat! version 3.x and want your bulletins to use
the Wildcat! color codes. Put ANSI here if you want standard
ansi color codes used in your bulletin.
LINE 6: This is the complete drive letter, path and filename of your
COLOR bulletin. There is no error checking to make sure that
the path, filename is legal, so make sure you enter the
information correctly.
LINE 7: This is the complete drive letter, path and filename of your
MONO bulletin. This bulletin will not be created if line 5
contains the keyword WILDCAT3. However, this line, or a blank
line, must still be placed here. There is no error checking to
make sure that the path, filename is legal, so make sure you
enter the information correctly.
LINE 8: This is the score that is any player gets a score higher than
this, they have won the game. We suggest 750. Initially, most
players will have a day or 2 of negative scores, but once they
get the hang of it, their score should roller-coaster. If you
are using the prize option, and the prize is substantial in
value, then increase this number as desired. The maximum
allowed number is 32000.
LINE 9: This is the score that if a player has a score below this, he is
automatically deleted and started over. This number should be a
negative number. We suggest -5000. There is usually no return
from such a low score. The lowest allowed number is -32000.
LINE 10: These lines describe the prize you are offering. You may enter
LINE 11: up to 5 lines of prize description, but each line should not
LINE 12: exceed 50 characters. If you wish to disable the prize option,
LINE 13: enter the word NONE on line 10 and leave lines 11-14 blank.
LINE 14: Even if your prize description is less than 5 lines, ALL 5 LINES
MUST BE PRESENT. Simply leave them blank if not needed.
LINE 15: This is the dollar amount that each player gets when they first
start the game. This number must be greater than 0 and less than
32000. This number has no dollar sign, no decimal point and no
commas.
LINE 16: Enter here whether you will allow new players to Look for
Money on their first day. This line is either YES or NO. YES
means that you will allow them to look for money on their first
day, NO means you will not.
LINE 17: This line of for non-standard comm port parameters. If you do
not use a standard comm port setup, then the syntax is
PORT:AAAA:X where AAAA is the base address and X is the IRQ.
FOODFITE will also support the use of FOSSIL drivers. The
syntax for a FOSSIL driver is: PORT:F:P. The 'F' tells FOODFITE
to use a Fossil driver for it's communications. The 'P'
following it tells it which port to use for the Fossil.
Example - PORT:F:1, tells FOODFITE to use a fossil driver for
port 1. If you use a standard port setup, place the word NONE
here.
Digiboard Intelligent Async boards are supported thru the
Universal DOS driver for Digiboard. The syntax is the same as
the Fossil driver except you replace the F with D and give the
channel number to use. Example - PORT:D:6 tells FOODFITE that it
is connected to a Digiboard and to use channel 6 on the
Digiboard.
LINE 18: This is the number of lottery tickets a player may buy PER DAY.
This number defaults to 5, and cannot be changed in the
unregistered version. If you wish to totally disable the lottery
feature, then place a 0 (zero) in this space. The upper limit is
32000, which is effectively unlimited.
LINE 19: This option is to enable or disable the Rob Another Player
on the main menu. 2 options are available: YES or NO.
YES will enable Stealing, and NO will disable it. Anything
other than YES or NO will default to YES.
LINE 20: This option is the time allowed in the door. It works this way:
If the number is ZERO, then no modification is made. The time
left on the board is the time allowed inthe door.
If the number is greater than ZERO, and less than the time left
on the board, the caller is given the new time.
If the number is greater than ZERO, and more than the time left
on the board, the time allowed in the door is the time left on
the board.
If the number is LESS than ZERO, then the user will be kicked out
of the door with this much time left. This means -5 will
cause the caller to be returned to the board with 5 minutes
left.
LINE 21: Do you want to offer the ATM bank to your callers. YES will
enable the BANK option, NO will disable it.
LINE 22: When players kill themselves, how many days must pass before they
can play again? 5 is the default. You can put up to 365 days
here. If you place a 0 (zero) here, this will disable the Kill
Yourself option.
ITEM.DAT
════════
The names of the foods, their cost, damage when thrown and percent
chance of hitting are all contained in the text file ITEM.DAT. Each
line contains 1 food. There must be exactly 10 foods in the file. The
format for each line is:
name,damage,cost,hit chance
NOTE: No spaces around any of the commas.
<name> can be any food name (or any other word), not more than 20
characters in length. The name can contain spaces.
<damage> is a number that is the points a thrower gains and the opponent
loses when a hit occurs. Remember your "winning score" when you enter
this number. Each game should take several weeks to a couple months.
<cost> is a number that is the cost, in dollars, of a single piece of
this food. Since the minimum is $20.00 per day, try not to make the
food too expensive.
<hit chance> is an integer that represents the percentage chance this
food has of hitting (e.g.: 95 would mean 95% chance of hitting). The
higher the number, the greater chance of hitting. 99 is the highest you
can go.
The ITEM.DAT file that came with this program has been extensively
tested, and should be fine for most boards. Be careful, however, when
altering this file to obey the above rules, and test it prior to letting
your callers use it.
DEFENSE.DAT
═══════════
The types of protections offered in your game are listed in DEFENSE.DAT.
This is a text file that can be edited with any pure ASCII editor. The
format is one defense per line in the following format:
type,percent,points,cost
The meaning of each is described below:
TYPE: This is the type of protection
PERCENT: This is the percentage of damage that the protection will
absorb, and deflect away from you. For example, if someone
throws a pinapple at you, and hits. Normally, this would do
100 points of damage. But, if you had a Garbage Can Lib, the
pinapple would only do 50 points of damage (50% of 100). The
Garbage can lib would absorb 50 points (50% of 100).
POINTS: The points is the amount of damage the protection can absorb
before becoming useless. In the above example, the garbage
can can absorb 150 points before becoming useless. After 3
hits with a pinapple, absorbing 50 points per hit, the
Garbage Can Lid would disappear, and you would be without
protection.
You can have from 0 to 10 protection items. If you do not wish to enable
protection in your game, delete DEFENSE.DAT.
Sample Door Batch File
──────────────────────
The configuration filename is placed on the command line of
FOODFITE.EXE. Here is a sample batch file to give you an idea of how
the door is called:
C:
CD\FOODFITE
FOODFITE FOODFITE.CFG
FFBULL FOODFITE.CFG
CD\
If the configuration file is missing, or incorrectly made, an error
will be displayed.
Local Mode
──────────
The door can be tested in Local Mode by having the config file point to
a BBS door file that has a comm port of zero (COM0:). Included are the
following files:
LOCAL.BAT
LOCAL.CFG
DOOR.SYS
These will assist you in testing the door in local mode. If you want your
name displayed instead of "SYSOP", edit DOOR.SYS and replace the word
SYSOP with your name.
Simply typing LOCAL with the above files in the current directory,
therefore, will put the door in local mode.
OPTIONAL FILES
══════════════
Display Files:
NOTE: All display files support both ANSI color and Monochrome files.
You should create both a .SCR and .BBS file for each file name
(i.e.: SBULL.SCR and SBULL.BBS). The correct file will
automatically be chosen by FoodFite based on the user's
"graphics" setting.
All files must be in the same directory as FOODFITE.EXE
SBULL: This file is the Sysop's bulletin. Callers may view it from the
main menu. This file may be of any length, and may give any
information you want. Every 23 lines, the display will pause
and a "more?" prompt will be displayed. If these files do not
exist, FoodFite will tell the caller that the bulletin is not
currently available.
BADUSER: This file is displayed to any caller whose name appears in
the BADNAMES.LST file. The default is to tell the caller
that the door is temporarily closed. However, if you wish
to give a more complete explanation, you may create this
file. This file can be of any length, and every 23 lines
the display will pause and a "more?" prompt will be
displayed.
Data Files:
PLAYER.DAT: The complete player list and player statistics. (binary)
BANK.DAT: All player's bank accounts and information. (binary)
FOODFITE.DAT: Game statistics, displayed with the [D]oor Stats on the
sysop menu. (binary)
DEAD.DAT: This file contains the names and dates players kill
themselves. It is used to determin who is dead, and when
they can play again. Delete it to remove all dead
players. (text)
IMESSAGE.DAT: This contains the individual message sent between
players. (binary)
GMESSAGE.DAT: This contains the global message left by the last player
in food fight. It will be displayed to the next person
to play. (binary)
BATTLE.DAT: This contains the battle information that is
displayed to each player during (not fast) login.
(binary)
BADNAMES.LST: This file is a text file that contains 1 name per line.
If the caller's name matches a name in this list, they
will not be allowed to enter the door. This is a good
tool for people who continue to use nasty or offensive
aliases or for people who you don't want playing games
on your board. (text)
SPONSOR.DAT: This file contains the names of the callers who helped
sponsor food fight. The file has 1 name per line, and up
to 10 names. These names will be displayed to the
players at the end of the game, IN THE REGISTERED VERSION
ONLY! (text)
LASTWIN.DAT: This file is automatically created when someone wins. It
will be used to tell callers who the last winner was. If
you do not want this information displayed, then delete
this file as part of resetting the door after a win.
(text)
CREATED BULLETINS
═════════════════
Each time you run FFBULL, the bulletins specified in lines 6 and 7 of the
configuration file are created. They have a header and a list of the top
10 players, with the highest score on top. IF the game has been won, then
the top player has the word WINNER printed on both sides of his name.
THE PRIZE OPTION
════════════════
The sysop has the option of making FOODFITE a tournament, and offering a
prize to the winner. Alter lines 10 through 14 in the config file to
reflect your desired prize. Whatever you enter on these lines will be
displayed to every caller when they enter the door. It will also be
displayed to the winner when he wins to remind him of what he has won.
If you wish to completely disable the prize option, put the word NONE as
the only word on line 10 in the config file.
RESETTING THE GAME
══════════════════
When someone wins the game, the game will not allow any more players
into the game. Anyone entering the game after a win will be presented
with a notice of the winner, and the time and date of winning. They
will also be asked to notify the sysop that the game is over and needs
to be reset.
When the sysop enters a game that has been won, he will be presented with
the option of resetting the game, and starting again as the first new
player. The sysop may also simply delete PLAYER.DAT, BANK.DAT and
FOODFITE.DAT. The next time the door is entered, these files will be
created, and a new game will begin.
The file FOODFITE.WIN will be created in the foodfite directory when
someone wins. It will contain the name of the winner, and the date the
game was won. You can put an "if exists foodfite.win" statement in your
door batch file to watch for this file, and notify you of the need to
reset the game.
BETTER DAT FILES
════════════════
There are 2 Data files for Food Fight. ITEM.DAT contains the food
items for sale. DEFENSE.DAT contains the protections for sale.
There are sample data files contained in this archive. These have been
developed by our beta testers, and work rather well. We are,
however, very interested in the data files that you create.
If you have developed your own data files, please upload them to the
Village BBS (408-229-0706) with a comment to the sysop. We'll look
at them, and try them out. If they work well with our users on the
West Coast, we'll include them in the next release of FOOD FIGHT, and
give full credit to your and your BBS.
MULTI-NODE SUPPORT
══════════════════
Food Fight does not support true on-line interactive play between two
callers, but it does support multi-line. What this means is that 2
callers may be playing the game at the same time, and all data files,
display files and scores will be updated on-the-fly so that each player
will see the changes caused by the other player as it happens. This may
seem odd, however, since there is currently no way for one player to be
aware of another player on the other node(s).
The main setup difference from single to multi-node is the configuration
file. Since the first line points to your door information file, you must
have a different config file for each door information file. All the
other lines should remain the same (unless you want to enable the lottery
on one node and not the other, but why?)
Do whatever you must do to start your multiple nodes, and have a
different batch file for each Food Fite node.
Food Fight will sense, and use the record locking options bult into SHARE
from MS DOS 3.30 or later. If you are using a multi-line system, you
should load share anyway, but if you have not, it will save you hours of
trouble if you load it before running Food Fight. This is because it is
possible for 2 players to be writing to the PLAYER.DAT, or other data file
at the same time. With share loaded, one node will wait until the otehr
is done. If share is not loaded, tehy will both write, and corrupt your
data files.
If retries become necessary, the word "Retry" with the retry number will
be seen in the upper right hand corner of the screen. Food Fight will try
60 retries before existing with a share violation. Food Fight will NOT
hang your machine with a Retry, Abort or Fail message if this occurs. The
caller will be asked to re-enter the game, which usually clears up any
SHARE retry loop.
The current node is displayed as part of the sign-on screen.
ANSI Screens
────────────
With version 2.2, I have started adding in Full Screen ANSI Pictures. As
of this release, only 1 has been completed. It is COP.ANS and will appear
if a player gets caught trying to steal things from another player. The
caller must also have ANSI color enabled.
If you do not want this ANSI picture to be displayed, delete COP.ANS. If
Food Fight cannot find that picture, then it will display the old style
screen.
If you are an ANSI artists, and have some ideas on improving Food Fight
with Full Screen ANSI Pictures, then call The Village and leave me a
comment.
USE
═══
see FFUSER.DOC
┌──────────────────────────────────────────────────────────────────────┐
│ NOTE: Make sure that you have FFUSER.DOC available for download by │
│ your callers. It contains complete playing instructions and menu │
│ commands. If your callers have this document, your game will be │
│ smoother with fewer questions ask of you about how to play the game. │
└──────────────────────────────────────────────────────────────────────┘
Sysop Menu
──────────
This option is only available to players with the name SYSOP, or whose
name matches that name entered in line 3 of the config file. There are
4 options on the sysop menu:
RESET THE GAME (Start over): This will delete all data files and
players, and start the game over.
DOOR STATS: This will display a series of stats concerning FOODFITE,
including, number of uses, last player, last played date and start
date. As part of the door stats is bank stats. Pressing B will
display the total accounts, top depositor and top borrower.
ZAP A PLAYER: This will permanently remove a player from the game. He
can still come back as a new player and start over. Enter his name in
the BADNAMES.LST file to prevent him from re-entering the game.
USER LIST: This option will allow you enter the partial ALIAS name of a
player. If a match is found, then a detailed display of this player
will occur. If you simply press enter for the player's name, then a
summary of every player in the game will be displayed. All printing
will be to device PRN.
BROADCAST A MESSAGE: You may enter up to 5 lines of message with this
option. This message will be shown to every user when they enter the
game. It will be shown only once per player.
END A BROADCAST MESSAGE: This will delete the broadcast message
created with the above option.
QUIT TO MAIN MENU: This will return you to the main menu
EXIT TO BBS: This will exit the door and return you to the BBS.
On-Line Sysop Commands
──────────────────────
While a caller is on-line, the local sysop has several options. They are
as follows:
Function key
------------
F5 Shell to DOS
F8 Return user to system
F9 Toggle display on/off
F10 Chat mode (use the ESCAPE key to exit)
* F3 Toggle printer on/off
* F4 Toggle pagebell on/off
* F7 Toggle caller alarm on/off
Alternate key
-------------
ALT-H Toggle between different status lines
* ALT-N Toggle sysop on next
* ALT-X Toggle exit to dos after call
and help lines
Alternately pressing the ALT-H key will bring up
the next status line screen. The 1st screen is a help screen,
the second screen shows your COM port status.
* The function keys marked with an "*" will only be of use to systems
using pcboard.sys. The rest are functional with any system.
FFMAINT
═══════
FFMaint is a separate program from FOODFITE.EXE. It should be
run at least once per week. Usage is simply this:
FFMAINT [#] | [LOG=#]
There are two different usage of FFMAINT. The first is to put a number
(#) on the command lines. With this option, FFMaint will open your
player.dat file, and delete any player that has not played in the number
of days you specify.
FFMaint displays the number of players kept and the number of players
deleted.
FFMaint must be run in the directory that contains PLAYER.DAT.
FFMaint will also trim the daily log. Buy putting the word LOG=# on the
command line, where # is the number of lines you want to keep, FFMaint
will trim your news log. For this option, FFMaint must be run from the
same directory as DAILY.LOG. The file DAILY.BAK is created which
contains the unaltered log. There can be no spaces on either side of
the equal sign.
FFmaint will tell you haw many lines it deleted, or if there was no
deletion needed.
It is a clean and small program that will never make any noise or hang.
It will, however, return an errorlevel of 1 if something went wrong.
FFBULL
══════
FFBULL is used to create your top ten players bulletins. It was split out
from the main FOODFIGHT program with version 2.5. This was done to make
Food Fight smaller and faster. Also, some sysops were asking for the
ability to only create a top ten bulletin once a night, in their night
maintenance.
Usage is simple. Invoke FFBULL with the name of your Food Fight config
file on the command line. For example, if your Food Fight config file is
called FOODFITE.CFG, then do this:
FFBULL FOODFITE.CFG
FFBULL will read the registration information, bulletin color type and
path/name of your color and mono bulletins, and will create them.
FOODFITE does not create any bulletins during normal operation. You must
run FFBULL to create the bulletins. If you want bulletins that are up to
the minute, then have your batch file be something like this:
@ECHO OFF
CD\DOORS\FOODFITE
FOODFITE FOODFITE.CFG
FFBULL FOODFITE.CFG
CD\WC
FFBULL will not include any players who's score is negative. Only players
with scores of ZERO or greater will be included in the bulletin.
COMPUFAX SOFTWARE
═════════════════
Compufax Software is a division of Compufax Consulting Services. We
specialize in getting the right computer and software for your needs. All
of our work is custom and created just for you.
We started writing door software with a program called BUY&SELL Door.
After reviewing dozens of For Sale Doors, we could not find one to meet
our needs, so we wrote one. That is what we do. We find a need, and
write a door to fill that. You won't find us writing 30 card game doors
that all look the same. Each door is individually designed to meet a
need. Currently, we have 7 BBS door/Utility Programs programs:
Food Fight
Buy & Sell
UNIPAGE
QDMENU
Dodge Ball
Thought of the Day
ShowMe!
We will not cripple our doors. We'll just put in a few seconds reminder
that this copy is unregistered. We will never write a door that expires.
We have over 60 doors on our board, and sometimes it is month before a
door is fully tested. We won't force you to download a demo key every few
weeks either. Everything you need for full operation of our doors is
included in the distribution zip. No runtime modules, no keys, nothing
extra, nothing more to download.
All of our doors have a simple to use Local mode. You can see the program
before you put it online.
Your registrations are forever. When we give you a registration number,
you will never need to buy anything ever again. Each new version will use
the same number, and you're registered for life.
You can receive free technical support even if you are not a registered
user. Because of my schedule, I cannot be available for voice support,
but I'll answer every message on my BBS and Compuserve. If you need to
talk to me voice, I'll be happy to make an appointment and call you.
We're tired of poorly programmed, boring BBS Doors. We are here to change
all that. We may not have 30 doors, but the few we have are the best!
MISCELLANEOUS NOTES
═══════════════════
I am doing everything possible to add all the features requested while
making Food Fight small enough to run on the most minimal BBS system.
Food Fight is fully tested on my BBS which is Wildcat 3.55m running under
Desqview. It is also fully tested on The Haunted Castle BBS which runs
Spitfire. We make no effort to "pre-release" software. Everything is
fully tested for many weeks before final release.
REGISTRATION
════════════
When you register FOODFITE, your registration number will be posted on
The Village BBS (408-229-0706), in a private message to you. You
should allow 1 week from the time you send your check before the
message is posted. Other options include sending you the number and
sending you the latest version of the program with the number.
NOTE: The latest version may not be later than the one you have, and no
version number verification will be performed..
FOOD FIGHT REGISTRATION FORM
════════════════════════════
Your BBS Number (so I can call and play):________________
Name: ___________________________________________________
(Your name here must match EXACTLY with the name entered
on line 3 of the config file. Upper and lower case make a
difference here. Print or type clearly.)
BBS Name: _______________________________________________
(Your BBS name here must match EXACTLY with the BBS name
entered on line 2 of the config file. Upper and lower case
make a difference here. Print or type clearly.)
The name you have used or wish to use to log into The Village BBS:
_________________________________________________________________
╔════════════════════════════════════════════════════════════╗
║ ║
║ If you do not have a login to my board, and wish me to set ║
║ one up for you, supply the following information: ║
║ ║
║ ║
║ Phone number (with area code): __________________________ ║
║ ║
║ Birthday: _______________________________________________ ║
║ ║
║ Password: _______________________________________________ ║
║ ║
╚════════════════════════════════════════════════════════════╝
If you wish me to send you the registration number of the latest
version of FOODFITE, fill out the following:
Address:____________________________________________________
____________________________________________________
____________________________________________________
Mail To: Compufax Consulting Services
7145 Aptos Beach Court
San Jose, CA 95139
Select which option you would like to register Food Fight:
Basic Registration.
Includes lifetime registration number posted
to The Village BBS in a private message to you....$20.00 _____
Mail Number.
Includes lifetime registration number mailed
to you at the above address.......................$22.50 _____
Mail Diskette.
Includes lifetime registration number mailed
to on a diskette, along with the latest version
of this software..................................$27.00 _____
Type of diskette: *5.25" High Density _____
5.25" Low Density _____
*3.5" High Density _____
3.5" Low Density _____
*If you choose a High Denisty diskette, you will get
sample of other compufax Software on the same disk
Total Enclosed: __________
Payment method:
[ ] Check made payable to Compufax Consulting Services.
[ ] VISA [ ] Master Card [ ] Discover [ ] Carte Blanche
[ ] JCB [ ] Diner's Club
For Credit Card Purchases:
Number:________________________________Ex Date:_________________
Name on card:___________________________________________________
Statement ______________________________________________________
Mailing
Address:______________________________________________________
______________________________________________________
Home Phone:_____________________ Work Phone:____________________
Signature:______________________________________________________
R E G I S T E R O N L I N E
═════════════════════════════
You can register this software On-Line on the Village BBS. From the main
menu, Choose [Q]uestionnaires, and choose questionnaire number 6. Have
your charge card ready.
We accept VISA, Master Card, Discover, Diner's Club, Carte Blanche and
JCB cards.
Due to the nature of your purchase, your registration number will be
available within 12 hours of you completing the questionnaire.
This is how you do it:
1. Log onto my board in the normal fashion
-If you have never called before, answer the new caller questions
2. Press Q from the main menu
3. Press 6 and Enter from the Questionaire menu
4. Answer the questions
5. That's it!
BUG REPORT
══════════
Please report any and all bugs to my. Include as much information as you
can. If I think I have fixed it, I will send you the new version
for free, for testing.
You may use the form below to report any bugs, or use your own form.
Please send the form to me, or upload it to my BBS.
Explain the bug:____________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
____________________________________________________________________
(use another sheet of paper if needed)
Your BBS number:____________________________________________________
Version of FoodFite:________________________________________________
DOS Date and time of FOODFITE.EXE:__________________________________
BBS Software and version:___________________________________________
Describe your machine:______________________________________________
____________________________________________________________________
Describe your multi-tasking, if any:________________________________
____________________________________________________________________
Is this multi-node? (how many)______________________________________
Please include copies of your ITEM.DAT, FOODFITE.CFG, FOODFITE.DAT,
PLAYER.DAT, IMESSAGE.DAT, GMESSAGE.DAT, DAILY.LOG and your door
information file (door.sys, pcboard.sys, callinfo.bbs, etc).
REVISION HISTORY
════════════════
June 17, 1992 Version 1.0
Initial Release
June 24, 1992 Version 1.1
1. Better date control on the DAILY.LOG file
2. Better display of the DAILY.LOG file
3. Option to Abort looking for money
4. Added "nothing happened today" to log days where
nothing happened
5. Changed Arena screen to allow only A-J food letters
June 29, 1992 Version 1.2
1. Added the USER LIST function to the sysop menu allowing
sysops to review a player, and find out the real name of any
player.
July 17, 1992 Version 2.0
1. Added the option to Buy Protection
2. Added sysop's option to Broadcast a Message
3. Fixed bug in the View Scores Option
4. Highlight foods and protection that the caller can afford
and use low intensity for the one's he cannot afford
5. Highlight the Sysop bulletin option if there is one,
use low intensity if there is not.
6. If the user is in graphics mode, and SBULL.SCR does not
exist, but SBULL.BBS does, display SBULL.BBS.
7. Rework of the time and date functions
8. Check to see if the player is below LOW_SCORE at login.
9. Fixed arena screen display in non-color mode
10. Added Message Line-Length Markers
11. Rework of sort routines
12. Added sort to Choose Foe screen.
13. Redesign of Choose Foe screen including addition of Relist
14. Various cleanups, debugs, rewrites and internal changes.
15. Added FAST Login option
16. Added Food Fight Lottery
July 29, 1992 Version 2.1
1. Fixed a few misspellings
2. Cleaned up the final screen a little bit
3. Added the ability for the sysop to enter a won game and
reset the door from within
4. Fixed a bug when there was only 1 player in the game
5. Warn users who have NO ANSI control that this door relies
heavily on them, and that things might look odd
6. Added line 18 to the config file, limiting lotto tickets
or disabling the lottery totally
7. Added the option for players to steal from each other
8. Limit players from carrying more than 500 items. This fixes a
number of bugs with integer manipulation and was the easiest
way out of the problem
REVISION HISTORY (continued)
════════════════
August 10, 1992 Version 2.2
1. Fixed a bug in the [R]ob another player where you just hit
enter and steal nothing (bug or feature?)
2. Fixed the [R]ob another player screen, centering and such
3. Improved decoding of the configuration file
4. Progressive lottery jackpot
5. Automatically exit the food store when you are out of money
6. Made [R]ob another player optional in the config file
7. Added ability to sell protection back to the store
8. First attempt at full screen ANSI pictures
September 22, 1992 Version 2.3
1. Removed a bug that allowed duplicate alias names
2. Added the Bank
3. Added EMS and EXT overlays
4. Better display of daily log and view scores
5. Fixed date alignments in sysop's user list
6. Added the number of players and bank stats to the sysop's
door stats
7. Added sponsor listing
8. Modified lottery so that the jackpot does not grow so fast
October 1, 1992 Version 2.4
1. Fixed bug with alias names longer than 30 characters
2. Modified how bank interest was calculated
3. Made lottery winnings more "realistic"
4. Added Block purchase of lottery tickets
5. Added tax of lottery winnings
6. Made individual and global message up to 5 lines
7. Added ability to throw all food at once
8. Added ability to throw all of 1 type of food
9. Added loan due date to ATM screen
10. Modified colors and order of options in the Arena
11. Increased to lottery ticket limit to 32,000
12. Check for carrier in all minor loops
13. General screen cleanup
October 13, 1992 Version 2.5
1. Fixed a bug that always displayed starting money as $20 no matter
what the sysop had it set to (only effected registered users)
2. Guido will not attach your bank account if you are past due on a
loan. This gives at least some chance of catching up.
3. Display last winner as part of the logon.
4. Fixed bug that did not accurately display time left in BBS while
in door. Some users were given 0 time left in the door.
5. If you go past the losing score, you cannot play until the next
day.
6. Fixed "endless loop" hang when using Sponsor.dat file
7. More compact usage of ANSI screens
8. Split FFBULL program out of main program
November 19, 1992 Version 3.0
1. Fixed bug that would mess up the screen if you chose a new
opponent in battle, and pressed 'Q'
2. Fixed bug with long food names, and hitting a Policeman
3. Guido has become a little softer when loans are due...Sometimes
4. No longer show "loser" scores when [V]iewing Scores
5. No longer show negative numbers on the top ten bulletin
6. Added option for users to kill themselves
7. Added Share support for Multi-node systems
8. Door exits with a low intensity white (07)
9. Increased information in Examine Configuration
December 21, 1992 Version 3.1
1. Fixed bug with single letter alias names
2. Fixed bug with long list of names in stealing
3. Fixed bug with similar alias names (rare)
4. Added support for Digiboard Intelligent Async boards
5. Added support for higher IRQs and comm ports greater than 8
February 4, 1992 Version 3.2
1. Fixed a bug in Robbing another player
2. Fixed some spelling errors