<!-- MHonArc v2.4.4 -->
<!--X-Subject: Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks) -->
<!--X-From-R13: ptNnzv-pt.UenlEntr.Sqzbagba.OP.QO (Quevf Uenl) -->
<!--X-Date: Mon, 02 Mar 1998 09:28:57 +0000 -->
<!--X-Message-Id: 9803012349.8vmx@ami-cg.GraySage.Edmonton.AB.CA -->
<!--X-Content-Type: text/plain -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks</title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">
</head>
<body background="/backgrounds/paperback.gif" bgcolor="#ffffff"
text="#000000" link="#0000FF" alink="#FF0000" vlink="#006000">
<font size="+4" color="#804040">
<strong><em>MUD-Dev<br>mailing list archive</em></strong>
</font>
<br>
[ <a href="../">Other Periods</a>
| <a href="../../">Other mailing lists</a>
| <a href="/search.php3">Search</a>
]
<br clear=all><hr>
<!--X-Body-Begin-->
<!--X-User-Header-->
<!--X-User-Header-End-->
<!--X-TopPNI-->
Date:
[ <a href="msg00665.html">Previous</a>
| <a href="msg00667.html">Next</a>
]
Thread:
[ <a href="msg00837.html">Previous</a>
| <a href="msg00790.html">Next</a>
]
Index:
[ <A HREF="author.html#00666">Author</A>
| <A HREF="#00666">Date</A>
| <A HREF="thread.html#00666">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</H1>
<HR>
<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->
<UL>
<LI><em>To</em>: <A HREF="mailto:mud-dev#null,net">mud-dev#null,net</A></LI>
<LI><em>Subject</em>: Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</LI>
<LI><em>From</em>: <A HREF="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</A> (Chris Gray)</LI>
<LI><em>Date</em>: Sun, 1 Mar 98 16:49:37 MST</LI>
</UL>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<HR>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<PRE>
[Adam Wiggins:]
:So here's a question to you, Chris, and all those that have remained silent
:on this thus far: which do you prefer - a client whose speed is directly
:proportional to the speed of your internet connection so that you can rely
:on every client always being 100% "correct", or one which runs at its own
:framerate (hopefully 30fps or better) attempting to display what data it has
:about the world as best it can, resulting in some inconsistencies (or perhaps
:many if your connection is very unstable)? I know which one I'd choose, but
:I wonder how many people feel the same? Or perhaps there should be some sort
:of consistency sliders in the options screen which change how much prediction
:it does on its own, and how much it relies on the server for?
I'll answer since asked, but I doubt my opinion has much value. I haven't
played any serious real-time games for years, so have little in the way
of experience to back up an opinion with. I have never even seen any of
the current multi-player online action games. Maybe in a few months I'll
be able to afford a new computer.
My concerns have not been with the presentation, but with what is
presented. It seems to me that once you allow your system to display
something that it doesn't know to be accurate, you have essentially
"stepped off the deep end" in that respect. With a limited game, such as
some that have been discussed with respect to this question, I tend to
agree that doing simple physics and projections in the client is likely
good enough.
But what about a full MUD, with player written magic spells, wierd NPC's
created by builders, etc? You *can't* predict what they will do without
having all of the database available to the client. Sure, 99.9% of the
time you will have enough to run their code and get the same answer the
master server will. It's a bit like chaos theory - you can't predict all
of the answers all of the time, because seemingly inconsequential things
can combine to yield massive changes. To me, the main thing I want in
a computer interface of any kind is predictability and consistency. If
the interface does some blinking or sparkling or something to show me
when it doesn't quite know what is going to happen, then I want it to
guarantee that it will do so. But that pretty well means that it has
to do so everywhere, all the time. So, it isn't useful.
Again, my perspective here is likely different than the kind of game and
client that were being discussed, but as I said above, I don't have a
valid opinion about that kind of game.
--
Chris Gray cg#ami-cg,GraySage.Edmonton.AB.CA
</PRE>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<HR>
<!--X-Follow-Ups-End-->
<!--X-References-->
<!--X-References-End-->
<!--X-BotPNI-->
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg00665.html">Re: [MUD-Dev] Java and Javascript</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00667.html">Re: [MUD-Dev] Net protocols for MUDing</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00837.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00790.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00666"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00666"><STRONG>Thread</STRONG></A></LI>
</UL>
</LI>
</UL>
<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
<ul><li>Thread context:
<BLOCKQUOTE><UL>
<LI><STRONG>Re: [MUD-Dev] Net protocols for MUDing</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<LI><strong><A NAME="00795" HREF="msg00795.html">Re: [MUD-Dev] Net protocols for MUDing</A></strong>,
Shawn Halpenny <a href="mailto:malachai#iname,com">malachai#iname,com</a>, Fri 20 Mar 1998, 18:57 GMT
<UL>
<LI><strong><A NAME="00862" HREF="msg00862.html">Re: [MUD-Dev] Net protocols for MUDing</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Mon 23 Mar 1998, 20:53 GMT
</LI>
</UL>
</LI>
</ul>
</ul>
<LI><strong><A NAME="00775" HREF="msg00775.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Fri 20 Mar 1998, 00:06 GMT
<UL>
<LI><strong><A NAME="00837" HREF="msg00837.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
Adam Wiggins <a href="mailto:nightfall#user2,inficad.com">nightfall#user2,inficad.com</a>, Mon 23 Mar 1998, 07:41 GMT
</LI>
</UL>
</LI>
</ul>
</ul>
<LI><strong><A NAME="00666" HREF="msg00666.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Mon 02 Mar 1998, 09:28 GMT
</LI>
<LI><strong><A NAME="00790" HREF="msg00790.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Fri 20 Mar 1998, 16:36 GMT
<UL>
<LI><strong><A NAME="00792" HREF="msg00792.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
Joel Dillon <a href="mailto:emily#cornholio,new.ox.ac.uk">emily#cornholio,new.ox.ac.uk</a>, Fri 20 Mar 1998, 17:05 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00802" HREF="msg00802.html">Re: [MUD-Dev] Net protocols for MUDing (was: Moore's Law sucks)</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Sat 21 Mar 1998, 02:29 GMT
</LI>
</ul>
</LI>
<LI><strong><A NAME="00649" HREF="msg00649.html">Tutorial: Let's build a Compiler! - Part X: Introducing TINY</A></strong>,
Jon A. Lambert <a href="mailto:jlsysinc#ix,netcom.com">jlsysinc#ix,netcom.com</a>, Sat 28 Feb 1998, 21:43 GMT
</UL></BLOCKQUOTE>
</ul>
<hr>
<center>
[ <a href="../">Other Periods</a>
| <a href="../../">Other mailing lists</a>
| <a href="/search.php3">Search</a>
]
</center>
<hr>
</body>
</html>
