From: "Ron Natalie" <ron@ronnatalie.com>
To: "Mary Ann Horton" <mah@mhorton.net>, tuhs@tuhs.org
Subject: [TUHS] Re: Unix/Linux games [was Re: Early GUI on Linux]
Date: Tue, 28 Feb 2023 19:45:43 +0000 [thread overview]
Message-ID: <emb9f47cca-a05d-43bc-a297-a0f64fdde7e7@ad99ed46.com> (raw)
In-Reply-To: <4bea6304-e275-c336-042b-899aaf3cab35@mhorton.net>
[-- Attachment #1: Type: text/plain, Size: 1560 bytes --]
We all pretty much started with Adventure (Dungeon, Collosal Cave)
whatever you want to call it.
We got Zork later on.
There was Peter Langston’s Empire that had a huge following at BRL. We
thought we had it in check because the game had it’s own limits on how
much you could play it you were limited to 60 minutes of clock time a
day and how many BTUs (bureaucratic time units) your capital made.
The problem was people would spend their time online downloading maps
and then spend the afternoon pouring over tomorrows moves. The
director finally made us shut it down.
There was a multiplayer game called “search” that we would play. Late
in the day you’d hear someone yell “Search’s up” and off we go.
Then we got the SGI workstations and flew the flight simulator. They
had a multiplayer dogfight but it used XNS which our network wasn’t
going to handle (at least not off the local subnet). I recoded it to
use TCP. Rather than using broadcast packets, each “airplane” opened a
connection to a server I called “Air Traffic Control.” From there I
could watch the whole thing. I also added an anti-aircraft gun to
shoot at people hanging around the airfield waiting to attack aircraft
that newly appeared in the game there. A few months later I was at
Nasa Ames for an IETF meeting and mentioned I had done this and they
made me sit down and ftp over the code so NASA’s productivity could also
be destroyed.
Ron “A hollow voice says ‘plugh’ Natalie
[-- Attachment #2: Type: text/html, Size: 2506 bytes --]
next prev parent reply other threads:[~2023-02-28 19:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 7:48 [TUHS] " Andy Kosela
2023-02-28 10:44 ` [TUHS] " Lars Brinkhoff
2023-02-28 11:02 ` Arno Griffioen via TUHS
2023-02-28 11:06 ` Dagobert Michelsen
2023-02-28 16:49 ` Mary Ann Horton
2023-02-28 19:45 ` Ron Natalie [this message]
2023-02-28 20:01 ` segaloco via TUHS
2023-02-28 20:24 ` Dr Iain Maoileoin
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=emb9f47cca-a05d-43bc-a297-a0f64fdde7e7@ad99ed46.com \
--to=ron@ronnatalie.com \
--cc=mah@mhorton.net \
--cc=tuhs@tuhs.org \
/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).