| 1 |
.\" Automatically generated from atc/atc.6.in. Do not edit. |
| 2 |
.\" $NetBSD: atc.6,v 1.21 2004/01/01 16:31:37 wiz Exp $ |
| 3 |
.\" |
| 4 |
.\" Copyright (c) 1990, 1993 |
| 5 |
.\" The Regents of the University of California. All rights reserved. |
| 6 |
.\" |
| 7 |
.\" This code is derived from software contributed to Berkeley by |
| 8 |
.\" Ed James. |
| 9 |
.\" |
| 10 |
.\" Redistribution and use in source and binary forms, with or without |
| 11 |
.\" modification, are permitted provided that the following conditions |
| 12 |
.\" are met: |
| 13 |
.\" 1. Redistributions of source code must retain the above copyright |
| 14 |
.\" notice, this list of conditions and the following disclaimer. |
| 15 |
.\" 2. Redistributions in binary form must reproduce the above copyright |
| 16 |
.\" notice, this list of conditions and the following disclaimer in the |
| 17 |
.\" documentation and/or other materials provided with the distribution. |
| 18 |
.\" 3. Neither the name of the University nor the names of its contributors |
| 19 |
.\" may be used to endorse or promote products derived from this software |
| 20 |
.\" without specific prior written permission. |
| 21 |
.\" |
| 22 |
.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND |
| 23 |
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE |
| 24 |
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE |
| 25 |
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE |
| 26 |
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL |
| 27 |
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS |
| 28 |
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) |
| 29 |
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT |
| 30 |
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY |
| 31 |
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF |
| 32 |
.\" SUCH DAMAGE. |
| 33 |
.\" |
| 34 |
.\" @(#)atc.6 8.1 (Berkeley) 5/31/93 |
| 35 |
.\" |
| 36 |
.\" Copyright (c) 1986 Ed James. All rights reserved. |
| 37 |
.\" |
| 38 |
.Dd January 1, 2004 |
| 39 |
.Dt ATC 6 |
| 40 |
.Os |
| 41 |
.Sh NAME |
| 42 |
.Nm atc |
| 43 |
.Nd air traffic controller game |
| 44 |
.Sh SYNOPSIS |
| 45 |
.Nm atc |
| 46 |
.Op Fl u?lstp |
| 47 |
.Op Fl gf Ar "game name" |
| 48 |
.Op Fl r Ar "random seed" |
| 49 |
.Sh DESCRIPTION |
| 50 |
.Nm |
| 51 |
lets you try your hand at the nerve wracking duties of the air traffic |
| 52 |
controller without endangering the lives of millions of travelers each year. |
| 53 |
Your responsibilities require you to direct the flight of jets |
| 54 |
and prop planes into and out of the flight arena and airports. |
| 55 |
The speed (update time) and frequency of the planes depend on the |
| 56 |
difficulty of the chosen arena. |
| 57 |
.Sh OPTIONS |
| 58 |
.Bl -tag -width flag |
| 59 |
.It Fl u |
| 60 |
Print the usage line and exit. |
| 61 |
.It Fl \&? |
| 62 |
Same as |
| 63 |
.Fl u . |
| 64 |
.It Fl l |
| 65 |
Print a list of available games and exit. |
| 66 |
The first game name printed is the default game. |
| 67 |
.It Fl s |
| 68 |
Print the score list (formerly the Top Ten list). |
| 69 |
.It Fl t |
| 70 |
Same as |
| 71 |
.Fl s . |
| 72 |
.It Fl p |
| 73 |
Print the path to the special directory where |
| 74 |
.Nm |
| 75 |
expects to find its private files. |
| 76 |
This is used during the installation of the program. |
| 77 |
.It Fl g Ar game |
| 78 |
Play the named game. |
| 79 |
If the game listed is not one of the ones printed from the |
| 80 |
.Fl l |
| 81 |
option, the default game is played. |
| 82 |
.It Fl f Ar game |
| 83 |
Same as |
| 84 |
.Fl g . |
| 85 |
.It Fl r Ar seed |
| 86 |
Set the random seed. |
| 87 |
The purpose of this flag is questionable. |
| 88 |
.El |
| 89 |
.Sh GOALS |
| 90 |
Your goal in |
| 91 |
.Nm |
| 92 |
is to keep the game going as long as possible. |
| 93 |
There is no winning state, except to beat the times of other players. |
| 94 |
You will need to: launch planes at airports (by instructing them to |
| 95 |
increase their altitude); land planes at airports (by instructing them to |
| 96 |
go to altitude zero when exactly over the airport); and maneuver planes |
| 97 |
out of exit points. |
| 98 |
.Pp |
| 99 |
Several things will cause the end of the game. |
| 100 |
Each plane has a destination (see information area), and |
| 101 |
sending a plane to the wrong destination is an error. |
| 102 |
Planes can run out of fuel, or can collide. |
| 103 |
Collision is defined as adjacency in all three dimensions. |
| 104 |
A plane leaving the arena |
| 105 |
in any other way than through its destination exit is an error as well. |
| 106 |
.Pp |
| 107 |
Scores are sorted in order of the number of planes safe. |
| 108 |
The other statistics are provided merely for fun. |
| 109 |
There is no penalty for |
| 110 |
taking longer than another player (except in the case of ties). |
| 111 |
.Pp |
| 112 |
Suspending a game is not permitted. |
| 113 |
If you get a talk message, tough. |
| 114 |
When was the last time an Air Traffic Controller got called away to the phone? |
| 115 |
.Sh THE DISPLAY |
| 116 |
Depending on the terminal you run |
| 117 |
.Nm |
| 118 |
on, the screen will be divided into 4 areas. |
| 119 |
It should be stressed that the terminal driver portion of the |
| 120 |
game was designed to be reconfigurable, so the display format can vary |
| 121 |
depending on the version you are playing. |
| 122 |
The descriptions here are based on the ascii version of the game. |
| 123 |
The game rules and input format, however, should remain consistent. |
| 124 |
Control-L redraws the screen, should it become muddled. |
| 125 |
.Ss RADAR |
| 126 |
The first screen area is the radar display, showing the relative locations |
| 127 |
of the planes, airports, standard entry/exit points, radar |
| 128 |
beacons, and ``lines'' which simply serve to aid you in guiding |
| 129 |
the planes. |
| 130 |
.Pp |
| 131 |
Planes are shown as a single letter with an altitude. |
| 132 |
If the numerical altitude is a single digit, then it represents |
| 133 |
thousands of feet. |
| 134 |
Some distinction is made between the prop planes and the jets. |
| 135 |
On ascii terminals, prop planes are |
| 136 |
represented by a upper case letter, jets by a lower case letter. |
| 137 |
.Pp |
| 138 |
Airports are shown as a number and some indication of the direction |
| 139 |
planes must be going to land at the airport. |
| 140 |
On ascii terminals, this is one of `^', `\*[Gt]', `\*[Lt]', and `v', to indicate |
| 141 |
north (0 degrees), east (90), west (270) and south (180), respectively. |
| 142 |
The planes will also take off in this direction. |
| 143 |
.Pp |
| 144 |
Beacons are represented as circles or asterisks and a number. |
| 145 |
Their purpose is to offer a place of easy reference to the plane pilots. |
| 146 |
See |
| 147 |
.Sx THE DELAY COMMAND |
| 148 |
section below. |
| 149 |
.Pp |
| 150 |
Entry/exit points are displayed as numbers along the border of the |
| 151 |
radar screen. |
| 152 |
Planes will enter the arena from these points without warning. |
| 153 |
These points have a direction associated with them, and |
| 154 |
planes will always enter the arena from this direction. |
| 155 |
On the ascii version of |
| 156 |
.Nm , |
| 157 |
this direction is not displayed. |
| 158 |
It will become apparent what this direction is as the game progresses. |
| 159 |
.Pp |
| 160 |
Incoming planes will always enter at the same altitude: 7000 feet. |
| 161 |
For a plane to successfully depart through an entry/exit point, |
| 162 |
it must be flying at 9000 feet. |
| 163 |
It is not necessary for the planes to be flying in any particular |
| 164 |
direction when they leave the arena (yet). |
| 165 |
.Ss INFORMATION AREA |
| 166 |
The second area of the display is the information area, which lists |
| 167 |
the time (number of updates since start), and the number of planes you |
| 168 |
have directed safely out of the arena. |
| 169 |
Below this is a list of planes currently in the air, followed by a |
| 170 |
blank line, and then a list of planes on the ground (at airports). |
| 171 |
Each line lists the plane name and its current altitude, |
| 172 |
an optional asterisk indicating low fuel, the plane's destination, |
| 173 |
and the plane's current command. |
| 174 |
Changing altitude is not considered |
| 175 |
to be a command and is therefore not displayed. |
| 176 |
The following are some possible information lines: |
| 177 |
.Pp |
| 178 |
.Bd -literal -offset indent |
| 179 |
B4*A0: Circle @ b1 |
| 180 |
g7 E4: 225 |
| 181 |
.Ed |
| 182 |
.Pp |
| 183 |
The first example shows a prop plane named `B' that is flying at 4000 feet. |
| 184 |
It is low on fuel (note the `*'). |
| 185 |
Its destination is Airport #0. |
| 186 |
The next command it expects to do is circle when it reaches Beacon #1. |
| 187 |
The second example shows a jet named `g' at 7000 feet, destined for |
| 188 |
Exit #4. |
| 189 |
It is just now executing a turn to 225 degrees (South-West). |
| 190 |
.Ss INPUT AREA |
| 191 |
The third area of the display is the input area. |
| 192 |
It is here that your input is reflected. |
| 193 |
See the |
| 194 |
.Sx INPUT |
| 195 |
heading of this manual for more details. |
| 196 |
.Ss AUTHOR AREA |
| 197 |
This area is used simply to give credit where credit is due. :-) |
| 198 |
.Sh INPUT |
| 199 |
A command completion interface is built into the game. |
| 200 |
At any time, typing `?' will list possible input characters. |
| 201 |
Typing a backspace (your erase character) backs up, erasing the last part |
| 202 |
of the command. |
| 203 |
When a command is complete, a return enters it, and |
| 204 |
any semantic checking is done at that time. |
| 205 |
If no errors are detected, the command is sent to the appropriate plane. |
| 206 |
If an error is discovered |
| 207 |
during the check, the offending statement will be underscored and a |
| 208 |
(hopefully) descriptive message will be printed under it. |
| 209 |
.Pp |
| 210 |
The command syntax is broken into two parts: |
| 211 |
.Em Immediate Only |
| 212 |
and |
| 213 |
.Em Delayable |
| 214 |
commands. |
| 215 |
.Em Immediate Only |
| 216 |
commands happen on the next update. |
| 217 |
.Em Delayable |
| 218 |
commands also happen on the next update unless they |
| 219 |
are followed by an optional predicate called the |
| 220 |
.Em Delay |
| 221 |
command. |
| 222 |
.Pp |
| 223 |
In the following tables, the syntax |
| 224 |
.Em [0\-9] |
| 225 |
means any single digit, and |
| 226 |
.Aq Em dir |
| 227 |
refers to a direction, given by the keys around the `s' key: ``wedcxzaq''. |
| 228 |
In absolute references, `q' refers to North-West or 315 degrees, and `w' |
| 229 |
refers to North, or 0 degrees. |
| 230 |
In relative references, `q' refers to \-45 degrees or 45 degrees left, and `w' |
| 231 |
refers to 0 degrees, or no change in direction. |
| 232 |
.Pp |
| 233 |
All commands start with a plane letter. |
| 234 |
This indicates the recipient of the command. |
| 235 |
Case is ignored. |
| 236 |
.Ss IMMEDIATE ONLY COMMANDS |
| 237 |
.Bl -tag -width "aaaa" |
| 238 |
.It "a [ cd+- ]" Em number |
| 239 |
Altitude: Change a plane's altitude, possibly requesting takeoff. |
| 240 |
`+' and `-' are the same as `c' and `d'. |
| 241 |
.Bl -tag -width "aaaaaaaaaa" -compact |
| 242 |
.It a Em number |
| 243 |
Climb or descend to the given altitude (in thousands of feet). |
| 244 |
.It ac Em number |
| 245 |
Climb: relative altitude change. |
| 246 |
.It ad Em number |
| 247 |
Descend: relative altitude change. |
| 248 |
.El |
| 249 |
.It m |
| 250 |
Mark: Display in highlighted mode. |
| 251 |
Plane and command information is displayed normally. |
| 252 |
.It i |
| 253 |
Ignore: Do not display highlighted. |
| 254 |
Command is displayed as a line of dashes if there is no command. |
| 255 |
.It u |
| 256 |
Unmark: Same as ignore, but if a delayed command is processed, |
| 257 |
the plane will become marked. |
| 258 |
This is useful if you want to forget about a plane during part, |
| 259 |
but not all, of its journey. |
| 260 |
.El |
| 261 |
.Ss DELAYABLE COMMANDS |
| 262 |
.Bl -tag -width "aaaa" |
| 263 |
.It "c [ lr ]" |
| 264 |
Circle: Have the plane circle. |
| 265 |
.Bl -tag -width "aaaaaaaaaa" -compact |
| 266 |
.It cl |
| 267 |
Left: Circle counterclockwise. |
| 268 |
.It cr |
| 269 |
Right: Circle clockwise (default). |
| 270 |
.El |
| 271 |
.It "t [ l-r+LR ] [ dir ] or tt [ abe* ]" Em number |
| 272 |
Turn: Change direction. |
| 273 |
.Bl -tag -width "aaaaaaaaaa" -compact |
| 274 |
.It "t\*[Lt]dir\*[Gt]" |
| 275 |
Turn to direction: Turn to the absolute compass heading given. |
| 276 |
The shortest turn will be taken. |
| 277 |
.It "tl [ dir ]" |
| 278 |
Left: Turn counterclockwise: 45 degrees by default, or the amount |
| 279 |
specified in |
| 280 |
.Aq dir |
| 281 |
(not |
| 282 |
.Em to |
| 283 |
.Aq dir . ) |
| 284 |
`w' (0 degrees) is no turn. |
| 285 |
`e' is 45 degrees; `q' gives \-45 degrees counterclockwise, that is, |
| 286 |
45 degrees clockwise. |
| 287 |
.It "t- [ dir ]" |
| 288 |
Same as left. |
| 289 |
.It "tr [ dir ]" |
| 290 |
Right: Turn clockwise, 45 degrees by default, or the amount specified in |
| 291 |
.Aq dir . |
| 292 |
.It "t+ [ dir ]" |
| 293 |
Same as right. |
| 294 |
.It tL |
| 295 |
Hard left: Turn counterclockwise 90 degrees. |
| 296 |
.It tR |
| 297 |
Hard right: Turn clockwise 90 degrees. |
| 298 |
.It "tt [abe*]" |
| 299 |
Towards: Turn towards a beacon, airport or exit. |
| 300 |
The turn is just an estimate. |
| 301 |
.It "tta" Em number |
| 302 |
Turn towards the given airport. |
| 303 |
.It "ttb" Em number |
| 304 |
Turn towards the specified beacon. |
| 305 |
.It "tte" Em number |
| 306 |
Turn towards an exit. |
| 307 |
.It "tt*" Em number |
| 308 |
Same as ttb. |
| 309 |
.El |
| 310 |
.El |
| 311 |
.Ss THE DELAY COMMAND |
| 312 |
The |
| 313 |
.Em Delay |
| 314 |
(a/@) command may be appended to any |
| 315 |
.Em Delayable |
| 316 |
command. |
| 317 |
It allows the controller to instruct a plane to do an action when the |
| 318 |
plane reaches a particular beacon (or other objects in future versions). |
| 319 |
.Bl -tag -width "aaaa" |
| 320 |
.It ab Em number |
| 321 |
Do the delayable command when the plane reaches the specified beacon. |
| 322 |
The `b' for ``beacon'' is redundant to allow for expansion. |
| 323 |
`@' can be used instead of `a'. |
| 324 |
.El |
| 325 |
.Ss MARKING, UNMARKING AND IGNORING |
| 326 |
Planes are |
| 327 |
.Em marked |
| 328 |
by default when they enter the arena. |
| 329 |
This means they are displayed in highlighted mode on the radar display. |
| 330 |
A plane may also be either |
| 331 |
.Em unmarked |
| 332 |
or |
| 333 |
.Em ignored . |
| 334 |
An |
| 335 |
.Em ignored |
| 336 |
plane is drawn in unhighlighted mode, and a line of dashes is displayed in |
| 337 |
the command field of the information area. |
| 338 |
The plane will remain this way until a mark command has been issued. |
| 339 |
Any other command will be issued, but the command line will return to a |
| 340 |
line of dashes when the command is completed. |
| 341 |
.Pp |
| 342 |
An |
| 343 |
.Em unmarked |
| 344 |
plane is treated the same as an |
| 345 |
.Em ignored |
| 346 |
plane, except that it will automatically switch to |
| 347 |
.Em marked |
| 348 |
status when a delayed command has been processed. |
| 349 |
This is useful if you want to forget about a plane for a while, but its |
| 350 |
flight path has not yet been completely set. |
| 351 |
.Pp |
| 352 |
As with all of the commands, marking, unmarking and ignoring will take effect |
| 353 |
at the beginning of the next update. |
| 354 |
Do not be surprised if the plane does |
| 355 |
not immediately switch to unhighlighted mode. |
| 356 |
.Ss EXAMPLES |
| 357 |
.Bl -tag -width gtte4ab2 -offset indent |
| 358 |
.It atlab1 |
| 359 |
Plane A: turn left at beacon #1 |
| 360 |
.It cc |
| 361 |
Plane C: circle |
| 362 |
.It gtte4ab2 |
| 363 |
Plane G: turn towards exit #4 at beacon #2 |
| 364 |
.It ma+2 |
| 365 |
Plane M: altitude: climb 2000 feet |
| 366 |
.It stq |
| 367 |
Plane S: turn to 315 |
| 368 |
.It xi |
| 369 |
Plane X: ignore |
| 370 |
.El |
| 371 |
.Sh OTHER INFORMATION |
| 372 |
.Bl -bullet |
| 373 |
.It |
| 374 |
Jets move every update; prop planes move every other update. |
| 375 |
.It |
| 376 |
All planes turn at most 90 degrees per movement. |
| 377 |
.It |
| 378 |
Planes enter at 7000 feet and leave at 9000 feet. |
| 379 |
.It |
| 380 |
Planes flying at an altitude of 0 crash if they are not over an airport. |
| 381 |
.It |
| 382 |
Planes waiting at airports can only be told to take off (climb in altitude). |
| 383 |
.It |
| 384 |
Pressing return (that is, entering an empty command) will perform the |
| 385 |
next update immediately. |
| 386 |
This allows you to ``fast forward'' |
| 387 |
the game clock if nothing interesting is happening. |
| 388 |
.El |
| 389 |
.Sh NEW GAMES |
| 390 |
The |
| 391 |
.Pa Game_List |
| 392 |
file lists the currently available play fields. |
| 393 |
New field description file names must be placed in this file to be playable. |
| 394 |
If a player specifies a game not in this file, his score will not be logged. |
| 395 |
.Pp |
| 396 |
The game field description files are broken into two parts. |
| 397 |
The first part is the definition section. |
| 398 |
Here, the four tunable game parameters must be set. |
| 399 |
These variables are set with the syntax: |
| 400 |
.Pp |
| 401 |
.Dl "variable = number;" |
| 402 |
.Pp |
| 403 |
Variable may be one of: |
| 404 |
.Li update , |
| 405 |
indicating the number of seconds between forced updates; |
| 406 |
.Li newplane , |
| 407 |
indicating (about) the number of updates between new plane entries; |
| 408 |
.Li width , |
| 409 |
indicating the width of the play field; or |
| 410 |
.Li height , |
| 411 |
indicating the height of the play field. |
| 412 |
.Pp |
| 413 |
The second part of the field description files describes the locations |
| 414 |
of the exits, the beacons, the airports and the lines. |
| 415 |
The syntax is as follows: |
| 416 |
.Pp |
| 417 |
.Bd -literal -offset indent |
| 418 |
.Bl -tag -width airport: -compact |
| 419 |
.It beacon : |
| 420 |
(x y) ... ; |
| 421 |
.It airport : |
| 422 |
(x y direction) ... ; |
| 423 |
.It exit : |
| 424 |
(x y direction) ... ; |
| 425 |
.It line : |
| 426 |
[ (x1 y1) (x2 y2) ] ... ; |
| 427 |
.El |
| 428 |
.Ed |
| 429 |
.Pp |
| 430 |
For beacons, a simple x, y coordinate pair is used (enclosed in parenthesis). |
| 431 |
Airports and exits require a third value, which is one of the directions |
| 432 |
.Em wedcxzaq . |
| 433 |
For airports, this is the direction that planes must be going to take |
| 434 |
off and land, and for exits, this is the direction that planes will be |
| 435 |
going when they |
| 436 |
.Em enter |
| 437 |
the arena. |
| 438 |
This may not seem intuitive, but as there is no restriction on |
| 439 |
direction of exit, this is appropriate. |
| 440 |
Lines are slightly different, since they need two coordinate pairs to |
| 441 |
specify the line endpoints. |
| 442 |
These endpoints must be enclosed in square brackets. |
| 443 |
.Pp |
| 444 |
All statements are semi-colon (;) terminated. |
| 445 |
Multiple item statements accumulate. |
| 446 |
Each definition must occur exactly once, before any item statements. |
| 447 |
Comments begin with a hash (#) symbol and terminate with a newline. |
| 448 |
The coordinates are between zero and width-1 and height-1 inclusive. |
| 449 |
All of the exit coordinates must lie on the borders, and |
| 450 |
all of the beacons and airports must lie inside of the borders. |
| 451 |
Line endpoints may be anywhere within the field, so long as |
| 452 |
the lines are horizontal, vertical or |
| 453 |
.Em exactly |
| 454 |
diagonal. |
| 455 |
.Ss FIELD FILE EXAMPLE |
| 456 |
.Bd -literal |
| 457 |
# This is the default game. |
| 458 |
|
| 459 |
update = 5; |
| 460 |
newplane = 5; |
| 461 |
width = 30; |
| 462 |
height = 21; |
| 463 |
|
| 464 |
exit: ( 12 0 x ) ( 29 0 z ) ( 29 7 a ) ( 29 17 a ) |
| 465 |
( 9 20 e ) ( 0 13 d ) ( 0 7 d ) ( 0 0 c ) ; |
| 466 |
|
| 467 |
beacon: ( 12 7 ) ( 12 17 ) ; |
| 468 |
|
| 469 |
airport: ( 20 15 w ) ( 20 18 d ) ; |
| 470 |
|
| 471 |
line: [ ( 1 1 ) ( 6 6 ) ] |
| 472 |
[ ( 12 1 ) ( 12 6 ) ] |
| 473 |
[ ( 13 7 ) ( 28 7 ) ] |
| 474 |
[ ( 28 1 ) ( 13 16 ) ] |
| 475 |
[ ( 1 13 ) ( 11 13 ) ] |
| 476 |
[ ( 12 8 ) ( 12 16 ) ] |
| 477 |
[ ( 11 18 ) ( 10 19 ) ] |
| 478 |
[ ( 13 17 ) ( 28 17 ) ] |
| 479 |
[ ( 1 7 ) ( 11 7 ) ] ; |
| 480 |
|
| 481 |
.Ed |
| 482 |
.Sh FILES |
| 483 |
Files are kept in a special directory. |
| 484 |
See the |
| 485 |
.Sx OPTIONS |
| 486 |
section for a way to print this path out. |
| 487 |
It is normally |
| 488 |
.Pa /usr/share/games/bsdgames/atc . |
| 489 |
.Pp |
| 490 |
This directory contains the file |
| 491 |
.Pa Game_List , |
| 492 |
which holds the list of playable games, as well as the games themselves. |
| 493 |
.Pp |
| 494 |
The scores are kept in |
| 495 |
.Pa /var/games/bsdgames/atc_score . |
| 496 |
.Sh AUTHOR |
| 497 |
Ed James, UC Berkeley: [email protected], ucbvax!edjames |
| 498 |
.Pp |
| 499 |
This game is based on someone's description of the overall flavor |
| 500 |
of a game written for some unknown PC many years ago, maybe. |
| 501 |
.Sh BUGS |
| 502 |
The screen sometimes refreshes after you have quit. |