|
Trooper II Guide
The text following is extracted from the online
guide for Trooper II that was originally developed
to be released on the CD for sale as part of our
young enterprise project. Because of the work load
in the creation of this site, I decided to port
it pretty much intact from the originial HTML file:
this should not prove a problem, since the guide
is supplemented generously with screenshots and
is fairly well written and extensive, but some of
the text may be irrelevant, arachaic, or just bizarre-
on the other hand, I think you should be used to
that now. Nevertheless, the guide is indespensibe
to anyone who wants to play Trooper II as it was
meant to be; intensively, and is fairly amusing
simultaneously.
The guide is subdivided into 6 sections:
Basic
controls
Game objects
Weapons in the game
Monsters in the game
Using the level editor
Image catalogue
Each section contains information on each topic,
usually in tabulated form alongside screenshots
of the action or object described. The original
plan was also to include a section on tactics in
Trooper II, or indeed a walkthrough of the game
itself; but this seemed a little excessive, and
would detract from the central pleasure of deriving
your own unique way of tackling the physical manifestation
of my neuroses that is Trooper II. Nevertheless,
in certain sections (such as those describing the
monsters) I have integrated a good deal of solid
tactics for tackling such obstacles into more general
information, and I believe there are even some semi-bugs
that you can take advantage of detailed in these
descriptions. The image catalogue is designed to
be used as a visual reference for the appearance
of images to be placed independently in the game
through the level editor, and is displayed as catagorised
into the several functional groups in which the
images are normally employed. It's oftend best to
use the catalogue when first designing levels, so
you don't have to run the game every time you want
to see what a new image looks like. I hope you find
it useful, Jon
|