Habitat Emails

These are logs/diary entries which were taken from Chip Morningstars Habitat Archives.

July 1985

July 18th

Taken from worldComments.

From dragon Thu Jul 18 17:13:15 1985
Subject: microworld
(no, not a serious name suggestion)

An idea, though...  In addition to avatars (which might have different modes
of seeing/moving/etc), one might have tools in the other world, such as
binoculars (or a telescope, lacking 3-D capability).  Perhaps the normal view
would be as in Rescue, Eidolon or Koronis Rift, about 90 degrees and not very
far away.  A telescopic view would present about the same amount of detail,
but distribute it differently so that one could see a long distance in a very
narrow cone (say 10 degrees).

Objects and terrain could have several additional non-visual dimensions of
information, such as temperature, reflectivity and metallic content.  Thus,
different modes of "seeing" might give entirely different views from the same
terrain.  Electromagnetic scanners, such as radar, would show a metallic
object as being substantially brighter than a non-metallic one, for instance.
Infrared would show lakes as dark spots, and volcanoes, hot springs or
subterranean nuclear power stations as brighter highlights.

We should also be careful not to rule out non-human modes of vision (and other
sensory apparatus).  Many non-human or semi-human races in D&D have
infravision, for example, and would see in the infrared spectrum as well
underground as a normal human might above ground.

In True Names, one of the characters takes off (from the high mountain
[satellite] meeting place) as an eagle.  This might be represented on a home
computer as a flight simulator with a very narrow field of view, and different
(but not unrealistic) flight dynamics.  The narrow field graphics might
provide a certain amount of disorientation, until one "got used to the form",
so to speak.

Just an idea...
							Charlie

May 1986

May 14th

Taken from demo.aric.t.

From aric Wed May 14 10:03:13 1986
Subject: CES presentation
	Randy and I talked yesterday about ideas for the CES presentation.
Following are some of the ideas that came out of that discussion...

Purpose of demonstration:

	Show off avatars (variety, capabilities)
	Show off objects (variety, portability, containership...)
	Show off Regions (variety)
	Show off Telecommunications (multiple players, shared host)
	Show off potential for game play

Possible demonstration:

	Begin with avatar at home...

Scene:	Inside of avatar home. Surroundings include; fishtank,
	answering machine, avatar, chair, window.  Answering machine
	is blinking indicating that it has a message.

Action:	Avatar can move things around the house and then later moves to
	answering machine and gets message that FRIENDX is coming over.
	Moments later, doorbell rings and FRIENDX arrives.
	Conversation follows regarding visit to...fountain, park, atm, arcade.
	Avatars decide to travel to arcade.
	Avatars leave house via front door.

Scene:	Front of house.  Surroundings include home, Sun, trees, mailbox.  Flag
	is up on mailbox.

Action:	Avatar opens mailbox and retrieves letter.  Avatar can read contents
	if desired.  Flag lowers on mailbox.
	Avatar realizes that he has no cash, and requests that they stop at
	atm on the way to the arcade.

Scene:	Next region over.  Contains convenient teleport booth, fire hydrant,
	trees.

Action:	Avatars walk to teleport booth and ZAP tm. to side of bank. (we could
	set destination choice with function keys to get us to any region
	desired!)

Scene:	Outside of Bank.  Brick wall in back and ATM attached to wall.

Action	Avatar performs correct mumbo jumbo and Tokens arrive.  Avatars are
	now ready to go to the arcade.

Scene:	Park.  Lots of trees and bushes

Action:	Walk through

Scene:	Arcade.	Contains targets and guns

Action:	Shoot targets together, for points, sound effects.

Scene:	Outside of Cave.  Dark entrance with stonework around edge.

Action:	Decision as to whether to travel inside.

Scene:	Inside of Cave.  Dark background with Rocks on floor and stalagtites
	hanging from roof.  A locked treasure chest lies on the floor here.

Action:	Use target gun to shoot Rocks, Stalagtite, Treasure chest.  When
	the chest is opened (there should also be a key around somewhere)
	a gem will be found inside.  Avatars should decide who gets the gem.

	This is a preliminary layout for a possible demonstration, but many
new objects need to be added in order to give us a larger range of possible
actions.  I think that using a scripting system in important in order to
view all of the possible variations that we can present.

		--aric

September 1986

September 5th

Taken from statusReport.Sept5.

From chip Fri Sep  5 22:30:06 1986
Received: by moth; 05 SEP 86 22:30:06 PDT
From: chip (Chip Morningstar -- "Software Without Moving Parts")
To: sda
Cc: chip
Subject: Status report
Status: R

