Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: Notesfiles $Revision: 1.6.2.17 $; site uiucdcs.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!ihnp4!inuxc!pur-ee!uiucdcs!mcewan
From: mcewan@uiucdcs.UUCP
Newsgroups: net.games.rogue
Subject: Re: Suggested Changes in Hack
Message-ID: <34500046@uiucdcs.UUCP>
Date: Tue, 29-Jan-85 12:31:00 EST
Article-I.D.: uiucdcs.34500046
Posted: Tue Jan 29 12:31:00 1985
Date-Received: Thu, 31-Jan-85 02:02:09 EST
References: <171@cbuxc.UUCP>
Lines: 22
Nf-ID: #R:cbuxc:-17100:uiucdcs:34500046:000:1114
Nf-From: uiucdcs!mcewan    Jan 29 11:31:00 1985

>        For example: Let's say that the user is searching out a wall.  The little
>   dog comes in and runs around, occasionally resting.  Then the display stops.
>   The user assumes that the search produced no results, and hits the h-key.  But,
>   in fact, the display had stopped because the computer was taking its own
>   goddamned time.  The search is resumed; the dog runs around; the search comes
>   to an end; the dog steps in the way; and -- POW! -- you kill the little dog.
>        This sort of thing happens to me all the time, and the only way the avoid
>   it is to wait a minute or two between each entry.
>   

A very simple way around this problem (at least it works in all versions
of rogue I've played, although I've never played hack) is to hit a key
that does not correspond to a command ("a" is handy in rogue) or some
command that doesn't do anything active ("v" works well) and then wait
for the error message or version number to be displayed before making
any moves.

			Scott McEwan
			{ihnp4,pur-ee}!uiucdcs!mcewan

"Uh oh. Looks like we got a 666 down there - diety on a rampage."