1
0
mirror of https://github.com/openbsd/src.git synced 2025-01-10 06:47:55 -08:00

forgot to remove mention of deleted dump/restart.

also delete ancient todo file:
Frankly,
I am getting pretty sick of playing this game.
Hence,
the version which you get may have several bugs
This commit is contained in:
tedu 2017-05-26 19:48:28 +00:00
parent 88afa33fb1
commit 9283ef5c3b
4 changed files with 4 additions and 185 deletions

View File

@ -1,154 +0,0 @@
.\" $OpenBSD: read_me.nr,v 1.4 2001/01/08 05:08:43 pjanzen Exp $
.\" $NetBSD: read_me.nr,v 1.2 1995/04/22 10:59:44 cgd Exp $
.de @h
'sp 4
'tl 'TREK SETUP INSTRUCTIONS''%'
'sp 2
.ns
..
.de @f
'bp
..
.wh 0 @h
.wh -6 @f
.de pp
.sp
.ne 2
.ti +5
..
.de s1
.sp 2
.nr S1 +1
.nr S2 0
.ne 5
.in 4
.ti 0
\\n(S1.\ \ \c
..
.de s2
.sp 1
.nr S2 +1
.ne 3
.in 8
.ti 4
\\n(S2.\ \ \c
..
.br
.ce
TREK SETUP INSTRUCTIONS
.sp 2
.pp
This document describes all sorts of nifty things
you should know
before you start to muck around
with the trek source code.
Please read them carefully.
.s1
MAINTENANCE
.pp
There is a compilation option xTRACE which must be set for any
trace information to be generated
(the -t option must also be set on the command line).
It is no longer defined by default.
.s1
DISCLAIMERS
.s2
Frankly,
I am getting pretty sick of playing this game.
Hence,
the version which you get may have several bugs
in it;
I freely admit
that it is probably buggier
than some previous versions.
Sorry about that.
.s2
Along with being buggy,
the game never had quite everything implemented
that was originally intended.
If you see things that look weird,
that may be why.
There are even some features which I have taken out
(like ghost starsystems)
upon deciding that I didn't have the energy
to implement them correctly.
.s1
REQUESTS
.pp
There are several things that I would like to ask of anyone
who does work on the source code.
.s2
Please let me know of any bugs which you find
in the code,
and any fixes which you may have.
Other copies will probably be going out to other people later,
and it would be nice if those copies where less buggy.
Also,
I would be interested in hearing about any
enhancements of the game which you might install.
.s2
Please note that I have a distinct coding style.
I feel that it is cleaner
and easier to read than a more
casual style.
If possible,
please stick to it,
especially if you end up sending tapes back to me.
This goes along with my whole belief in clean code:
I ask you to please avoid obscure code
whenever possible.
If you throw some in,
please don't let me see it.
It just depresses me.
.s2
Unfortunately,
the game is huge.
There are many neat things
which could go in,
if there were only enough space.
However,
I have specifically not gone to separated I/D
space.
The main reason is that I would like future versions
of the game
to be 11/40 compatible.
.s1
SUGGESTIONS FOR THE FUTURE
.pp
If you happen to have more energy than I do,
you may want to examine the following areas.
These are things that I may get to,
but don't hold your breath.
.s2
The routine "capture" is quite unclean.
First, it should have a manner of selecting Klingons
other than random,
either selecting the most likely
or asking the captain (probably best).
It should either be fully implemented,
which includes adding a "board" routine
(half written,
on some tapes as board.x)
which sends a boarding party to forcefully
take over the Klingon,
or it should go out completely,
which is probably what I will end up doing.
When this happens,
the transporter will go completely.
It seems that the space may be better used
for something which more directly enhances the game.
.sp 3
.in 0
Well, that's about it.
To get hold of me,
write to:
.nf
.sp
Eric P Allman
Electronics Research Laboratory
University of California
Berkeley, California 94720
.fi
Happy trekking!!
.pp

View File

@ -1,10 +0,0 @@
* tractor beams
* power distribution
* Romulans:
- plasma bolts
- neutral zone
- cloaking device
* the thing
* ion storms
* torpedoes with time delays
* Put removal from event list into killk

View File

@ -1,4 +1,4 @@
.\" $OpenBSD: trek.me,v 1.6 2004/08/21 23:09:12 jmc Exp $
.\" $OpenBSD: trek.me,v 1.7 2017/05/26 19:48:28 tedu Exp $
.\" $NetBSD: trek.me,v 1.2 1995/04/22 10:59:49 cgd Exp $
.\"
.\" Copyright (c) 1980, 1993
@ -160,9 +160,7 @@ from the shell.
The game will ask you what length game
you would like.
Valid responses are "short", "medium", and "long".
You may also type "restart",
which restarts a previously saved game, \*f./trek.dump\fR, if
it exists. Ideally,
Ideally,
the length of the game does not affect the difficulty,
but currently the shorter games tend to be harder than the longer ones.
.pp
@ -867,14 +865,6 @@ any Klingons
(and stars,
and starbases)
left in your quadrant.
.bl "Save the Game"
Mnemonic: dump
Shortest Abbreviation: dump
.FF
.pp
Saves the current game in \*f./trek.dump\fR
if possible. Game play continues after
the dump.
.bl "Terminate the Game"
Mnemonic: terminate
Shortest Abbreviation: terminate
@ -929,7 +919,6 @@ Command Requires Consumes
\*fda\fRmages - -
\*fdestruct\fR computer -
\*fdo\fRck - -
\*fdump\fR - -
\*fhelp\fR subspace radio -
\*fi\fRmpulse course distance impulse engines time, energy
computer, SINS

View File

@ -1,4 +1,4 @@
.\" $OpenBSD: trek.6,v 1.15 2011/12/28 22:06:36 schwarze Exp $
.\" $OpenBSD: trek.6,v 1.16 2017/05/26 19:48:28 tedu Exp $
.\" $NetBSD: trek.6,v 1.4 1995/04/22 10:59:35 cgd Exp $
.\"
.\" Copyright (c) 1980, 1993
@ -30,7 +30,7 @@
.\"
.\" @(#)trek.6 8.2 (Berkeley) 12/30/93
.\"
.Dd $Mdocdate: December 28 2011 $
.Dd $Mdocdate: May 26 2017 $
.Dt TREK 6
.Os
.Sh NAME
@ -52,9 +52,6 @@ Valid responses are
.Dq medium ,
and
.Dq long .
You may also type
.Dq restart ,
which restarts a previously saved game.
You will then be prompted for the skill, to which you must respond
.Dq novice ,
.Dq fair ,
@ -85,9 +82,6 @@ the game will tell you what it expects if you just type in a question mark.
.It
.Ic do Ns ck
.It
.Ic dump No (save game to
.Pa ./trek.dump )
.It
.Ic help
.It
.Ic i Ns mpulse course distance