We had the interview with the Japanese TV folk.  It went well, I think, though
they were pretty loose in their shooting, so I'm not sure what the result will
look like.  (In general the Japanese media seems to prefer to produce a lot of
material quickly and with less polish, whereas their American counterparts are
more conscious of style and produce a smaller volume of more carefully crafted
stuff -- I've noticed this about the Japanese magazines and the TV people
seemed the same way.  Comparative sociology at work!)

Randy got a call from Janet early this morning, just before she disappeared
off to wherever she's going.  She said that she was finally able to login to
our system (she'd been having problems yesterday) and transfer the stuff over
that we wanted them to have (more regions for Populopolis and the data tables
for the memory capacity handler).  (I asked her to leave me a message on their
system telling me where all the material relating to this component is so that
I can work on it myself if necessary.  She does not appear to have done this.)

Randy mentioned to Janet that we had been thinking about a scheme to allow
more objects to occupy memory at the same time by selectively not loading
their imagery and behavior code under certain circumstances (this is the thing
we mentioned to you Thursday) but that it would cost a week or two to
implement.  In spite of the inherent delay, she was intrigued.  Randy suspects
he knows what he's going to be doing next week.

She called back a short while later, said she had talked to Marc, and that he
was entertaining the notion of delaying beta to put this in, and that you and
I should call him to discuss it!  Unfortunately, you weren't here.

I could have called him on my own, but I felt very strongly that I should
consult with you before undertaking discussion of this with Quantum, since it
seems rather drastic, possibly threatening getting the product out for
Christmas -- frankly I felt that I would be a little over my head to call Marc
on my own and start discussing this, since I am unclear, in particular, on the
specifics of the timing constraints we are under.

In other words, I didn't call Marc back and take it up with him by myself
because you weren't here and I was afraid to make any kind of commitments one
way or the other on my own initiative.  This may have been a mistake, since it
*is* Friday (thus the decision gets delayed over the weekend instead of just
overnight), but I suspect not, since Randy won't really be able to begin work
on the thing in earnest until Monday anyhow.  Nevertheless, you and I need to
talk about this ASAP, then contact Marc.  I will be in the office Saturday
afternoon for sure and either Saturday evening or Sunday afternoon also
(probably both...).

From chip Fri Sep  5 23:04:13 1986
Received: by moth; 05 SEP 86 23:04:13 PDT
From: chip (Chip Morningstar -- "Software Without Moving Parts")
To: sda
Cc: chip
Subject: Status report addenda
Status: R

One thing I forgot to include in the previous message:

I met this morning with Jamie Williams.  I gave her the latest draft of the
manual to look over, and told her the things that I thought needed adding that
I'd like to have her work on.  I also asked her to proof the thing for
stylistic consistency, since I have rewritten large chunks of it in the time
between when she last worked on it and now.  I want to make sure that the
clear and direct style which she adopted is also reflected in the parts I have
added or substantially changed.

I showed her the promo tape (do we have a name for that thing, by the way?)
and gave her a live demo of the system.

We then talked about the press conference and about the sort of
demonstration/presentation I should be giving and how it should be structured
to cover the items on the agenda that I am supposed to talk about (suitably
modified by our own idea of appropriateness by adding some things to and
removing one or two things from the list that Quantum sent us).  We roughed
out a basic demo structure which she is going to take as a starting point.  I
also gave her copies of the "Funativity" and "Machiavelli" documents to give
her some general idea of the various kinds of activities we are thinking of
having in Habitat, beyond the rather vague notion of "adventuring".

She is going to work on these things and send (by messenger service) the
manual revisions and a first draft demo/presentation on Monday or Tuesday.
I'll give her feedback by phone (she has some job she has to be at those days)
and she'll then work on whatever adjustments to the presentation we deem
necessary.  She will come back in person on Wednesday or Thursday to start
finalizing the presentation.

It all looks good to me.  Jamie's a real pro.

I had gotten the feeling from our earlier conversations that you had some
things that *you* wanted her to work on for the press conference also, but I
had no idea what, if anything, these might be, so we obviously didn't cover
them.  If I am mistaken, great.  If not, you'd best contact her.

By the way, did you notice that the proposed press conference agenda that
Quantum sent us allocates 5 minutes for our 8 minute tape?

Oh, also:  I got a call today from Rob Fulop.  He wants to come up and visit
us Tuesday.  He's interested in various things, including mutual support
developing software for Quantum, development tools for 6502 machines, and of
course various Habitat tie-in things (creative and/or technological).  I think
he will contact you directly to arrange something official.

November 1986

November 7th

Taken from nancymemo.

Date:  November 7, 1986
To:  Cathy Anderson
>From:  Nancy Mohler
Subject:  HABITAT STATUS

Here is today's updated Habitat Task List, including time to complete tasks,
target completions, categorization of beta prerequisites, and the requested
change to the Effects column.  Implementation time for remaining tasks will
be determined with Janet's input.  Beta software submission is expected 11/24.
The public release schedule will be determined next week.

Recapping the status conference call today:
  1. Resolved to limit the Rant to a condensed version in a Habitat book and
     put bulk of text in tree-structure outside.
  2. Protocol bug estimated to be 95% fixed, with update made available this
     afternoon.
  3. Delivery date for the user version (beta testers) map TBD by LFL ASAP.
  4. Open issue for discussion is how the home vendo will be used.
  5. Tabled until Monday how to make mail more accessible.  LFL to prepare
     alternative proposal.
  6. Agreed on 100 as the number of tokens in pocket of Avatars being hatched,
     pending completion of economic plan.
The 11/10 Habitat status conference call will be at 4:00 QL-time, 1:00 Marin.
Suggested agenda:  protocol bug status, mail resolution, Task List.

cc:  Steve Arnold
     Steve Case
     Randy Farmer
     Janet Hunter
     Chip Morningstar
     Marc Seriff
     Aric Wilmunder

November 11th

Taken from janetEst.

From quantum Tue Nov 11 09:16:37 1986
Received: from shem by moth; 11 NOV 86 09:16:37 PST
From: quantum (Janet Hunter, Quantum Computer Services)
To: chip
Received: by shem; 11 NOV 86 09:16:36 PST
Subject: Time estimates
Status: RO

Chip, 
   Here are my time estimates for the
Beta Test Prequisite Tasks:

  6 Capacity Monitor - 2 days
                       target 11/14
  7 Rebuild Regionproc - done 11/11
 15 Oracle response - 1 day
                      target 11/17
 16 Bank acct utility - 1 day
                        target 11/16
 18 Text input utility - 1 day
                         target 11/19
 67 Avatar to ghost - done
 68 Online-only ghosts - done
 69 Exclude non-beta testers - done
 40 Msg of the day - 1 day
                     target 11/20 (?)
 72 create avatar w/ token - .5 day
                          target 11/14

 OOPS: Target date for #16 should be
       11/18, not 11/16.

 Note: Question mark on target date for
       #40 is because it is assigned to
       both you and me.

April 1987

April 19th

Taken from newprocedure.t.

From nancy Sun Apr 19 19:02:01 1987
Subject: Friday meeting outcome
file notes
4/17/87 Habitat team meeting w/sda

In order to achieve release into beta test and to revise project completion
plan with better time estimates--

1. confirmed commitment to daily playtesting w/QL at 5:30 (our time)--Aric,
Chip & Randy will let me know of any conflict not allowing them to be on.

2. revised playtest debriefing procedure:  a hard copy bug reporting form
will be created by Chip for distribution to all playtesters.  completed
forms will be turned in to Randy asap (next morning fax from Janet) for him
to maintain tracking system; Chip will review with him Randy's assignment of
disposition daily.  so, rather than the on-line PC debriefings immediately
following a playtest & conference calls after receipt of the tapes to review
the list, Randy will maintain a bug tracking system to, 1) improve efficient
use of everyone's time, 2) improve response to reported bugs, and 3) improve
communication & confidence between us & QL.  I'll discuss this procedure
revision w/Janet & Rob during the scheduled 10:00 conference call Monday
morning.  Assuming their agreement, Cathy & I will review the bug tracking
reports via near-daily conference calls & flag ones needing discussion among
the team.

3. established daily status reports:  Aric & Randy will mail to Chip
(copying each other & sda & me) at the end of each day a brief list of their
accomplishments for the day, notes explaining significant delays in any
tasks, and a list of tasks expected to be undertaken the next day, including
time estimated to complete.  Chip, including his own tasks, will issue a
Habitat daily status summary of accomplishments relative to start of alpha,
start of beta, & estimated time to release.

4. reduced frequency of entire team QL conference calls:  to be scheduled by
Cathy & me as needed, usually at 1:00 our time.  We'll discuss this process
with her on Thursday when she's here.

5. established weekly Habitat team meetings on Friday afternoons, to review
accomplishments of the week & goals for the next.