Newsgroups: rec.arts.int-fiction
Path: gmd.de!jvnc.net!yale.edu!spool.mu.edu!wupost!udel!princeton!phoenix.Princeton.EDU!jacobw
From: jacobw@phoenix.Princeton.EDU (Jacob Solomon Weinstein)
Subject: Re: Encrypted hints
Message-ID: <1992Dec9.042338.25929@Princeton.EDU>
Originator: news@nimaster
Sender: news@Princeton.EDU (USENET News System)
Nntp-Posting-Host: phoenix.princeton.edu
Organization: Princeton University
References: <1992Dec8.163209.29880@Princeton.EDU>> <9561927@MVB.SAIC.COM> <librik.723862760@cory.Berkeley.EDU>
Date: Wed, 9 Dec 1992 04:23:38 GMT
Lines: 18

librik@cory.Berkeley.EDU (David Librik) writes:
>
>jacobw@phoenix.Princeton.EDU (Jacob Solomon Weinstein) writes:
>> I wouldn't want to decode thirteen pages of
>>hints encoded in my cypher, but the letter-reversal thing would make
>>reading them pretty easy.
>
>If you have to read thirteen pages of hints, something's wrong with your game.
>Hints should be used sparingly, when you get stuck.
I don't quite understand your objection. My point in my original posting
was  that, when the hints are well-written, it's fun to read through all
the hints AFTER you've solved the game. Clearly, anybody who would read
all thirteen pages of hints before solving the game would probably have
been better off just getting a walkthrough.

The reason my hint sheet is so long, by the way, is that I've followed
the old Infocom model of having a series of progressively more spoiling
hints for each puzzle.
