1 <?xml version="1.0" encoding="ISO-8859-1"?>
\r
2 <!DOCTYPE book PUBLIC
\r
3 "-//OASIS//DTD DocBook XML V4.1.2//EN"
\r
4 "docbook/docbookxx.dtd">
\r
8 <title>Super Star Trek</title>
\r
12 <firstname>David</firstname>
\r
13 <surname>Matuzsek</surname>
\r
16 <firstname>Paul</firstname>
\r
17 <surname>Reynolds</surname>
\r
20 <firstname>Tom</firstname>
\r
21 <surname>Almy</surname>
\r
24 <firstname>Stas</firstname>
\r
25 <surname>Sergeev</surname>
\r
28 <firstname>Eric</firstname>
\r
29 <othername>Steven</othername>
\r
30 <surname>Raymond</surname>
\r
35 <para>Permission is hereby granted for the copying, distribution,
\r
36 modification and use of this program and associated documentation
\r
37 for recreational purposes, provided that all references to the
\r
38 authors are retained. However, permission is not and will not be
\r
39 granted for the sale or promotional use of this program or program
\r
40 documentation, or for use in any situation in which profit may be
\r
41 considered an objective, since it is the desire of the authors to
\r
42 respect the copyrights of the originators of Star Trek.</para>
\r
48 <literallayout format='linespecific' class='monospaced'>
\r
49 SSSSS U U PPPPP EEEEE RRRRR
\r
51 SSSSS U U PPPPP EEEE RRRRR
\r
53 SSSSS UUUUU P EEEEE R R
\r
56 SSSSSSS TTTTTTTT A RRRRRRR
\r
57 SSSSSSSS TTTTTTTT AAA RRRRRRRR
\r
59 SSSSSSS TT AA AA RR RR
\r
60 SSSSSSS TT AA AA RRRRRRRR
\r
61 SS TT AAAAAAA RRRRRRR
\r
63 SSSSSSSS TT AA AA RR RR
\r
64 SSSSSSS TT AA AA RR RR
\r
68 TTTTTTTT RRRRRRR EEEEEEEEE KK KK
\r
69 TTTTTTTT RRRRRRRR EEEEEEEEE KK KK
\r
71 TT RR RR EEEEEE KKKKKK
\r
72 TT RRRRRRRR EEEEEE KKKKK
\r
75 TT RR RR EEEEEEEEE KK KK
\r
76 TT RR RR EEEEEEEEE KK KK
\r
79 Produced For Your Enjoyment
\r
87 With Modifications By
\r
101 <chapter><title>Introduction</title>
\r
102 <para>The Organian Peace Treaty has collapsed, and the Federation is at war
\r
103 with the Klingon Empire. Joining the Klingons against the Federation
\r
104 are the members of the <quote>Romulan Star Empire.</quote> As commander of the
\r
105 Starship U.S.S. Enterprise, your job is to wipe out the Klingon
\r
106 invasion fleet and make the galaxy safe for democracy.</para>
\r
108 <para>Your battleground is the entire galaxy, which for convenience is
\r
109 divided up into eight rows of eight quadrants each, like a
\r
110 checkerboard. Rows are numbered from top to bottom, and columns are
\r
111 numbered left to right, so quadrant 1 - 8 would be in the upper right
\r
112 hand corner of the galaxy.</para>
\r
114 <para>During battle you will be concerned only with those enemies that
\r
115 occupy the same quadrant as yourself. Quadrants are divided up into
\r
116 sectors: ten rows of ten sectors each. Sectors are numbered in the
\r
117 same way as quadrants, so the sector in the upper right corner is
\r
118 sector 1 - 10. You have a short-range scanner which allows you to
\r
119 look at the entire quadrant in a single display.</para>
\r
121 <para>Enemies recharge during your absence. If you leave a quadrant
\r
122 containing a weakened enemy, when you return to that quadrant he will
\r
123 be strong again. Also, each time you enter a quadrant, the positions
\r
124 of everthing in the quadrant (except your ship) are randomized, to
\r
125 save you the trouble of trying to remember where everything in the
\r
126 quadrant is. Notice that this refers only to the positions of things
\r
127 in the quadrant—the numbers of each kind of thing are not changed
\r
128 (except for black holes and the Super-commander, which move around
\r
129 the galaxy). If you kill something, it stays dead.</para>
\r
131 <para>The Romulans are not as serious a threat to the Federation as the
\r
132 Klingons. For one thing, there are not as many of them. For
\r
133 another, the Romulans are not as treacherous. However, Romulans are
\r
134 not to be trifled with, especially when you are in violation of the
\r
135 Romulan Neutral Zone.</para>
\r
137 <para>There are two kinds of Klingons: Ordinary Klingons, which are
\r
138 bad enough, and Klingon Commanders, which are even worse. Commanders
\r
139 are about three times stronger than ordinary Klingons. Commanders are
\r
140 more resistant to your weapons. Commanders can move about during
\r
141 battle while Ordinary Klingons stay put. And finally, Commanders have
\r
142 a thing called a <quote>long-range tractor beam</quote> which they can
\r
143 use, at random intervals, to yank you away from what you are doing
\r
144 into their quadrant, to do battle with them. There is also a special
\r
145 commander, called the <quote>Super-commander.</quote> This character
\r
146 is so bad he is reserved for the Good, Expert, and Emeritus games.
\r
147 Fortunately, there is just one Super-commander in a game. In addition
\r
148 to the undesirable traits of Commanders, he can move from quadrant to
\r
149 quadrant at will, seeking out and destroying your starbases and any
\r
150 helpful planets he runs across. He also has a spy planted aboard your
\r
151 ship, giving him valuable information about your condition. Using
\r
152 this information, he can do dastardly things like tractor beam your
\r
153 ship when you are in bad shape. And once you've been tractor beamed
\r
154 by the Super-commander —</para>
\r
156 <para>But the advantages are not all on the side of the enemy. Your ship
\r
157 is more powerful, and has better weapons. Besides, in the this
\r
158 galaxy there are from two to five starbases, at which you can stop to
\r
159 refuel and lick your wounds, safe from phaser attack or tractor
\r
160 beams. But you had best not dally there too long, since time is not
\r
161 on your side. The Klingons are not just after you; they are
\r
162 attacking the entire Federation. There is always a finite <quote>time
\r
163 left,</quote> which is how much longer the Federation can hold out if you
\r
164 just sit on your fat behind and do nothing. As you wipe out
\r
165 Klingons, you reduce the rate at which the invasion fleet weakens the
\r
166 Federation, and so the time left until the Federation collapses may
\r
167 actually increase. Since Klingons are the main threat to the
\r
168 Federation, the Romulans do not figure into the <quote>time left.</quote> In
\r
169 fact, you need not kill all the Romulans to win. If you can get all
\r
170 the Klingons, the Federation will abide forever, and you have won the
\r
173 <para>Space is vast, and it takes precious time to move from one place to
\r
174 another. In comparison, other things happen so quickly that we
\r
175 assume the take no time at all. Two ways that time can pass are when
\r
176 you move, or when you issue a command to sit still and rest for a
\r
177 period of time. You will sometimes want to do the latter, since the
\r
178 various devices aboard your starship may be damaged and require time
\r
179 to repair. Of course, repairs can be made more quickly at a starbase
\r
180 than than can in flight.</para>
\r
182 <para>In addition to Klingons, Romulans, and starbases, the galaxy
\r
183 contains (surprise) stars. Mostly, stars are a nuisance and just get
\r
184 in your way. You can trigger a star into going nova by shooting one
\r
185 of your photon torpedoes at it. When a star novas, it does a lot of
\r
186 dammage to anything immediately adjacent to it. If another star is
\r
187 adjacent to a nova, it too will go nova. Stars may also occasionally
\r
188 go supernova; a supernova in a quadrant destroys everything in the
\r
189 quadrant andmakes the quadrant permanently uninhabitable. You may
\r
190 <quote>jump over</quote> a quadrant containing a supernova when you
\r
191 move, but you should not stop there.</para>
\r
193 <para>Supernovas may happen spontaneously, without provocation. If a
\r
194 supernova occurs in the same quadrant you are in, your starship has an
\r
195 <quote>emergency automatic override</quote> which picks some random
\r
196 direction and some random warp factor, and tries to throw you clear of
\r
197 the supernova. If the supernova occurs in some other quadrant, you
\r
198 just get a warning message from starfleet about it (provided, of
\r
199 course, that your subspace radio is working).</para>
\r
201 <para>Also a few planets are scattered through the galaxy. These can
\r
202 sometimes be a great help since some of them will have <quote>dilithium
\r
203 crystals,</quote> which are capable of replenishing the ship's energy
\r
204 supply. You can either beam down to the planet surface using the
\r
205 transporter, or take the shuttle craft <quote>Galileo</quote>.</para>
\r
207 <para>Finally, each quadrant will contain from zero to three black
\r
208 holes. These can deflect or swallow torpedoes passing near them. They
\r
209 also swallow enemy ships knocked into them. If your ship enters one
\r
212 <para>Star Trek is a rich game, full of detail. These instructions are
\r
213 written at a moderate level—no attempt has been made fully to
\r
214 describe everything about the game, but there is quite a bit more
\r
215 here than you need to get started. If you are new to the game, just
\r
216 get a rough idea of the kinds of commands available, and start
\r
217 playing. After a game or two you will have learned everthing
\r
218 important, and the detailed command descriptions which follow will be
\r
219 a lot more meaningful to you.</para>
\r
221 <para>You have weapons: phasers and photon torpedoes. You have a defense:
\r
222 deflector shields. You can look at things: long-range scaners,
\r
223 short-range scanners, and a star chart. You can move about, under
\r
224 warp drive or impulse power. You can also dock at a starbase, rest
\r
225 while repairs are being made, abandon ship, self destruct, or give up
\r
226 and start a new game.</para>
\r
228 <para>The Klingons are waiting.</para>
\r
231 <chapter><title>How To Issue Commands</title>
\r
233 <para>When the game is waiting for you to enter a command it will
\r
240 <para>You may then type in your command. All you have to remember for each
\r
241 command is the mnemonic. For example, if you want to move straight up
\r
242 one quadrant, you can type in the mnemonic (case insensitive)</para>
\r
248 <para>and the computer will prompt you with</para>
\r
251 Manual or automatic-
\r
254 <para>Say you type in <quote>manual</quote>. The computer then responds</para>
\r
257 X and Y displacements-
\r
260 <para>Now you type in <quote>0 1</quote> which specifies an X movement of zero and a Y
\r
261 movement of one.</para>
\r
263 <para>When you have learned the commands, you can avoid being prompted
\r
264 simply by typing in the information without waiting to be asked for
\r
265 it. For example, in the above example, you could simply type in</para>
\r
271 <para>and it will be done. Or you could type in</para>
\r
277 <para>and when the computer responds with the displacement prompt, you
\r
284 <para>and it will understand.</para>
\r
286 <para>You can abbreviate most mnemonics. For <quote>move</quote>, you can use any
\r
293 <para>successfully. For your safety, certain critical commands (such as to
\r
294 abandon ship) must be written out in full. Also, in a few cases two
\r
295 or more commands begin with the same letter, and in this case that
\r
296 letter refers to a particular one of the commands; to get the other,
\r
297 your abbreviation must be two or more characters long. This sounds
\r
298 complicated, but you will learn the abbreviations qGuickly enough.</para>
\r
300 <para>What this all boils down to is:</para>
\r
303 <listitem><para>You can abbreviate practically anything</para></listitem>
\r
304 <listitem><para>If you forget, the computer will proompt you</para></listitem>
\r
305 <listitem><para>If you remember, you can type it all on one line</para></listitem>
\r
308 <para>If you are part way through entering a command and you change your
\r
309 minde, you can cancel the command by typing -1 as one of the
\r
310 parameters, with the exception of the manual move command.</para>
\r
312 <para>If anything is not clear to you, experiment. The worst you can do is
\r
313 lose a game or two.</para>
\r
316 <chapter><title>List of Commands</title>
\r
318 <sect1><title>Short-Range Scan</title>
\r
322 Shortest abbreviation: S
\r
323 Full commands: SRSCAN
\r
328 <!-- This is new in SST 2K -->
\r
329 <para>If you are using the screen-oriented interface, it should never
\r
330 be necessary to call this command explicitly; a short-range scan will
\r
331 always be present on the screen.</para>
\r
333 <para>The short-range scan gives you a considerable amount of information
\r
334 about the quadrant your starship is in. A short-range scan is best
\r
335 described by an example.</para>
\r
338 1 2 3 4 5 6 7 8 9 10
\r
339 1 * . . . . R . . . . Stardate 2516.3
\r
340 2 . . . E . . . . . . Condition RED
\r
341 3 . . . . . * . B . . Position 5 - 1, 2 - 4
\r
342 4 . . . S . . . . . . Life Support DAMAGED, Reserves=2.30
\r
343 5 . . . . . . . K . . Warp Factor 5.0
\r
344 6 . K . . . . . * . Energy 2176.24
\r
345 7 . . . . . P . . . . Torpedoes 3
\r
346 8 . . . . * . . . . . Shields UP, 42% 1050.0 units
\r
347 9 . * . . * . . . C . Klingons Left 12
\r
348 10 . . . . . . . . . . Time Left 3.72
\r
351 <para>The left part is a picture of the quadrant. The E at sector 2 -
\r
352 4 represents the Enterprise; the B at sector 3 - 8 is a starbase.
\r
353 There are ordinary Klingons (K) at sectors 5 - 8 and 6 - 2, and a
\r
354 Klingon Commander (C) at 9 - 9. The (GULP)
\r
355 <quote>Super-commander</quote> (S) is occupies sector 4 - 4, and a
\r
356 Romulan (R) is at 1 - 6. A planet (P) is at sector 7 - 6. There are
\r
357 also a large number of stars (*). The periods (.) are just empty
\r
358 space—they are printed to help you get your bearings. Sector 6
\r
359 - 4 contains a black hole ( ).</para>
\r
361 <para>The information on the right is assorted status information. You
\r
362 can get this alone with the STATUS command. The status information
\r
363 will be absent if you type <quote>N</quote> after SRSCAN. Otherwise
\r
364 status information will be presented.</para>
\r
366 <para>If you type <quote>C</quote> after SRSCAN, you will be given a
\r
367 short-range scan and a Star Chart.</para>
\r
369 <para>Short-range scans are free. That is, they use up no energy and no
\r
370 time. If you are in battle, doing a short-range scan does not give
\r
371 the enemies another chance to hit you. You can safely do a
\r
372 short-range scan anytime you like.</para>
\r
374 <para>If your short-range sensors are damaged, this command will only show
\r
375 the contents of adjacent sectors.</para>
\r
377 <sect1><title>Status Report</title>
\r
381 Shortest abbreviation: ST
\r
384 <para>This command gives you information about the current state of your
\r
385 starship as follows:</para>
\r
389 <term>STARDATE</term>
\r
391 <para>The current date. A stardate is the same as a day.</para>
\r
395 <term>CONDITION</term>
\r
397 <para>There are four possible conditions:</para>
\r
400 <term>DOCKED</term>
\r
401 <listitem><para>docked at starbase.</para></listitem>
\r
405 <listitem><para>in battle.</para></listitem>
\r
408 <term>YELLOW</term>
\r
409 <listitem><para>low on energy (<1000 units)</para></listitem>
\r
413 <listitem><para>none of the above</para></listitem>
\r
419 <term>POSITION</term>
\r
421 <para>Quadrant is given first, then sector</para>
\r
425 <term>LIFE SUPPOR</term>
\r
427 <para>If <quote>ACTIVE</quote> then life support systems are functioning
\r
428 normally. If on <quote>RESERVES</quote> the number is how many stardates your
\r
429 reserve food, air, etc. will last—you must get repairs made or get to
\r
430 starbase before your reserves run out.</para>
\r
434 <term>WARP FACTOR</term>
\r
436 <para>What your warp factor is currently set to.</para>
\r
440 <term>ENERGY</term>
\r
442 <para>The amount of energy you have left. If it drops to zero, you die.</para>
\r
446 <term>TORPEDOES</term>
\r
448 <para>How many photon torpedoes you have left.</para>
\r
452 <term>SHIELDS</term>
\r
454 <para>Whether your shields are up or down, how strong they are
\r
455 (what percentage of a hit they can deflect), and shield energy.</para>
\r
459 <term>KLINGONS LEFT</term>
\r
461 <para>How many of the Klingons are still out there.</para>
\r
465 <term>TIME LEFT</term>
\r
467 <para>How long the Federation can hold out against the
\r
468 present number of Klingons; that is, how long until the end
\r
469 if you do nothing in the meantime. If you kill Klingons
\r
470 quickly, this number will go up—if not, it will go down. If
\r
471 it reaches zero, the federation is conquered and you lose.</para>
\r
476 <para>Status information is free—it uses no time or energy, and if you are
\r
477 in battle, the Klingons are not given another chance to hit you.</para>
\r
479 <para>Status information can also be obtained by doing a short-range scan.
\r
480 See the SRSCAN command for details.</para>
\r
482 <para>Each item of information can be obtained singly by requesting it.
\r
483 See REQUEST command for details.</para>
\r
486 <sect1><title>Long-Range Scan</title>
\r
490 Shortest abbreviation: L
\r
493 <!-- This is new in SST 2K -->
\r
494 <para>If you are using the screen-oriented interface, it should never
\r
495 be necessary to call this command explicitly; a long-range scan will
\r
496 always be present on the screen.</para>
\r
498 <para>A long-range scan gives you general information about where you are
\r
499 and what is around you. Here is an example output.</para>
\r
502 Long-range scan for Quadrant 5 - 1
\r
508 <para>This scan says that you are in row 5, column 1 of the 8 by 8 galaxy.
\r
509 The numbers in the scan indicate how many of each kind of thing there
\r
510 is in your quadrant and all adjacent quadrants. The digits are
\r
511 interpreted as follows.</para>
\r
517 <entry>Thousands digit:</entry>
\r
518 <entry>1000 indicates a supernova (only)</entry>
\r
521 <entry>Hundreds digit:</entry>
\r
522 <entry>number of Klingons present</entry>
\r
525 <entry>Tens digit:</entry>
\r
526 <entry>number of starbases present</entry>
\r
529 <entry>Ones digit:</entry>
\r
530 <entry>number of stars present</entry>
\r
536 <para>For example, in your quadrant (5 - 1) the number is 316, which
\r
537 indicates 3 Klingons, 1 starbase, and 6 stars. The long-range
\r
538 scanner does not distinguish between ordinary Klingons and Klingon
\r
539 command ships. If there is a supernova, as in the quadrant below and
\r
540 to your right (quadrant 6 - 2), there is nothing else in the
\r
543 <para>Romulans possess a <quote>cloaking device</quote> which prevents
\r
544 their detection by long-range scan. Because of this fact, Starfleet
\r
545 Command is never sure how many Romulans are <quote>out there</quote>.
\r
546 When you kill the last Klingon, the remaining Romulans surrender to
\r
547 the Federation.</para>
\r
549 <para>Planets are also undetectable by long-range scan. The only way to
\r
550 detect a planet is to find it in your current quadrant with the
\r
551 short-range sensors.</para>
\r
553 <para>Since you are in column 1, there are no quadrants to your left. The
\r
554 minus ones indicate the negative energy barrier at the edge of the
\r
555 galaxy, which you are not permitted to cross.</para>
\r
557 <para>Long-range scans are free. They use up no energy or time, and can be
\r
558 done safely regardless of battle conditions.</para>
\r
560 <sect1><title>Star Chart</title>
\r
564 Shortest abbreviation: C
\r
567 <para>As you proceed in the game, you learn more and more about what things
\r
568 are where in the galaxy. When ever you first do a scan in a quadrant,
\r
569 telemetry sensors are ejected which will report any changes in the
\r
570 quadrant(s) back to your ship, providing the sub-space radio is
\r
571 working. Spock will enter this information in the chart. If the radio
\r
572 is not working, Spock can only enter new information discovered from
\r
573 scans, and information in other quadrants may be obsolete.</para>
\r
575 <para>The chart looks like an 8 by 8 array of numbers. These numbers are
\r
576 interpreted exactly as they are on a long-range scan. A period (.) in
\r
577 place of a digit means you do not know that information yet. For
\r
578 example, ... means you know nothing about the quadrant, while .1.
\r
579 menas you know it contains a base, but an unknown number of Klingons
\r
582 <para>Looking at the star chart is a free operation. It costs neither time
\r
583 nor energy, and can be done safely whether in or out of battle.</para>
\r
586 <sect1><title>Damage Report</title>
\r
590 Shortest abbreviation: DA
\r
593 <para>At any time you may ask for a damage report to find out what devices
\r
594 are damaged and how long it will take to repair them. Naturally,
\r
595 repairs proceed faster at a starbase.</para>
\r
597 <para>If you suffer damages while moving, it is possible that a subsequent
\r
598 damage report will not show any damage. This happens if the time
\r
599 spent on the move exceeds the repair time, since in this case the
\r
600 damaged devices were fixed en route.</para>
\r
602 <para>Damage reports are free. They use no energy or time, and can be done
\r
603 safely even in the midst of battle.</para>
\r
606 <sect1><title>Move Under Warp Drive</title>
\r
610 Shortest abbreviation: M
\r
611 Full command: MOVE MANUAL <displacement>
\r
612 MOVE AUTOMATIC <destination>
\r
615 <para>This command is the usual way to move from one place to another
\r
616 within the galaxy. You move under warp drive, according to the
\r
617 current warp factor (see <quote>WARP FACTOR</quote>).</para>
\r
619 <para>There are two command modes for movement: MANUAL and AUTOMATIC.
\r
620 The manual mode requires the following format:</para>
\r
623 MOVE MANUAL <deltax> <deltay>
\r
626 <para><deltax> and <deltay> are the horizontal and vertical
\r
627 displacements for your starship, in quadrants; a displacement of one
\r
628 sector is 0.1 quadrants. Specifying <deltax> and <deltay>
\r
629 causes your ship to move in a straight line to the specified
\r
630 destination. If <deltay> is omitted, it is assumed zero. For
\r
631 example, the shortest possible command to move one sector to the right
\r
638 <para>The following examples of manual movement refer to the short-range
\r
639 scan shown earlier.</para>
\r
642 Destination Sector Manual Movement command
\r
647 (leaving quadrant) M M 0 .2
\r
650 <para>The automatic mode is as follows:</para>
\r
653 MOVE AUTOMATIC <qrow> <qcol> <srow> <scol>
\r
656 <para><para>where <qrow> and <qcol> are the row and column
\r
657 numbers of the destination quadrant, and <srow> and <scol>
\r
658 are the row and column numbers of the destination sector in that
\r
659 quadrant. This command also moves your ship in a straight line path
\r
660 to the destination. For moving within a quadrant, <qrow> and
\r
661 <qcol> may be omitted. For example, to move to sector 2 - 9 in
\r
662 the current quadrant, the shortest command would be</para>
\r
668 <para>To move to quadrant 3 - 7, sector 5 - 8, type</para>
\r
674 <para>and it will be done. In automatic mode, either two or four numbers
\r
675 must be supplied.</para>
\r
677 <para>Automatic mode utilizes the ship's <quote>battle computer.</quote> If the
\r
678 computer is damaged, manual movement must be used.</para>
\r
680 <para>If warp engines are damaged less than 10 stardates (undocked) you can
\r
681 still go warp 4.</para>
\r
683 <para>It uses time and energy to move. How much time and how much energy
\r
684 depends on your current warp factor, the distance you move, and
\r
685 whether your shields are up. The higher the warp factor, the faster
\r
686 you move, but higher warp factors require more energy. You may move
\r
687 with your shields up, but this doubles the energy required.</para>
\r
689 <para>You can move within a quadrant without being attacked if you just
\r
690 entered the quadrant or have been attacked since your last move
\r
691 command. This enables you to move and hit them before they
\r
695 <sect1><title>Warp Factor</title>
\r
699 Shortest abbreviation: W
\r
700 Full command: WARP <number>
\r
703 <para>Your warp factor controls the speed of your starship. The larger the
\r
704 warp factor, the faster you go and the more energy you use.</para>
\r
706 <para>Your minimum warp factor is 1.0 and your maximum warp factor is 10.0
\r
707 (which is 100 times as fast and uses 1000 times as much energy). At
\r
708 speeds above warp 6 there is some danger of causing damage to your
\r
709 warp engines; this damage is larger at higher warp factors and also
\r
710 depends on how far you go at that warp factor.</para>
\r
712 <para>At exactly warp 10 there is some probability of entering a
\r
713 so-called <quote>time warp</quote> and being thrown foward or backward
\r
714 in time. The farther you go at warp 10, the greater is the
\r
715 probability of entering the time warp.</para>
\r
718 <sect1><title>Impulse Engines</title>
\r
722 Shortest abbreviation: I
\r
723 Full command: IMPULSE MANUAL <displacement>
\r
724 IMPULSE AUTOMATIC <destination>
\r
727 <para>The impulse engines give you a way to move when your warp engines are
\r
728 damaged. They move you at a speed of 0.95 sectors per stardate,
\r
729 which is the equivalent of a warp factor of about 0.975, so they are
\r
730 much too slow to use except in emergencies.</para>
\r
732 <para>Movement commands are indicated just as in the <quote>MOVE</quote> command.</para>
\r
734 <para>The impulse engines require 20 units of energy to engage, plus 10
\r
735 units per sector (100 units per quadrant) traveled. It does not cost
\r
736 extra to move with the shields up.</para>
\r
739 <sect1><title>Deflector Shields</title>
\r
743 Shortest abbreviation: SH
\r
744 Full commands: SHIELDS UP
\r
746 SHIELDS TRANSFER <amount of energy to transfer>
\r
749 <para>Your deflector shields are a defensive device to protect you from
\r
750 Klingon attacks (and nearby novas). As the shields protect you, they
\r
751 gradually weaken. A shield strength of 75%, for example, means that
\r
752 the next time a Klingon hits you, your shields will deflect 75% of
\r
753 the hit, and let 25% get through to hurt you.</para>
\r
755 <para>It costs 50 units of energy to raise shields, nothing to lower them.
\r
756 You may move with your shields up; this costs nothing under impulse
\r
757 power, but doubles the energy required for warp drive.</para>
\r
759 <para>Each time you raise or lower your shields, the Klingons have another
\r
760 chance to attack. Since shields do not raise and lower
\r
761 instantaneously, the hits you receive will be intermediate between
\r
762 what they would be if the shields were completely up or completely
\r
765 <para>You may not fire phasers through your shields. However you may use
\r
766 the <quote>high-speed shield control</quote> to lower shields, fire phasers, and
\r
767 raise the shields again before the Klingons can react. Since rapid
\r
768 lowering and raising of the shields requires more energy than normal
\r
769 speed operation, it costs you 200 units of energy to activate this
\r
770 control. It is automatically activated when you fire phasers while
\r
771 shields are up. You may fire photon torpedoes, but they may be
\r
772 deflected considerably from their intended course as they pass
\r
773 through the shields (depending on shield strength).</para>
\r
775 <para>You may transfer energy beteen the ship's energy (given as
\r
776 <quote>Energy</quote> in the status) and the shields. Thee word
\r
777 <quote>TRANSFER</quote> may be abbreviated <quote>T</quote>. The
\r
778 ammount of energy to transfer is the number of units of energy you
\r
779 wish to take from the ship's energy and put into the shields. If you
\r
780 specify an negative number, energy is drained from the shields to the
\r
781 ship. Transfering energy constitutes a turn. If you transfer energy
\r
782 to the shields while you are under attack, they will be at the new
\r
783 energy level when you are next hit.</para>
\r
785 <para>Enemy torpedoes hitting your ship explode on your shields (if they
\r
786 are up) and have essentially the same effect as phaser hits.</para>
\r
789 <sect1><title>Phasers</title>
\r
793 Shortest abbreviation: P
\r
794 Full commands: PHASERS AUTOMATIC <AMOUNT TO FIRE> <NO>
\r
795 PHASERS <AMOUNT TO FIRE> <NO>
\r
796 PHASERS MANUAL <NO> <AMOUNT 1> <AMOUNT 2>...<AMOUNT N>
\r
799 <para>Phasers are energy weapons. As you fire phasers at Klingons, you
\r
800 specify an <quote>amount to fire</quote> which is drawn from your
\r
801 energy reserves. The amount of total hit required to kill an enemy is
\r
802 partly random. but also depends on skill level.</para>
\r
804 <para>The average hit required to kill an ordinary Klingon varies from 200
\r
805 units in the Novice game to 250 units in the Emeritus game.
\r
806 Commanders normally require from 600 (Novice) to 700 (Emeritus). The
\r
807 Super-commander requres from 875 (Good) to 1000 (Emeritus). Romulans
\r
808 require an average of 350 (Novice) to 450 (Emeritus).</para>
\r
810 <para>Hits on enemies are cumulative, as long as you don't leave the
\r
813 <para>In general, not all that you fire will reach the Klingons. The
\r
814 farther away they are, the less phaser energy will reach them. If a
\r
815 Klingon is adjacent to you, he will receive about 90% of the phaser
\r
816 energy directed at him; a Klingon 5 sectors away will receive about
\r
817 60% and a Klingon 10 sectors away will receive about 35%. There is
\r
818 some randomness involved, so these figures are not exact. Phasers
\r
819 have no effect beyond the boundaries of the quadrant you are in.</para>
\r
821 <para>Phasers may overheat (and be damaged) if you fire too large a burst
\r
822 at once. Firing up to 1500 units is safe. From 1500 on up the
\r
823 probability of overheat increases with the amount fired.</para>
\r
825 <para>If phaser firing is automatic, the computer decides how to
\r
826 divide up your <amount to fire> among the Klingons present. If
\r
827 phaser firing is manual, you specify how much energy to fire at each
\r
828 Klingon present (nearest first), rather than just specifying a total
\r
829 amount. You can abreviate <quote>MANUAL</quote> and
\r
830 <quote>AUTOMATIC</quote> to one or more letters; if you mention
\r
831 neither, automatic fire is usually assumed.</para>
\r
833 <para>Battle computer information is available by firing phasers manually,
\r
834 and allowing the computer to prompt you. If you enter zero for the
\r
835 amount to fire at each enemy, you will get a complete report, without
\r
836 cost. The battle computer will tell you how much phaser energy to
\r
837 fire at each enemy for a sure kill. This information appears in
\r
838 parentheses prior to the prompt for each enemy. Since the amount is
\r
839 computed from sensor data, if either the computer or the S.R. sensors
\r
840 are damaged, this information will be unavailable, and phasers must
\r
841 be fired manually.</para>
\r
843 <para>A safety interlock prevents phasers from being fired through
\r
844 the shields. If this were not so, the shields would contain your fire
\r
845 and you would fry yourself. However, you may utilize the
\r
846 <quote>high-speed shield control</quote> to drop shields, fire
\r
847 phasers, and raise shields before the enemy can react. Since it takes
\r
848 more energy to work the shields rapidly with a shot, it costs you 200
\r
849 units of energy each time you activate this control. It is
\r
850 automatically activated when you fire phasers while the shields are
\r
851 up. By specifying the <no> option, shields are not raised after
\r
854 <para>Phasers have no effect on starbases (which are shielded) or on
\r
858 <sect1><title>Report</title>
\r
862 Shortest abbreviation: REP
\r
865 <para>This command supplies you with information about the state of the
\r
866 current game. Its purpose is to remind you of things that you have
\r
867 learned during play, but may have forgotten, and cannot otherwise
\r
868 retrieve if you are not playing at a hard-copy terminal.</para>
\r
870 <para>You are told the following things:</para>
\r
873 <listitem><para>The length and skill level of the game you are playing</para></listitem>
\r
874 <listitem><para>The original number of Klingons</para></listitem>
\r
875 <listitem><para>How many Klingons you have destroyed</para></listitem>
\r
876 <listitem><para>Whether the Super-Commander has been destroyed</para></listitem>
\r
877 <listitem><para>How many bases have been destroyed</para></listitem>
\r
878 <listitem><para>How many bases are left</para></listitem>
\r
879 <listitem><para>What bases (if any) are under attack; your subspace radio
\r
880 must have been working since the attack to get this
\r
881 information.</para></listitem>
\r
882 <listitem><para>How many casualties you have suffered</para></listitem>
\r
883 <listitem><para>How many times you have called for help.</para></listitem>
\r
886 <para>This same information is automatically given to you when you start to
\r
887 play a frozen game.</para>
\r
890 <sect1><title>Computer</title>
\r
894 Shortest abbreviation: CO
\r
897 <para>This command allows using the ship's computer (if functional) to
\r
898 calculate travel times and energy usage.</para>
\r
901 <sect1><title>Photon Torpedoes</title>
\r
905 Shortest abbreviation: PHO
\r
906 Full commands: PHOTONS <NUMBER> <TARG1> <TARG2> <TARG3>
\r
909 <para>Photon torpedoes are projectile weapons—you either hit what you aim
\r
910 at, or you don't. There are no <quote>partial hits</quote>.</para>
\r
912 <para>One photon torpedo will usually kill one ordinary Klingon, but it
\r
913 usually takes about two for a Klingon Commander. Photon torpedoes
\r
914 can also blow up stars and starbases, if you aren't careful.</para>
\r
916 <para>You may fire photon torpedoes singly, or in bursts of two or three.
\r
917 Each torpedo is individually targetable. The computer will prompt
\r
918 you, asking for the target sector for each torpedo. Alternately, you
\r
919 may specify each target in the command line.</para>
\r
921 <para>Photon torpedoes cannot be aimed precisely—there is always some
\r
922 randomness involved in the direction they go. Photon torpedoes may
\r
923 be fired with your shields up, but as they pass through the shields
\r
924 they are randomly deflected from their intended course even more.</para>
\r
926 <para>Photon torpedoes are proximity-fused. The closer they explode to the
\r
927 enemy, the more damage they do. There is a hit <quote>window</quote> about one
\r
928 sector wide. If the torpedo misses the hit window, it does not
\r
929 explode and the enemy is unaffected. Photon torpedoes are only
\r
930 effective within the quadrant. They have no effect on things in
\r
931 adjacent quadrants.</para>
\r
933 <para>If more than one torpedo is fired and only one target sector is
\r
934 specified, all torpedoes are fired at that sector. For example, to
\r
935 fire two torpedoes at sector 3 - 4, you type</para>
\r
938 PHO 2 3 4 (or) PHO 2 3 4 3 4
\r
941 <para>To fire torpedoes at, consecutively, sectors 2 - 6, 1 - 10, and 4 -
\r
948 <para>There is no restriction to fire directly at a sector. For example,
\r
949 you can enter</para>
\r
955 <para>to aim between two sectors. However, sector numbers must be 1 to 10
\r
959 <sect1><title>Dock at Starbase</title>
\r
963 Shortest abbreviation: D
\r
966 <para>You may dock your starship whenever you are in one of the eight
\r
967 sector positions immediately adjacent to a starbase. When you dock,
\r
968 your starship is resupplied with energy, shield energy photon
\r
969 torpedoes, and life support reserves. Repairs also proceed faster at
\r
970 starbase, so if some of your devices are damaged, you may wish to stay
\r
971 at base (by using the <quote>REST</quote> command) until they are
\r
972 fixed. If your ship has more than its normal maximum energy (which
\r
973 can happen if you've loaded crystals) the ship's energy is not
\r
976 <para>You may not dock while in standard orbit around a planet.</para>
\r
978 <para>Starbases have their own deflector shields, so you are completely
\r
979 safe from phaser attack while docked. You are also safe from
\r
980 long-range tractor beams.</para>
\r
982 <para>Starbases also have both short and long range sensors, which you can
\r
983 use if yours are broken. There's also a subspace radio to get
\r
984 information about happenings in the galaxy. Mr. Spock will update the
\r
985 star chart if your ask for it while docked and your own radio is dead.</para>
\r
988 <sect1><title>Rest</title>
\r
992 Shortest abbreviation: R
\r
993 Full command: REST <NUMBER OF STARDATES>
\r
996 <para>This command simply allows the specified number of stardates to go
\r
997 by. This is useful if you have suffered damages and wish to wait
\r
998 until repairs are made before you go back into battle.</para>
\r
1000 <para>It is not generally advisable to rest while you are under attack by
\r
1004 <sect1><title>Call Starbase for Help</title>
\r
1011 <para>[Originally, this command was called <quote>HELP</quote>, but
\r
1012 these days it might be misinterpreted as built-in
\r
1013 documentation!]</para>
\r
1015 <para>When you get into serious trouble, you may call starbase for
\r
1016 help. Starbases have a device called a <quote>long-range transporter
\r
1017 beam</quote> which they can use to teleport you to base. This works
\r
1018 by dematerializing your starship at its current position and
\r
1019 re-materializing it adjacent to the nearest starbase. Teleportation
\r
1020 is instantaneous, and starbase supplies the required energy—all
\r
1021 you have to do is let them know (via subspace radio) that you need to
\r
1022 be rescued.</para>
\r
1024 <para>This command should be employed only when absolutely necessary. In
\r
1025 the first place, calling for help is an admission on your part that
\r
1026 you got yourself into something you cannot get yourself out of, and
\r
1027 you are heavily penalized for this in the final scoring. Secondly,
\r
1028 the long-range transporter beam is not reliable—starbase can always
\r
1029 manage to dematerialize your starship, but (depending on distance)
\r
1030 may or may not be able to re-materialize you again. The long-range
\r
1031 transporter beam has no absolute maximum range; if you are in the
\r
1032 same quadrant as a starbase, you have a good chance (about 90%) of
\r
1033 re-materializing successfully. your chances drop to roughly 50-50 at
\r
1034 just over 3 quadrants.</para>
\r
1037 <sect1><title>Abandon Ship</title>
\r
1044 <para>You may abandon the Enterprise if necessary. If there is still a
\r
1045 starbase in the galaxy, you will be sent there and put in charge of a
\r
1046 weaker ship, the Faerie Queene.</para>
\r
1048 <para>The Faerie Queene cannot be abandoned.</para>
\r
1051 <sect1><title>Self-Destruct</title>
\r
1054 Mnemonic: DESTRUCT
\r
1058 <para>You may self-destruct, thus killing yourself and ending the game. If
\r
1059 there are nearby Klingons, you may take a few of them with you (the
\r
1060 more energy you have left, the bigger the bang).</para>
\r
1062 <para>In order to self-destruct you must remember the password you typed in
\r
1063 at the beginning of the game.</para>
\r
1066 <sect1><title>Quit Game</title>
\r
1073 <para>Immediately cancel the current game; no conclusion is reached. You
\r
1074 will be given an opportunity to start a new game or to leave the Star
\r
1075 Trek program.</para>
\r
1078 <sect1><title>Sensor-Scan</title>
\r
1082 Shortest abbreviation: SE
\r
1085 <para>Utilizing the short-range sensors, science officer Spock gives you a
\r
1086 readout on any planet in your quadrant. Planets come in three
\r
1087 classes: M, N, and O. Only class M planets have earth-like
\r
1088 conditions. Spock informs you if the planet has any dilithium
\r
1089 crystals. Sensor scans are free.</para>
\r
1092 <sect1><title>Enter Standard Orbit</title>
\r
1096 Shortest abbreviation: O
\r
1099 <para>To land on a planet you must first be in standard orbit. You achieve
\r
1100 this in a manner similar to docking at starbase. Moving to one of
\r
1101 the eight sector positions immediately adjacent to the planet, you
\r
1102 give the orbit command which puts your ship into standard orbit about
\r
1103 the planet. Since this is a maneuver, a small amount of time is
\r
1104 used; negligible energy is required. If enemies are present, they
\r
1105 will attack.</para>
\r
1108 <sect1><title>Transporter Travel</title>
\r
1111 Mnemonic: TRANSPORT
\r
1112 Shortest abbreviation: T
\r
1115 <para>The transporter is a device which can convert any physical object
\r
1116 into energy, beam the energy through space, and reconstruct the
\r
1117 physical object at some destination. Transporting is one way to land
\r
1118 on a planet. Since the transporter has a limited range, you must be
\r
1119 in standard orbit to beam down to a planet. Shields must be down
\r
1120 while transporting.</para>
\r
1122 <para>The transport command is used to beam a landing party onto a planet
\r
1123 to mine <quote>dilithium crystals</quote>. Each time the command is given the
\r
1124 landing party (which you lead) moves from the ship to the planet, or
\r
1125 vice-versa.</para>
\r
1127 <para>You are advised against needless transporting, since like all
\r
1128 devices, the transporter will sometimes malfunction.</para>
\r
1130 <para>The transporter consumes negligible time and energy. Its use does
\r
1131 not constitute a <quote>turn</quote>.</para>
\r
1134 <sect1><title>Shuttle Craft</title>
\r
1138 Shortest abbreviation: SHU
\r
1141 <para>An alternate way to travel to and from planets. Because of limited
\r
1142 range, you must be in standard orbit to use the shuttle craft, named
\r
1143 "Galileo". Shields must be down.</para>
\r
1145 <para>Unlike transporting, use of the shuttle craft does constitute a
\r
1146 <quote>turn</quote> since time is consumed. The time naturally
\r
1147 depends on orbit altitude, and is equal to 3.0e-5 times altitude.
\r
1148 Shuttling uses no ship energy.</para>
\r
1150 <para>You should use the same travel device going from the planet to the
\r
1151 ship as you use to go from the ship to the planet. However it is
\r
1152 possible to transport to the planet and have the Galileo crew come
\r
1153 and pick your landing party up, or to take the Galileo to the planet
\r
1154 and then transport back, leaving the shuttle craft on the planet.</para>
\r
1157 <sect1><title>Mine Dilithium Crystals</title>
\r
1161 Shortest abbreviation: MI
\r
1164 <para>Once you and your mining party are on the surface of a planet which
\r
1165 has dilithium crystals, this command will dig them for you.</para>
\r
1167 <para>Mining requires time and constitutes a <quote>turn</quote>. No
\r
1168 energy is used. Class M planets require 0.1 to 0.3 stardates to mine.
\r
1169 Class N planets take twice as long, and class O planets take three
\r
1170 times as long.</para>
\r
1172 <para>Dilithium crystals contain enormous energy in a form that is readily
\r
1173 released in the ship's power system. It is an excellent idea to mine
\r
1174 them whenever possible, for use in emergencies. You keep the
\r
1175 crystals until the game is over or you abandon ship when not at a
\r
1179 <sect1><title>Load Dilithium Crystals</title>
\r
1182 Mnemonic: CRYSTALS
\r
1183 Shortest abbreviation: CR
\r
1186 <para>This is a very powerful command which should be used with caution.
\r
1187 Once you have dilithium crystals aboard ship, this command will
\r
1188 instruct engineering officer Scott and Mr. Spock to place a raw
\r
1189 dilithium crystal into the power channel of the ship's
\r
1190 matter-antimatter converter. When it works, this command will
\r
1191 greatly boost the ship's energy.</para>
\r
1193 <para>Because the crystals are raw and impure, instabilities can occur in
\r
1194 the power channel. Usually Scotty can control these. When he
\r
1195 cannot, the results are disastrous. Scotty will use those crystals
\r
1196 that appear to be most stable first.</para>
\r
1198 <para>Since using raw dilithium crystals for this purpose entails
\r
1199 considerable risk, Starfleet Regulations allow its use only during
\r
1200 "condition yellow". No time or energy is used.</para>
\r
1203 <sect1><title>Planet Report</title>
\r
1207 Shortest abbreviation: PL
\r
1210 <para>Mr. Spock presents you a list of the available information on planets
\r
1211 in the galaxy. Since planets do not show up on long-range scans, the
\r
1212 only way to obtain this information is with the <quote>SENSORS</quote> command.</para>
\r
1215 <sect1><title>Freeze</title>
\r
1220 Full command: FREEZE <FILE NAME>
\r
1223 <para>The purpose of the FREEZE command is to allow a player to save the
\r
1224 current state of the game, so that it can be finished later. A
\r
1225 plaque may not be generated from a frozen game. A file with the
\r
1226 specified <file name> and type '.TRK' is created (if necessary) in
\r
1227 the current directory, and all pertinent information about the game
\r
1228 is written to that file. The game may be continued as usual or be
\r
1229 terminated at the user's option.</para>
\r
1231 <para>To restart a game created by the <quote>FREEZE</quote> command,
\r
1232 the user need only type <quote>FROZEN</quote> in response to the
\r
1233 initial question about the type of game desired, followed by the
\r
1234 <file name>.</para>
\r
1236 <para>NOTE: A <quote>tournament</quote> game is like a frozen game,
\r
1237 with the following differences. (1) Tournament games always start
\r
1238 from the beginning, while a frozen game can start at any point. (2)
\r
1239 Tournament games require only that the player remember the name or
\r
1240 number of the tournament, while the information about a frozen game
\r
1241 must be kept on a file. Tournament games can be frozen, but then they
\r
1242 behave like regular frozen games.</para>
\r
1244 <para>A point worth noting is that 'FREEZE' does not save the seed for the
\r
1245 random number generator, so that identical actions after restarting
\r
1246 the same frozen game can lead to different results. However,
\r
1247 identical actions after starting a given tournament game always lead
\r
1248 to the same results.</para>
\r
1251 <sect1><title>Request</title>
\r
1255 Shortest abbreviation: REQ
\r
1256 Full command: REQUEST <ITEM>
\r
1259 <para>This command allows you to get any single piece of information
\r
1260 from the <STATUS> command. <ITEM> specifies which
\r
1261 information as follows:</para>
\r
1267 <entry>Information</entry>
\r
1268 <entry>Mnemonic for <item></entry>
\r
1269 <entry>Shortest Abbreviation</entry>
\r
1273 <row><entry>STARDATE</entry> <entry>DATE</entry> <entry>D</entry></row>
\r
1274 <row><entry>CONDITION</entry> <entry>CONDITION</entry> <entry>C</entry></row>
\r
1275 <row><entry>POSITION</entry> <entry>POSITION</entry> <entry>P</entry></row>
\r
1276 <row><entry>LIFE SUPPORT</entry><entry>LSUPPORT</entry> <entry>L</entry></row>
\r
1277 <row><entry>WARP FACTOR</entry> <entry>WARPFACTOR</entry><entry>W</entry></row>
\r
1278 <row><entry>ENERGY</entry> <entry>ENERGY</entry> <entry>E</entry></row>
\r
1279 <row><entry>TORPEDOES</entry> <entry>TORPEDOES</entry> <entry>T</entry></row>
\r
1280 <row><entry>SHIELDS</entry> <entry>SHIELDS</entry> <entry>S</entry></row>
\r
1281 <row><entry>KLINGONS LEFT</entry><entry>KLINGONS</entry> <entry>K</entry></row>
\r
1282 <row><entry>TIME LEFT</entry> <entry>TIME</entry> <entry>TI</entry></row>
\r
1288 <sect1><title>Experimental Death Ray</title>
\r
1291 Mnemonic: DEATHRAY
\r
1295 <para>This command should be used only in those desperate cases where
\r
1296 you have absolutely no alternative. The death ray uses energy to
\r
1297 rearrange matter. Unfortunately, its working principles are not yet
\r
1298 thoroughly understood, and the results are highly
\r
1299 unpredictable.</para>
\r
1301 <para>The only good thing that can result is the destruction of all
\r
1302 enemies in your current quadrant. This will happen about 70% of the
\r
1303 time. Only enemies are destroyed; starbases, stars, and planets are
\r
1304 unaffected.</para>
\r
1306 <para>Constituting the remaining 30% are results varying from bad to
\r
1309 <para>The death ray requires no energy or time, but if you survive, enemies
\r
1310 will hit you.</para>
\r
1312 <para>The Faerie Queene has no death ray.</para>
\r
1314 <para>If the death ray is damaged in its use, it must be totally replaced.
\r
1315 This can only be done at starbase. Because it is a very complex
\r
1316 device, it takes 9.99 stardates at base to replace the death ray.
\r
1317 The death ray cannot be repaired in flight.</para>
\r
1320 <sect1><title>Launch Deep Space Probe</title>
\r
1324 Shortest abbreviation: PR
\r
1325 Full command: PROBE <ARMED> MANUAL <displacement>
\r
1326 PROBE <ARMED> AUTOMATIC <destination>
\r
1329 <para>The Enterprise carries a limited number of Long Range Probes. These
\r
1330 fly to the end of the galaxy and report back a count of the number of
\r
1331 important things found in each quadrant through which it went. The
\r
1332 probe flies at warp 10, and therefore uses time during its flight.
\r
1333 Results are reported immediately via subspace radio and are recorded
\r
1334 in the star chart.</para>
\r
1336 <para>The probe can also be armed with a NOVAMAX warhead. When launched
\r
1337 with the warhead armed, the probe flies the same except as soon as it
\r
1338 reaches the target location, it detonates the warhead in the heart of
\r
1339 a star, causing a supernova and destroying everything in the
\r
1340 quadrant. It then flies no further. There must be a star in the
\r
1341 target quadrant for the NOVAMAX to function. </para>
\r
1343 <para>The probe can fly around objects in a galaxy, but is destroyed if it
\r
1344 enters a quadrant containing a supernova, or if it leaves the galaxy.</para>
\r
1346 <para>The target location is specified in the same manner as the MOVE
\r
1347 command, however for automatic movement, if only one pair of
\r
1348 coordinates are specified they are assumed to be the quadrant and not
\r
1349 the sector in the current quadrant!</para>
\r
1351 <para>The Faerie Queene has no probes.</para>
\r
1354 <sect1><title>Emergency Exit</title>
\r
1358 Shortest abbreviation: E
\r
1361 <para>This command provides a quick way to exit from the game when you
\r
1362 observe a Klingon battle cruiser approaching your terminal. Its
\r
1363 effect is to freeze the game on the file 'EMSAVE.TRK' in your current
\r
1364 directory, erase the screen, and exit.</para>
\r
1366 <para>Of course, you do lose the chance to get a plaque when you use this
\r
1370 <sect1><title>Ask for Help</title>
\r
1374 Full command: HELP <command>
\r
1377 <para>This command reads the appropriate section from the SST.DOC file,
\r
1378 providing the file is in the current directory.</para>
\r
1382 <chapter><title>Miscellaneous Notes</title>
\r
1384 <para>Starbases can be attacked by either commanders or by the
\r
1385 <quote>Super-Commander</quote>. When this happens, you will be
\r
1386 notified by subspace radio, provided it is working. The message will
\r
1387 inform you how long the base under attack can last. Since the
\r
1388 <quote>Super-Commander</quote> is more powerful than an ordinary
\r
1389 commander, he can destroy a base more quickly.</para>
\r
1391 <para>The <quote>Super-Commander</quote> travels around the galaxy at a speed of about
\r
1392 warp 6 or 7. His movement is strictly time based; the more time
\r
1393 passes, the further he can go.</para>
\r
1395 <para>Scattered through the galaxy are certain zones of control,
\r
1396 collectively designated the <quote>Romulan Neutral Zone</quote>. Any
\r
1397 quadrant which contains Romulans without Klingons is part of the
\r
1398 Neutral Zone, except if a base is present. Since Romulans do not show
\r
1399 on either the long-range scan or the star chart, it is easy for you to
\r
1400 stumble into this zone. When you do, if your subspace radio is
\r
1401 working, you will receive a warning message from the Romulan, politely
\r
1402 asking you to leave.</para>
\r
1404 <para>In general, Romulans are a galactic nuisance.</para>
\r
1406 <para>The high-speed shield control is fairly reliable, but it has been
\r
1407 known to malfunction.</para>
\r
1409 <para>You can observe the galactic movements of the
\r
1410 <quote>Super-Commander</quote> on the star chart, provided he is in
\r
1411 territory you have scanned and your subspace radio is working.</para>
\r
1413 <para>Periodically, you will receive intelligence reports from
\r
1414 starfleet command, indicating the current quadrant of the
\r
1415 <quote>Super-Commander</quote>. Your subspace radio must be working,
\r
1418 <para>Each quadrant will contain from 0 to 3 black holes. Torpedoes
\r
1419 entering a black hole disappear. In fact, anything entering a black
\r
1420 hole disappears, permanently. If you can displace an enemy into one,
\r
1421 he is a goner. Black holes do not necessarily remain in a quadrant.
\r
1422 they are transient phenomena.</para>
\r
1424 <para>Commanders will ram your ship, killing themselves and inflicting
\r
1425 heavy damage to you, if they should happen to decide to advance into
\r
1426 your sector.</para>
\r
1428 <para>You can get a list of commands by typing
\r
1429 <quote>COMMANDS</quote>.</para>
\r
1432 <chapter><title>Scoring</title>
\r
1434 <para>Scoring is fairly simple. You get points for good things, and you
\r
1435 lose points for bad things.</para>
\r
1437 <para>You gain—</para>
\r
1440 <listitem><para>10 points for each ordinary Klingon you kill,</para></listitem>
\r
1441 <listitem><para>50 points for each commander you kill,</para></listitem>
\r
1442 <listitem><para>200 points for killing the <quote>Super-Commander</quote>,</para></listitem>
\r
1443 <listitem><para>20 points for each Romulan killed,</para></listitem>
\r
1444 <listitem><para>1 point for each Romulan captured.</para></listitem>
\r
1446 <para>100 times your average Klingon/stardate kill rate. If you lose
\r
1447 the game, your kill rate is based on a minimum of 5 stardates.</para>
\r
1450 <para>You get a bonus if you win the game, based on your rating:</para>
\r
1451 <para>Novice=100, Fair=200, Good=300, Expert=400, Emeritus=500.</para>
\r
1455 <para>You lose—</para>
\r
1458 <listitem><para>200 points if you get yourself killed,</para></listitem>
\r
1459 <listitem><para>100 points for each starbase you destroy,</para></listitem>
\r
1460 <listitem><para>100 points for each starship you lose,</para></listitem>
\r
1461 <listitem><para>45 points for each time you had to call for help,</para></listitem>
\r
1462 <listitem><para>10 points for each planet you destroyed,</para></listitem>
\r
1463 <listitem><para>5 points for each star you destroyed, and</para></listitem>
\r
1464 <listitem><para>1 point for each casualty you incurred.</para></listitem>
\r
1467 <para>In addition to your score, you may also be promoted one grade in rank
\r
1468 if you play well enough. Promotion is based primarily on your
\r
1469 Klingon/stardate kill rate, since this is the best indicator of
\r
1470 whether you are ready to go on to the next higher rating. However,
\r
1471 if you have lost 100 or more points in penalties, the required kill
\r
1472 rate goes up. Normally, the required kill rate is 0.1 * skill *
\r
1473 (skill + 1.0) + 0.1, where skill ranges from 1 for Novice to 5 for
\r
1476 <para>You can be promoted from any level. There is a special
\r
1477 promotion available if you go beyond the <quote>Expert</quote> range.
\r
1478 You can also have a certificate of merit printed with your name, date,
\r
1479 and Klingon kill rate, provided you are promoted from either the
\r
1480 <quote>Expert</quote> or <quote>Emeritus</quote> levels. This
\r
1481 <quote>plaque</quote> requires a 132 column printer. You may need
\r
1482 print the certificate to a file, import it into your word processor,
\r
1483 selecting Courier 8pt font, and then print in <quote>landscape
\r
1484 orientation</quote>.</para>
\r
1486 <para>You should probably start out at the novice level, even if you are
\r
1487 already familiar with one of the other versions of the Star Trek
\r
1488 game—but, of course, the level of game you play is up to you. If
\r
1489 you want to start at the Expert level, go ahead. It's your funeral.
\r
1490 The emeritus game is strictly for masochists.</para>
\r
1493 <chapter><title>Handy Reference Page</title>
\r
1495 <literallayout format='linespecific' class='monospaced'>
\r
1496 ABBREV FULL COMMAND DEVICE USED
\r
1497 ------ ------------ -----------
\r
1498 ABANDON ABANDON shuttle craft
\r
1500 CALL CALL (for help) subspace radio
\r
1501 CO COMPUTER computer
\r
1502 CR CRYSTALS (none)
\r
1504 DEATHRAY DEATHRAY (none)
\r
1505 DESTRUCT DESTRUCT computer
\r
1508 FREEZE FREEZE <FILE NAME> (none)
\r
1509 I IMPULSE <MANUAL> <DISPLACEMENT> impulse engines
\r
1510 IMPULSE AUTOMATIC <DESTINATION> impulse engines and computer
\r
1511 L LRSCAN long-range sensors
\r
1513 M MOVE <MANUAL> <DISPLACEMENT> warp engines
\r
1514 MOVE AUTOMATIC <DESTINATION> warp engines and computer
\r
1515 O ORBIT warp or impulse engines
\r
1516 P PHASERS <TOTAL AMOUNT> phasers and computer
\r
1517 PHASERS AUTOMATIC <TOTAL AMOUNT> phasers, computer, sr sensors
\r
1518 PHASERS MANUAL <AMT1> <AMT2> ... phasers
\r
1519 PHO PHOTONS <NUMBER> <TARGETS> torpedo tubes
\r
1521 PR PROBE <ARMED> <MANUAL> <DISPLACEMENT> probe launcher, radio
\r
1522 PROBE <ARMED> AUTOMATIC <DESTINATION> launcher, radio, computer
\r
1524 REQ REQUEST (none)
\r
1525 R REST <NUMBER OF STARDATES> (none)
\r
1527 S SRSCAN <NO or CHART> short-range sensors
\r
1528 SE SENSORS short-range sensors
\r
1529 SH SHIELDS <UP, DOWN, or TRANSFER> deflector shields
\r
1530 SHU SHUTTLE shuttle craft
\r
1532 T TRANSPORT transporter
\r
1533 W WARP <FACTOR> (none)
\r
1535 L. R. Scan: thousands digit: supernova
\r
1536 hundreds digit: Klingons
\r
1537 tens digit: starbases
\r
1539 period (.): digit not known (star chart only)
\r
1541 Courses are given in manual mode in X - Y displacements; in automatic
\r
1542 mode as destination quadrant and/or sector. Manual mode is default.
\r
1543 Distances are given in quadrants. A distance of one sector is 0.1 quadrant.
\r
1544 Ordinary Klingons have about 400 units of energy, Commanders about
\r
1545 1200. Romulans normally have about 800 units of energy, and the
\r
1546 (GULP) "Super-Commander" has about 1800.
\r
1547 Phaser fire diminishes to about 60 percent at 5 sectors. Up to 1500
\r
1548 units may be fired in a single burst without danger of overheat.
\r
1549 Warp 6 is the fastest safe speed. At higher speeds, engine damage
\r
1550 may occur. At warp 10 you may enter a time warp.
\r
1551 Shields cost 50 units of energy to raise, and double the power
\r
1552 requirements of moving under warp drive. Engaging the high-speed
\r
1553 shield control requires 200 units of energy.
\r
1554 Warp drive requires (distance)*(warp factor cubed) units of energy
\r
1555 to travel at a speed of (warp factor squared)/10 quadrants per stardate.
\r
1556 Impulse engines require 20 units to warm up, plus 100 units per
\r
1557 quadrant. Speed is just under one sector per stardate.
\r
1561 <chapter><title>Game History and Modifications</title>
\r
1563 <sect1><title>Tom Almy's story</title>
\r
1565 <para>Back in (about) 1977 I got a copy of this Super Star Trek game for
\r
1566 the CDC 6600 mainframe computer. Someone had converted it to PDP-11
\r
1567 Fortran but couldn't get it to run because of its size. I modified
\r
1568 the program to use overlays and managed to shoehorn it in on the 56k
\r
1569 byte machine.</para>
\r
1571 <para>I liked the game so much I put some time into fixing bugs, mainly
\r
1572 what could be called continuity errors and loopholes in the game's
\r
1573 logic. We even played a couple tournaments.</para>
\r
1575 <para>In 1979, I lost access to that PDP-11. I did save the source code
\r
1576 listing. In 1995, missing that old friend, I started converting the
\r
1577 program into portable ANSI C. It's been slow, tedious work that took
\r
1578 over a year to accomplish.</para>
\r
1580 <para>In early 1997, I got the bright idea to look for references to
\r
1581 <quote>Super Star Trek</quote> on the World Wide Web. There weren't
\r
1582 many hits, but there was one that came up with 1979 Fortran sources!
\r
1583 This version had a few additional features that mine didn't have,
\r
1584 however mine had some feature it didn't have. So I merged its features
\r
1585 that I liked. I also took a peek at the DECUS version (a port, less
\r
1586 sources, to the PDP-10), and some other variations.</para>
\r
1588 <para>Modifications I made:</para>
\r
1590 <para>Compared to original version, I've changed the
\r
1591 <quote>help</quote> command to <quote>call</quote> and the
\r
1592 <quote>terminate</quote> command to <quote>quit</quote> to better
\r
1593 match user expectations. The DECUS version apparently made those
\r
1594 changes as well as changing <quote>freeze</quote> to
\r
1595 <quote>save</quote>. However I like <quote>freeze</quote>.</para>
\r
1597 <para>I added EMEXIT from the 1979 version.</para>
\r
1599 <para>That later version also mentions srscan and lrscan working when
\r
1600 docked (using the starbase's scanners), so I made some changes here
\r
1601 to do this (and indicating that fact to the player), and then
\r
1602 realized the base would have a subspace radio as well — doing a
\r
1603 Chart when docked updates the star chart, and all radio reports will
\r
1604 be heard. The Dock command will also give a report if a base is under
\r
1607 <para>It also had some added logic to spread the initial positioning of
\r
1608 bases. That made sense to add because most people abort games with
\r
1609 bad base placement.</para>
\r
1611 <para>The experimental deathray originally had only a 5% chance of success,
\r
1612 but could be used repeatedly. I guess after a couple years of use, it
\r
1613 was less <quote>experimental</quote> because the 1979 version had a 70% success
\r
1614 rate. However it was prone to breaking after use. I upgraded the
\r
1615 deathray, but kept the original set of failure modes (great humor!).</para>
\r
1617 <para>I put in the Tholian Web code from the 1979 version.</para>
\r
1619 <para>I added code so that Romulans and regular Klingons could move in
\r
1620 advanced games. I re-enabled the code which allows enemy ships to
\r
1621 ram the Enterprise; it had never worked right. The 1979 version
\r
1622 seems to have it all fixed up, but I'm still not overly happy with
\r
1623 the algorithm.</para>
\r
1625 <para>The DECUS version had a Deep Space Probe. Looked like a good idea
\r
1626 so I implemented it based on its description.</para>
\r
1629 <sect1><title>Stas Sergeev's story</title>
\r
1631 <para>I started from an older Tom Almy version and added features I had
\r
1632 seen in mainframe variants of the game, I wrote a screen-oriented
\r
1633 interface for it based on the curses library.</para>
\r
1637 <para>The Space Thingy can be shoved, if you ram it, and can fire back if
\r
1638 fired upon.</para>
\r
1641 <para>The Tholian can be hit with phasers.</para>
\r
1644 <para>When you are docked, base covers you with an almost invincible shields
\r
1645 (a commander can still ram you, or a Romulan can destroy the base,
\r
1646 or a SCom can even succeed with direct attack IIRC, but this rarely
\r
1650 <para>SCom can't escape from you if no more enemies remain (without this,
\r
1651 chasing SCom can take an eternity).</para>
\r
1654 <para>Probe target you enter is now the destination quadrant. Before I don't
\r
1655 remember what it was, but it was something I had difficulty using)</para>
\r
1658 <para>Secret password is now autogenerated.</para>
\r
1661 <para>Victory plaque is adjusted for A4 paper rather than 132-column greenbar
\r
1665 <para>Phasers now tells you how much energy needed, but only if the computer
\r
1669 <para>Planets are auto-scanned when you enter the quadrant.</para>
\r
1672 <para>Mining or using crystals in presense of enemy now yields an attack.
\r
1673 There are other minor adjustments to what yields an attack
\r
1674 and what does not.</para>
\r
1677 <para>Ramming a black hole is no longer instant death. There is a
\r
1678 chance you might get timewarped instead.</para>
\r
1681 <para>"freeze" command reverts to "save", most people will understand this
\r
1682 better anyway.</para>
\r
1685 <para>Screen-oriented interface, with sensor scans always up.</para>
\r
1690 <sect1><title>Eric Raymond's story</title>
\r
1692 <para>I played the FORTRAN version of this game in the mid-1970s on a
\r
1693 DEC minicomputer. In the late 1980s Dave Matuszek and I became
\r
1694 friends; I was vaguely aware that he had had something to do with the
\r
1695 original Star Trek game. In October 2004, sitting in Dave's living
\r
1696 room, we got to talking about the game and I realized it would make a
\r
1697 great exhibit for the <ulink
\r
1698 url='http://www.catb.org/retro/'>Retrocomputing Museum</ulink>.</para>
\r
1700 <para>A few quick web searches later we found Tom Almy's page. We
\r
1701 downloaded his code and Dave verified that that it was a direct
\r
1702 descendent of UT Super Star Trek — even though it had been translated
\r
1703 to C, he was able to recognize names and techniques from the FORTRAN
\r
1706 <para>Thus, this game is a cousin of Eric Allman's BSD Trek game, which is
\r
1707 also derived from UT Super Star Trek. However, this one has had a lot
\r
1708 more stuff folded into it over the years — deep space probes,
\r
1709 dilithium mining, the Tholian Web, and so forth.</para>
\r
1711 <para>One signature trait of this group of variants is that the sectors are
\r
1712 10x10 rather than the 8x8 in Mike Mayfield's 1972 original and its
\r
1713 BASIC descendants) Also, you set courses and firing directions with
\r
1714 rectangular rather than polar coordinates. It also preserves the
\r
1715 original numbered quadrants rather than the astronomically-named
\r
1716 quadrants introduced into many BASIC versions.</para>
\r
1718 <para>This game is now an open-source project; see the <ulink
\r
1719 url='http://developer.berlios.de/projects/sst/'>project
\r
1720 site</ulink>.</para>
\r
1722 <para>After I launched the Berlios project, Stas Sergeev contacted me
\r
1723 me. We worked together to merge in his changes.</para>
\r
1725 <para>Modifications I've made:</para>
\r
1729 I converted the flat-text SST.DOC file to XML-Docbook so it can be
\r
1730 webbed. (That's what you're reading now.)
\r
1731 </para></listitem>
\r
1733 The command-help code needed a rewrite because the flat-text form of
\r
1734 the documentation is now generated from XML and doesn't have the
\r
1735 easily recognizable section delimiters it used to. I wrote a script
\r
1736 to filter that flat-text form into an sst.doc that's easy to parse for
\r
1737 command descriptions, and changed some logic in sst.c to match.
\r
1738 </para></listitem>
\r
1740 I've cleaned up a lot of grubby FORTRANisms in the code internals --
\r
1741 used sizeof(), replaced magic numeric constants with #defines,
\r
1742 that sort of thing.
\r
1743 </para></listitem>
\r
1745 I fixed a surprising number of typos in the code and documentation.
\r
1746 </para></listitem>
\r
1748 All the game state now lives in one big structure that can be
\r
1749 written to and read from disk as one blob. The write gives it an
\r
1750 an identifiable magic number and the thaw logic checks for same.
\r
1751 </para></listitem>
\r
1753 I made the internal pager work, nd in the process got rid of a number
\r
1754 of platform dependencies in the code.
\r
1755 </para></listitem>
\r
1757 The HELP/CALL/SOS command is now MAYDAY. SOS and CALL are still accepted.
\r
1758 </para></listitem>
\r
1761 <para>Here are some good pages on the history of Star Trek games:</para>
\r
1765 <ulink url='http://www.dunnington.u-net.com/public/startrek/'>http://www.dunnington.u-net.com/public/startrek/</ulink>
\r
1766 </para></listitem>
\r
1768 <ulink url='http://www3.sympatico.ca/maury/games/space/star_trek.html'>http://www3.sympatico.ca/maury/games/space/star_trek.html</ulink>
\r
1769 </para></listitem>
\r
1771 <ulink url='http://www.cactus.org/%7Enystrom/startrek.html'>http://www.cactus.org/%7Enystrom/startrek.html</ulink>
\r
1772 </para></listitem>
\r
1776 <sect1><title>Authors' Acknowledgments</title>
\r
1778 <para>These are the original acknowledgments by Dave Matuszek and Paul
\r
1781 <para>The authors would like to thank Professor Michael Duggan for his
\r
1782 encouragement and administrative assistance with the development of
\r
1783 the Star Trek game, without which it might never have been completed.</para>
\r
1785 <para>Much credit is due to Patrick McGehearty and Rich Cohen, who assisted
\r
1786 with the original design of the game and contributed greatly to its
\r
1787 conceptual development.</para>
\r
1789 <para>Thanks are also due to Carl Strange, Hardy Tichenor and Steven Bruell
\r
1790 for their assistance with certain coding problems.</para>
\r
1792 <para>This game was inspired by and rather loosely based on an earlier
\r
1793 game, programmed in the BASIC language, by Jim Korp and Grady Hicks.
\r
1794 It is the authors' understanding that the BASIC game was in turn
\r
1795 derived from a still earlier version in use at Penn State University.</para>
\r
1798 <sect1><title>References</title>
\r
1801 <listitem><para><citetitle>Star Trek</citetitle> (the original television
\r
1802 series), produced and directed by Gene Rodenberry.</para></listitem>
\r
1804 <listitem><para><citetitle>Star Trek</citetitle> (the animated
\r
1805 television series), produced by Gene Rodenberry and directed by Hal
\r
1806 Sutherland. Also excellent, and not just kiddie fare. If you enjoyed
\r
1807 the original series you should enjoy this one (unless you have some
\r
1808 sort of a hangup about watching cartoons).</para></listitem>
\r
1810 <listitem><para><citetitle>The Making of Star Trek</citetitle>, by
\r
1811 Steven E. Whitfield and Gene Rodenberry. The best and most complete
\r
1812 readily available book about Star Trek. (Ballantine
\r
1813 Books)</para></listitem>
\r
1815 <listitem><para><citetitle>The World of Star Trek</citetitle>, by
\r
1816 David Gerrold. Similiar in scope to the above book.
\r
1817 (Bantam)</para></listitem>
\r
1819 <listitem><para><citetitle>The Star Trek Guide</citetitle>, third revision 4/17/67, by Gene
\r
1820 Roddenberry. The original writer's guide for the television
\r
1821 series, but less comprehensive than (3) above.
\r
1822 (Norway Productions)</para></listitem>
\r
1824 <listitem><para><citetitle>The Trouble With Tribbles</citetitle>, by
\r
1825 David Gerrold. Includes the complete script of this popular show.
\r
1826 (Ballantine Books)</para></listitem>
\r
1828 <listitem><para><citetitle>Star Trek</citetitle>, <citetitle>Star Trek
\r
1829 2</citetitle>, ..., <citetitle>Star Trek 9</citetitle>, by James
\r
1830 Blish. The original shows in short story form.
\r
1831 (Bantam)</para></listitem>
\r
1833 <listitem><para><citetitle>Spock Must Die</citetitle>, by James Blish.
\r
1834 An original novel, but rather similar to the show <citetitle>The Enemy
\r
1835 Within</citetitle>. (Bantam)</para></listitem>
\r
1837 <listitem><para>Model kits of the Enterprise and a <quote>Klingon
\r
1838 Battle-Cruiser</quote> by AMT Corporation are available at most hobby
\r
1839 shops.</para></listitem>
\r
projects / super-star-trek.git / blob