(Message inbox:90)
Return-Path: cschaffe@piranha.rutgers.edu
Received: from mail.fwi.uva.nl by gene.fwi.uva.nl with SMTP (5.65c(FWI)/3.0)
          id AA29257; Tue Feb 16 11:56:44 1993
Received: by mail.fwi.uva.nl from piranha.rutgers.edu  with SMTP (5.65c(FWI)/3.0)
          id AA06894; Tue, 16 Feb 1993 22:59:16 +0100
Received: by piranha.rutgers.edu (5.59/SMI4.0/RU1.5/3.08) 
	id AA14258; Tue, 16 Feb 93 16:56:44 EST
Date: Tue, 16 Feb 93 16:56:44 EST
From: cschaffe@piranha.rutgers.edu (Michael Timmons)
Message-Id: <9302162156.AA14258@piranha.rutgers.edu>
To: stolk@fwi.uva.nl
Subject: ...
Cc: dove@well.sf.ca.us, edan@netcom.com, fontenot@comet.rice.edu,
        graham@cs.montana.edu, groenewo@fwi.uva.nl, hjtoi@jyu.fi,
        jw@ddsdx2.jhuapl.edu, lyn@matt.ksu.ksu.edu, peugh@wam.umd.edu,
        pulkka@cs.washington.edu, vexar@watserv.ucr.edu


Hi,

  I am working with the client, and I am working with a version of BSX
that will hopefully run on a MUCK.  I have been keeping my ear in on this
conference, and I think that all these changes will be fine and dandy, but
as someone stated previously, people will be annoyed with changes in the
client. (sorry for the run-on sentence).  I am designing this version of BSX
using the same old client with the same old protocol.  If a change in the
client or the protocol happens, My server side wont be affected, but the
users of Regenisis will be FURIOUS... some of those people who dont know
much about computers will be pissed when they find out that the client that
they spend 4 days trying to compile only shows 1/2 of the things the new
server dishes out to it.  All of the new stuff will show up as garbage, sort
of as if you connected to Regenisis using just telnet, or TF.
  But, I also have to say that the protocol is not perfect, as is.  In bringing
up graphics from the programs I had written, I found that I could (for example)

say @TMS

and it would automatically log everyone off in the room. Likewise if I shout it,
the everyone on the game... this momentarily stopped me from continuing
with my work, because I know there are users who love to take advantage of
these things.  

   I do agree that all of the changes that were mentioned in your letters
were great suggestions, and should be implimented, but I vote that you only
change the protocol once, and never change it again. I dont know how possible
this is, but it would prevent a lot of user aggravation.  Maybe, if there
is a list of where who the users are who call Regenesis, they could all be
mailed that the change in protocol has happened, and maybe assistance could
be given to those who cant figure out how to recompile it, etc.

One minor change that I WOULD like to see in the client (not the PROTOCOL)
is a MORE function... similar to the more command in unix, where it will
stop after a page of type has flown by on the screen, and wait until the user
type TAB, or something.

One MAJOR change that I would like to see in the PROTOCOL is that I would like
 to see all of the @ commands, like the @TMS command, HAVE to begin on a new
 line.  Whenever a user types something in, it wont show up on a new line. this
 will solve the problem that I mentioned WAY up there about people sending 
 unwanted graphics, and PROTOCOL commands to another user.  I feel so 
 strongly about this, because of certain users that I have met in the past
 who love to create trouble!

I dont know if any of this will help, but maybve it will....

  Chris Schaffer
  cschaffe@flounder.rutgers.edu