games, so you can't prove to others that you've seen it. He says it
shouldn't fire back, either. It should do nothing except scream and
disappear when hit by photon torpedos. It's OK that it may move
games, so you can't prove to others that you've seen it. He says it
shouldn't fire back, either. It should do nothing except scream and
disappear when hit by photon torpedos. It's OK that it may move
-when attacked, but it didn't in the original. (Whether the Thingy
-can fire back is now controlled by OPTION_THINGY and turned off if the
-game type is "plain" or "almy". The no-save behavior has been restored.)
+when attacked, but it didn't in the original. (The no-save behavior
+has been restored.)
features that I liked. I also took a peek at the DECUS version (a
port, less sources, to the PDP-10), and some other variations.
features that I liked. I also took a peek at the DECUS version (a
port, less sources, to the PDP-10), and some other variations.
command to "call" and the "terminate" command to "quit" to better
match user expectations. The DECUS version apparently made those
changes as well as changing "freeze" to "save". However I like
command to "call" and the "terminate" command to "quit" to better
match user expectations. The DECUS version apparently made those
changes as well as changing "freeze" to "save". However I like
the LRSCAN command is no longer needed. (Controlled by OPTION_AUTOSCAN
and turned off if game type is "plain" or "almy".)
the LRSCAN command is no longer needed. (Controlled by OPTION_AUTOSCAN
and turned off if game type is "plain" or "almy".)
Two things to do to the log before dropping it in the test directory:
(a) Strip out all lines beginning with "#curses:" - these are for debugging
Two things to do to the log before dropping it in the test directory:
(a) Strip out all lines beginning with "#curses:" - these are for debugging
them makes it easier to see the game commands.
(b) Add a header comment line explaining what the log is a test for.
them makes it easier to see the game commands.
(b) Add a header comment line explaining what the log is a test for.