Contents of the BOXER.DOC file
Requiem for a Heavyweight
Author : Paul D. Dembowski
Version : 1.0
Date : 1/31/89
-- Introduction --
Requiem for a Heavyweight is a boxing simulation aimed at
those who enjoy the statistical aspects of sports. If
recreating bouts between boxers of different eras appeals
to you, then I think that you will enjoy this game.
-- Hardware Requirements --
Requiem for a Heavyweight was designed to run on any IBM-
compatible microcomputer, regardless of the display
adaptor installed. I hasten to add that this program has
only been tested on a Win Labs 286-class machine w/Compaq
VGA card and a Dell System 300 with a Hercules Graphics Card.
-- Ulterior Motives --
I'm not actively soliciting donations for this program.
However I may be interested in any employment opportunities
that may present themselves. My only prerequisite is that
the work involves the C and/or C++ languages. Please note
that I have over 2 years of work experience, mostly as a C/C++
programmer. If you are familar with Paradox, you may want to
take a look at my first shareware program entitled PXDOC10.
This utility for PAL programmers generates a script and
procedural cross-reference of PAL scripts, as well as other
valuable information such as listings of unused scripts,
unresolved references, etc.. If you are interested in
discussing a job opportunity with me, I can be reached at
(703) 671-0700 during work hours, (703) 876-4085 or
(703) 522-0562 at night.
-- The object of the game --
Requiem for a Heavyweight is meant to be a game for two
players - each player 'manages' one boxer. The object of
the game is to defeat your opponent through effective selection
of strategies at the start of each round. A larger objective
of the game is to guide your boxer(s) career(s). This
version of Requiem for a Heavyweight does not implement a
ranking system for the fighters. However, devising such a
system is my first priority for the next release. Until then
you will have to create your own rating system.
-- Playing the game --
The game begins with an introduction screen that demonstrates
how much more I need to learn about programming graphics.
Pressing any key takes you to main menu where you will be
presented with 5 selections:
DOCUMENTATION Allows you to view this documentation without
having to exit the program or consult a printout.
RATINGS Allows you to view how the boxers are rated - in five
categories: by number of wins, by number of losses, by number
of knockouts, by win-loss percentage, and by knockout percentage.
JUDGESIf a fight is currently in progress, choosing this
selection will show you how the 3 fight judges have scored
the fight as of the last completed round.
FIGHT!If no fight is in progress, this selection will prompt
you for the 2 boxers to appear in the next bout. Then you
will be asked to choose 1st round strategies for the 2 fighters.
If a fight is already in progress, you will be prompted for the
2 fighter's strategies only.
Once the strategies have been selected for both fighters, the
round begins. As the fight is being fought, information about
what is happening in the ring will be presented to you. In the
top-middle portion of the screen, the current round and current
round-time can be found. Just below this is the knockdown
window. Any knockdowns, to whom and when they occurred, will
be recorded here. On either side of the knockdown window is
each respective fighter's condition window. All information
pertaining to injuries and cuts will be found here. When a fighter
suffers a cut, a description of the cut is followed by a number.
The number denotes the severity of the cut. In between the
condition windows is a simple depiction of the ring. This window
shows you where the boxers are in the ring. Note that if a
fighter is against the ropes, his opponent has an advantage over
him while they are in that position. Below each fighter's
condition window is his punch window. In this window is a
breakdown of 5 types of punches, and the damage the fighter has
inflicted on his opponent using them. The left column of numbers
shows the damage inflicted during the present round. The right
column of numbers shows the damage inflicted during the entire
fight.These two columns are totaled at the bottom of the
window. In the middle of the screen lies the announcer window.
Here you will be informed of any interesting (and sometimes not
so interesting) events that occur such as warnings from the
referee, knockdowns, etc.. Below the announcer window is the
damage window.Each fighter's name appears, along with a bar that
represents not only the punishment inflicted by his opponent in
the form of punches, but how often he is doing things that
judges don't like such as clinching his opponent, etc..
Finally, at the bottom of the screen is the endurance window.
The amount of endurance remaining for each boxer is shown in
the form of a bar. When the bar disappears, the fighter begins
to lose effectiveness in several ways such as reduced punching
power, higher susceptibility to knockdown, etc.. While a round
is being simulated, there is currently only one way to exit
the program which is to press the key.
QUIT! Exits the program.
-- Strategies --
NORMALThe fighter employs no special strategy.
COVER UP If your fighter was in big trouble during the previous
round, and needs to clear his head, You may want to use this
FIGHT INSIDE Your fighter will try to get inside and punish
his opponent both to the body and head. This strategy can
score some big points.However, your fighter's endurance will
decline faster, and he will be more open to punishment from his
OUTSIDE OFFENSIVE Your fighter will try to stay away from his
opponents power while attempting to land some punches himself.
DEFENSIVE Useful if it's late in the fight and your boxer has
a comfortable lead.
GO FOR KNOCKOUT Your fighter will try his best to end the bout
with that one big blow.
-- Technical notes --
Requiem for a Heavyweight was written using the Zortech C++ and
Microsoft C compilers.I also used Vermont Creative Software's
Windows for Data. I have tested this program extensively,
however, I realize that the worst tester of a system is the
programmer who wrote it. Any comments, suggestions and/or
bug reports would be most appreciated.My phone numbers can
be found at the beginning of this documentation.