<!-- MHonArc v2.4.4 --> <!--X-Subject: Re: [MUD-Dev] The impact of the web on muds --> <!--X-From-R13: ptNnzv-pt.UenlEntr.Sqzbagba.OP.QO (Quevf Uenl) --> <!--X-Date: Sun, 25 Jan 1998 18:55:12 +0000 --> <!--X-Message-Id: 9801251738.8rd3@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] The impact of the web on muds</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="msg00314.html">Previous</a> | <a href="msg00316.html">Next</a> ] Thread: [ <a href="msg00309.html">Previous</a> | <a href="msg00317.html">Next</a> ] Index: [ <A HREF="author.html#00315">Author</A> | <A HREF="#00315">Date</A> | <A HREF="thread.html#00315">Thread</A> ] <!--X-TopPNI-End--> <!--X-MsgBody--> <!--X-Subject-Header-Begin--> <H1>Re: [MUD-Dev] The impact of the web on muds</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] The impact of the web on muds</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, 25 Jan 98 10:38:13 MST</LI> </UL> <!--X-Head-of-Message-End--> <!--X-Head-Body-Sep-Begin--> <HR> <!--X-Head-Body-Sep-End--> <!--X-Body-of-Message--> <PRE> [Caliban:] [Lots of stuff snipped, but I'll touch on parts of it.] One of the things that you touch on is fairly subjective. That is the concept of the "mood" of the MUD, and the kind of things you as a player want from a MUD. If you get that best from a well-written text MUD, where your imagination provides the details and lets you enter the MUD world, then by all means play in, and try to extend the possibilities of, the text MUDs. But, please keep in mind that other people work in different ways. When I play a game, immersion simply doesn't happen. What I like doing is being in control to the extent that I understand what I need to do in the world. And, what I really like to do is explore. I like to see what is there, what the builder's imaginations have come up with. My enjoyment of that is often badly disrupted by the all-too-common mispellings, bad grammar, horrible formatting, etc. My mind is too picky about the details to be able to ride over them and figure out what the builder was trying to get at. My hope is that with graphics, and a display engine that doesn't glitch, I won't have that problem. With a pure polygon based engine (i.e. *no* bitmap frames), I should get a display that doesn't disrupt me, and so hopefully get some of the immersion that you already do. On the technical issues, yes the couple of Meg for graphics and sound verus the 1K or so for text does sound like a big difference. What I had always envisioned is a MUD which requires a CD on the client machine. The big stuff (models of the objects, monsters, etc.; textures, sounds, music scores) would be on that CD, and the client engine would generate the multimedia show from that and from much smaller dynamic stuff sent from the server (possibly in the form of some kind of script). Think of the scripts for a play, that say in very general terms what actions are to happen, what lines actors say, what the music score is, etc. That's the kind of information I see the server dynamically creating and shipping to the client. With a setup like that, the user could even customize things. You could create your own modified model of the dragon, so it looks more like what you think a dragon ought to look like. (There are some problems with that, such as consistency of world events between client and server, but I'll ignore those.) And I agree, that we probably won't see anything like this soon. The CPU power to do it should arrive in not too big a time, but the human resources to set up a system that can do this, and to build a good world on top of it, may not be forthcoming. -- Chris Gray cg#ami-cg,GraySage.Edmonton.AB.CA </PRE> <!--X-Body-of-Message-End--> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <HR> <ul compact><li><strong>Follow-Ups</strong>: <ul> <li><strong><A NAME="00317" HREF="msg00317.html">Re: [MUD-Dev] The impact of the web on muds</A></strong> <ul compact><li><em>From:</em> Michael Hohensee <michael#sparta,mainstream.net></li></ul> </UL></LI></UL> <!--X-Follow-Ups-End--> <!--X-References--> <!--X-References-End--> <!--X-BotPNI--> <UL> <LI>Prev by Date: <STRONG><A HREF="msg00314.html">Re: [MUD-Dev] OT: Socket programming - platform specific</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg00316.html">Re: [MUD-Dev] The impact of the web on muds</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg00309.html">Re: [MUD-Dev] The impact of the web on muds</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg00317.html">Re: [MUD-Dev] The impact of the web on muds</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="index.html#00315"><STRONG>Date</STRONG></A></LI> <LI><A HREF="thread.html#00315"><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] The impact of the web on muds</STRONG>, <EM>(continued)</EM> <ul compact> <LI><strong><A NAME="00282" HREF="msg00282.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Mike Sellers <a href="mailto:mike#online-alchemy,com">mike#online-alchemy,com</a>, Thu 22 Jan 1998, 16:26 GMT </LI> <LI><strong><A NAME="00292" HREF="msg00292.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Fri 23 Jan 1998, 07:04 GMT </LI> <LI><strong><A NAME="00296" HREF="msg00296.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Fri 23 Jan 1998, 15:49 GMT <UL> <LI><strong><A NAME="00309" HREF="msg00309.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Caliban Tiresias Darklock <a href="mailto:caliban#darklock,com">caliban#darklock,com</a>, Sun 25 Jan 1998, 07:11 GMT </LI> </UL> </LI> <LI><strong><A NAME="00315" HREF="msg00315.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Sun 25 Jan 1998, 18:55 GMT <UL> <LI><strong><A NAME="00317" HREF="msg00317.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Michael Hohensee <a href="mailto:michael#sparta,mainstream.net">michael#sparta,mainstream.net</a>, Sun 25 Jan 1998, 22:43 GMT </LI> </UL> </LI> <LI><strong><A NAME="00316" HREF="msg00316.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Mike Sellers <a href="mailto:mike#online-alchemy,com">mike#online-alchemy,com</a>, Sun 25 Jan 1998, 20:05 GMT </LI> <LI><strong><A NAME="00321" HREF="msg00321.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Mon 26 Jan 1998, 15:49 GMT <UL> <LI><strong><A NAME="00329" HREF="msg00329.html">Re: [MUD-Dev] The impact of the web on muds</A></strong>, Miroslav Silovic <a href="mailto:silovic#zesoi,fer.hr">silovic#zesoi,fer.hr</a>, Tue 27 Jan 1998, 12:27 GMT </LI> </UL> </LI> </ul> </LI> </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>