The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ken Thompson via TUHS <tuhs@minnie.tuhs.org>
To: Steve Johnson <scj@yaccman.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Gaming on early Unix
Date: Sun, 8 Dec 2019 16:35:25 -0800	[thread overview]
Message-ID: <CAG=a+riKQr1ohYMjt3=XE5CkFypoH-+u1H51Q3EVMWJFtZkkPQ@mail.gmail.com> (raw)
In-Reply-To: <3d1053b0debfc5a79267860e058b1d07e7686811@webmail.yaccman.com>

in the early 70s, noone had seen a computer.
i had a terminal at home and we were giving
a dinner party. i wrote several games for the
party from the back of an off-the-shelf puzzle
book.

the ones i remember:

moo (bulls + cows)
hunt the wumpus (move or shoot)
learning tic-tac-toe
i can guess your number (divide and conquer)
jealous husbands (similar to fox hen corn)
nim

i think there were more. they went over
pretty well at the party.

i think this was 1969 or 1970.

On Sun, Dec 8, 2019 at 4:14 PM Steve Johnson <scj@yaccman.com> wrote:
>
> I wrote a very simple game for my son -- go fish.   It was one of my first C programs (that is evident by the fact that it contains several goto's).  There is the source code in one of the BSD distributions, dated 1980 (with a UCB copyright...).
>
> The original game simply played cards at random from its hand, and was pretty easy to beat.  Then I realized that there was a simple strategy -- if the player asked the program for, e.g., a 5, the program remembered that the player had a 5.   If it later drew a 5 it immediately asked for it.   This "pro" version was very hard to beat, to the extent that nobody wanted to play it.  So I made the pro version an option--the default was the dumb mode.
>
> It didn't get a lot of hype, but I did face an irate user once at a Usenix meeting who publicly accused me of cheating (since the program did, in fact, know what the player's had was).  The pro option was that good, but, unless somebody changed a copy of it, the user's hand wasn't part of the strategy...
>
> Looking at the code a couple of months ago, I found at least one bug and one logical error.  The bug would have been caught by Lint, but that program was many years in the future.
>
> Steve
>
>
>
> ----- Original Message -----
> From: "Richard Salz" <rich.salz@gmail.com>
> To:<ron@ronnatalie.com>
> Cc:"TUHS main list" <tuhs@minnie.tuhs.org>
> Sent:Fri, 6 Dec 2019 11:39:42 -0500
> Subject:Re: [TUHS] Gaming on early Unix
>
>
>> There was another multiplayer game called “Search” that would result around 4:30 in the afternoon someone yelling “Search Up” which was everybody’s cue to join in the game.
>>
>>
> Was that "hunt" that came with BSD 4-something?

  reply	other threads:[~2019-12-09  0:36 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 10:45 Gabriel Diaz
2019-12-06 11:01 ` Steve Nickolas
2019-12-06 14:23 ` A. P. Garcia
2019-12-06 14:48   ` A. P. Garcia
2019-12-08  7:48   ` arnold
2019-12-08 19:54     ` Clem Cole
2019-12-06 16:19 ` ron
2019-12-06 16:39   ` Richard Salz
2019-12-06 16:54     ` Dan Cross
2019-12-09  0:05     ` Steve Johnson
2019-12-09  0:35       ` Ken Thompson via TUHS [this message]
2019-12-09  0:46         ` Adam Thornton
2019-12-09  2:03           ` Rob Pike
2019-12-09  2:10             ` Ken Thompson via TUHS
2019-12-09  2:15               ` Rob Pike
2019-12-09  2:19                 ` Ken Thompson via TUHS
2019-12-09  8:41                   ` Gabriel Diaz
2019-12-09 11:17               ` Angelo Papenhoff
2019-12-09  8:40         ` Naveen Nathan
2019-12-06 17:24   ` Arthur Krewat
2019-12-06 17:58   ` Dr Iain Maoileoin
2019-12-06 22:12     ` ron
2019-12-07  0:04       ` Rob Pike
2019-12-07  1:22 ` Adam Thornton
2019-12-07  1:28   ` Adam Thornton
2019-12-10  0:30 Doug McIlroy
2019-12-10  5:08 ` Adam Thornton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAG=a+riKQr1ohYMjt3=XE5CkFypoH-+u1H51Q3EVMWJFtZkkPQ@mail.gmail.com' \
    --to=tuhs@minnie.tuhs.org \
    --cc=ken@google.com \
    --cc=scj@yaccman.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).