[net.games.rogue] It's your own fault if you get hit with the saved game bug!!

dave@uwvax.ARPA (08/01/84)

Says Michael Mc Namara:

    It's like taking off your  plate mail and walking into a party room full of
trolls.  Every time I see people flaming about the "Saved game bug", I lose all
sympathy.  Guys, under 4.2BSD, ^Y is a delayed suspend signal.  ^Y  also  means
UP LEFT to rogue.  If you get a ^Y through the game to the shell, the game won't
immediatly die, but will get a suspend signal as soon as the program looks for 
any signals from the OS.  Rogue responds (incorrectly) to ^Y by saving the game.
If you want avoid this problem, and haven't written a shell script like:

Response:

BULLSH*T!!! I have my delayed suspend character undefined (i.e. *NOT*
CTRL/Y).  I am *still* hit with the saved game bug.  This normally
happens after being hit by the nympho bug.

-- 
Dave Cohrs @ wisconsin
...!{allegra,heurikon,ihnp4,seismo,ucbvax,uwm-evax}!uwvax!dave
dave@wisc-rsch.arpa

brian@uwvax.ARPA (08/01/84)

RIGHT!  It is your own fault if you get hit with the saved game bug... but 
not because there is a fix for the problem.  At Wisconsin, several of us run
rogue without dsusp defined and we STILL encounter the save bug.  If you get
hit with the bug, then it's your fault for saving the game in the first place.

-- 
Brian Pinkerton @ wisconsin
...!{allegra,heurikon,ihnp4,seismo,sfwin,ucbvax,uwm-evax}!uwvax!brian
brian@wisc-rsch.arpa

tims@mako.UUCP (Tim Stoehr) (08/03/84)

I can type the Control-Y key thousands of times with no effect generated.
I have been hit by the save bug many times that I know I didn't touch
that Control-Y.  It's a bona-fide bug in rogue source that needs to be
fixed.