Path: utzoo!utgpu!attcan!uunet!mcvax!hp4nl!philmds!prle!cstw01!meulenbr
From: meulenbr@cstw01.UUCP (Frans Meulenbroeks)
Newsgroups: comp.sources.games.bugs
Subject: Re: wanderer2, screens 13,16,17,18,20
Message-ID: <256@cstw01.UUCP>
Date: 7 Nov 88 10:56:38 GMT
References: <427@occrsh.ATT.COM> <438@occrsh.ATT.COM>
Reply-To: meulenbr@cstw01.UUCP (Frans Meulenbroeks)
Organization: Centre for Software Technology, Philips Eindhoven
Lines: 38

Hi!

Several people have complained about the screens mentioned above.
Various changes have been proposed.
I'd like to comment on a few of these:
screen 13: not solvable. suggested fix: ok
screen 16: the corrected version send out by Steven Shipway is solvable.
I'd suggest we use that one (it is harder).
screen 17: not solvable as corrected by Steven: the suggested fix is
(in my humble opinion) as good as another one. Can the author comment.
screen 18: this screen IS solvable as distributed. Don't fix it.
The looping of the S is in my opinion a feature and not a bug
(if a monster wants to occupy a position that is already taken, it
changes direction; seems fair).
I'll include a very small hint on solving it at the end of this message.
Note: screen 18 is very hard. I'm working on a screen which needs the 
same behaviour. but is a little less complicated.
screen 20: not solvable. with suggested fix: not too hard.

Remember: this game is tough! Don't complain too easy that a screen is
not solvable.

Thanks Steven, for creating such a great game.
(by the way: it is easy to port this game to Minix/ST: you just need to
declare a routine (I think getenv) somewhere, and you'll have to copy the
structs in scores.c manually. And of course you'll need a curses.
(Don't ask mine, it is not PD; sorry))



screen 18 small hint: 
Examine what causes the problem. 
Try to solve it using the same techniques.

-- 
Frans Meulenbroeks        (meulenbr@cst.prl.philips.nl)
	Centre for Software Technology
	( or try: ...!mcvax!philmds!prle!cst!meulenbr)