<!-- MHonArc v2.4.4 -->
<!--X-Subject: Delivery Notification: Delivery has failed -->
<!--X-From-R13: B[RT r-[nvy Wagrepbaarpg <cbfgznfgreNabin.jevtug.rqh> -->
<!--X-Date: Sat, 10 Jan 1998 06:55:42 +0000 -->
<!--X-Message-Id: 01IS70TY8SMU8ZEDFB#nova,wright.edu -->
<!--X-Content-Type: multipart/report -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, Delivery Notification: Delivery has failed</title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:postmaster#nova,wright.edu">
</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="msg00173.html">Previous</a>
| <a href="msg00175.html">Next</a>
]
Thread:
[ <a href="msg00172.html">Previous</a>
| <a href="msg00176.html">Next</a>
]
Index:
[ <A HREF="author.html#00174">Author</A>
| <A HREF="#00174">Date</A>
| <A HREF="thread.html#00174">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>Delivery Notification: Delivery has failed</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>: Delivery Notification: Delivery has failed</LI>
<LI><em>From</em>: PMDF e-Mail Interconnect <<A HREF="mailto:postmaster#nova,wright.edu">postmaster#nova,wright.edu</A>></LI>
<LI><em>Date</em>: Sat, 10 Jan 1998 01:56:04 -0500 (EST)</LI>
</UL>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<HR>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<PRE>
This report relates to a message you sent with the following header fields:
Message-id: <<A HREF="msg00173.html">199801100645.AAA17073#dfw-ix2,ix.netcom.com</A>>
Date: Fri, 09 Jan 1998 22:49:40 +0000 (PST8PDT)
From: "Jon A. Lambert" <jlsysinc#ix,netcom.com>
To: mud-dev#null,net
Subject: [MUD-Dev] Unique items
Your message cannot be delivered to the following recipients:
Recipient address: s006jbh#nova,wright.edu
%MAIL-E-OPENOUT, error opening !AS as output
-RMS-E-CRE, ACP file create failed
-SYSTEM-F-EXDISKQUOTA, disk quota exceeded
</PRE>
<PRE>
Original-envelope-id: 01IS70TMAUFA8ZEKW9#nova,wright.edu
Reporting-MTA: dns; nova.wright.edu
Action: failed
Status: 5.0.0
Original-recipient: rfc822;s006jbh#nova,wright.edu
Final-recipient: rfc822;s006jbh#nova,wright.edu
</PRE>
<BLOCKQUOTE><BR><HR ALIGN="LEFT" WIDTH="80%">
<UL>
<LI><em>To</em>: <A HREF="mailto:mud-dev#null,net">mud-dev#null,net</A></LI>
<LI><em>Subject</em>: [MUD-Dev] Unique items</LI>
<LI><em>From</em>: "Jon A. Lambert" <<A HREF="mailto:jlsysinc#ix,netcom.com">jlsysinc#ix,netcom.com</A>></LI>
<LI><em>Date</em>: Fri, 09 Jan 1998 22:49:40 +0000 (PST8PDT)</LI>
<LI><em>Comments</em>: Authenticated sender is <jlsysinc#popd,ix.netcom.com></LI>
<LI><em>Reply-to</em>: <A HREF="mailto:mud-dev#null,net">mud-dev#null,net</A></LI>
<LI><em>Sender</em>: mud-dev <<A HREF="mailto:mud-dev#null,net">mud-dev#null,net</A>></LI>
</UL>
<PRE>
On 9 Jan 98 at 15:51, Richard Woolcock wrote:
> Vadim Tkachenko wrote:
> >
> > I've been playing with a different idea - make unique/restricted items
> > change their properties - an example:
> >
> > - There's a door, you really need to open it to get some big reward.
> > - There's the key, and the only one.
> > - You accidently found it, or killed somebody who had it in possession,
> > [optional] you found the door.
> > - (to simplify) the further you from the given door, the heavier the key
> > becomes, so you either are forced to go in a right direction (btw, not
> > nessessarily, thus it becomes more compelling to solve the quest of
> > finding the right door), or drop the damned no-good thing.
> >
> > 'course, there are exceptions like above - one-way actions like dropping
> > into ocean, which should be resolved separately.
>
> (Hmmm this reminds me of Lord of the Rings :)
>
> But the Key had a will of its own, and way of slipping from one person,
> only to be found by another.
>
> Two friends were fishing in the ocean one day...
>
Funny, this reminded me of _the ring_ also. :)
It's a rather wonderful idea.
Cursed items and intelligent swords also come to mind.
[snip]
> My character descriptions are automatically generated according to eyes,
> hair and appearance. What I think would be really nice is if equipment
> descriptions could be incorporated into the description as well (rather
> than showing a description followed by a huge list of objects), so that
> you might get something like:
>
> [look woman
> She looks absolutely beautiful, with soft brown eyes and long, curly
> black hair which reaches down to her waist. She is wearing a torn
> pair of tight-fitting black jeans, fastened at the waist with a brown
> leather belt. A shredded and blood stained white shirt barely covers
> her body, and beneath it you can make out a ripped black silk bra and
> several painful-looking wounds, one of which is still leaking blood.
> In one hand she holds a slightly-notched steel knife, while in the
> other is a lit silver lantern.
>
> The main trouble is people who wear lots of equipment, which could
> result in very long (and silly looking) descriptions. I'm trying to
> decide if this would be a good thing to code, or just not worth it
> in the long run. Has anyone got any better ways of doing this that
> they might suggest?
>
Shouldn't the above example description get better as the equipment
is removed? :PP
Seriously, though, this is how I handle it:
I have properties in the objects which indicate their coverage area
or wear location (sound familar :> ) except my wear locations are
dependent upon the anatomy that the object was design for. Multiple
areas of coverage can occur. Thus, the pants cover both thighs and
lower legs, lower abdomen and rear. Each object has a transparency
property; transparent, translucent or opaque. I allow 4 layers and
they are described from the outermost to inner most, being blocked
or modified by the transparency property or described differently
when partially blocked by lesser coverage of outer layered objects.
The fair lady, above, might be hiding a small gun strapped to her
left lower leg, might be wearing some rather interesting undergarments
and sporting an "I love Bubba" tattoo on her rear.
Some others have discussed areas of perception or what would be
noticed on brief examination both solo and from the crowd perspective.
Or the order in which things get noticed depending of the level of
examination, the unusual, cultural and gender, yada, yada.
For instance if the lady above was wearing a clown mask, it might be
the first thing described or only item noticed in a casual examination.
How would you describe the above character or any other that was
wearing NO equipment? A problem? Would the system merely point
out that the character is nude, or would it go for anatomical
accuracy? Or would you allow the player to decribe and choose
the descriptions of all their character parts in addition to hair,
eyes, etc.? If so, what would be the average male organ size be
on the mud? <hehe> Would decription comparisons become an amusing
or disgusting mud sport? (Yikes, visions of Bubba the Troll showing
a full moon)
I think it is essential to the style of game I'm striving for.
A player's _equipment_ is geared to social interaction or acting
out a role instead of combat. Even on a hack-n-slash game I
believe their would be great interest in showing off scars and
tatoos. For a Cyberpunk world, accessories are a must.
The rudiments of my wear location system can be found on my lame
and sparse web page at: <http:\\www.netcom.com\~jlsysinc>
--
Jon A. Lambert
"Everything that deceives may be said to enchant" - Plato
</PRE>
<HR ALIGN="LEFT" WIDTH="80%"></BLOCKQUOTE><BR>
<!--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="msg00173.html">Re: [MUD-Dev] Unique items</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00175.html">Re: [MUD-Dev] Totally OT... (Or is it?) (yes it is ;)</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00172.html">Delivery Notification: Delivery has failed</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00176.html">Delivery Notification: Delivery has failed</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00174"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00174"><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] Races and stuff (was: FAQ)</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<LI><strong><A NAME="00356" HREF="msg00356.html">Re: [MUD-Dev] Races and stuff (was: FAQ)</A></strong>,
Vadim Tkachenko <a href="mailto:vadimt#4cs,com">vadimt#4cs,com</a>, Fri 30 Jan 1998, 19:31 GMT
</LI>
</ul>
</ul>
</ul>
</ul>
</LI>
<LI><strong><A NAME="00187" HREF="msg00187.html">Re: [MUD-Dev] Totally OT... (Or is it?) (yes it is ;)</A></strong>,
Mike Sellers <a href="mailto:mike#online-alchemy,com">mike#online-alchemy,com</a>, Sat 10 Jan 1998, 19:17 GMT
<UL>
<LI><strong><A NAME="00216" HREF="msg00216.html">Re: [MUD-Dev] Totally OT... (Or is it?) (yes it is ;)</A></strong>,
JC Lawrence <a href="mailto:claw#under,Eng.Sun.COM">claw#under,Eng.Sun.COM</a>, Mon 12 Jan 1998, 19:02 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00172" HREF="msg00172.html">Delivery Notification: Delivery has failed</A></strong>,
PMDF e-Mail Interconnect <a href="mailto:postmaster#nova,wright.edu">postmaster#nova,wright.edu</a>, Sat 10 Jan 1998, 04:36 GMT
<UL>
<li><Possible follow-up(s)><br>
<LI><strong><A NAME="00174" HREF="msg00174.html">Delivery Notification: Delivery has failed</A></strong>,
PMDF e-Mail Interconnect <a href="mailto:postmaster#nova,wright.edu">postmaster#nova,wright.edu</a>, Sat 10 Jan 1998, 06:55 GMT
</LI>
<LI><strong><A NAME="00176" HREF="msg00176.html">Delivery Notification: Delivery has failed</A></strong>,
PMDF e-Mail Interconnect <a href="mailto:postmaster#nova,wright.edu">postmaster#nova,wright.edu</a>, Sat 10 Jan 1998, 08:33 GMT
</LI>
<LI><strong><A NAME="00178" HREF="msg00178.html">Delivery Notification: Delivery has failed</A></strong>,
PMDF e-Mail Interconnect <a href="mailto:postmaster#nova,wright.edu">postmaster#nova,wright.edu</a>, Sat 10 Jan 1998, 15:46 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00159" HREF="msg00159.html">RE: [MUD-Dev] MUD Economy</A></strong>,
Koster, Raph <a href="mailto:rkoster#origin,ea.com">rkoster#origin,ea.com</a>, Sat 10 Jan 1998, 01:03 GMT
<UL>
<LI><strong><A NAME="00190" HREF="msg00190.html">Re: [MUD-Dev] MUD Economy</A></strong>,
Matt Chatterley <a href="mailto:root#mpc,dyn.ml.org">root#mpc,dyn.ml.org</a>, Sun 11 Jan 1998, 14:07 GMT
</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>
