[Home] [Groups] - Message: [Prev in Group] [Next in Group]
5220: Delivery Notification: Delivery has failed
[Full Header] [Plain Text]
From: PMDF e-Mail Interconnect <postmaster@nova.wright.edu>
Newsgroups: nu.kanga.list.mud-dev
Date: Sat, 10 Jan 1998 01:56:04 -0500 (EST)
Organization: Kanga.Nu
--Boundary_(ID_IIcS8PYuNiX87FgM5dCsMg)
Content-type: text/plain
This report relates to a message you sent with the following header fields:
Message-id: <199801100645.AAA17073@dfw-ix2.ix.netcom.com>
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
--Boundary_(ID_IIcS8PYuNiX87FgM5dCsMg)
Content-type: message/DELIVERY-STATUS
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
--Boundary_(ID_IIcS8PYuNiX87FgM5dCsMg)
Content-type: MESSAGE/RFC822
Return-path: mud-dev@null.net
Received: from nova.wright.edu by nova.wright.edu (PMDF V5.1-10 #12548)
id <01IS70TQ5Y6O8ZEDFB@nova.wright.edu> (original mail from mud-dev@null.net)
; Sat, 10 Jan 1998 01:56:04 EST
Received: from out5.ibm.net by nova.wright.edu (PMDF V5.1-10 #12548)
with ESMTP id <01IS70TM6I2S8ZEKW9@nova.wright.edu>; Sat,
10 Jan 1998 01:55:51 EST
Received: from shadow.null.net
(slip129-37-92-108.mi.us.ibm.net [129.37.92.108]) by out5.ibm.net
(8.8.5/8.6.9) with SMTP id GAA57990; Sat, 10 Jan 1998 06:54:55 +0000 (GMT)
Received: from shadow.null.net ( [10.0.0.1] )
by shadow.null.net (Hethmon Brothers Smtpd) ; Fri,
09 Jan 1998 22:49:51 +0000 (PST8PDT)
Received: from fred.globecomm.net [207.51.48.31] by in7.ibm.net id
884414401.76934-1 ; Sat, 10 Jan 1998 06:40:01 +0000
Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2])
by fred.globecomm.net (8.8.8/8.8.0) with ESMTP id BAA08808 for
<mud-dev@null.net>; Sat, 10 Jan 1998 01:41:57 -0500 (EST)
Received: (from smap@localhost) by dfw-ix2.ix.netcom.com (8.8.4/8.8.4)
id AAA17073 for <mud-dev@null.net>; Sat, 10 Jan 1998 00:45:57 -0600 (CST)
Received: from ely-oh4-08.ix.netcom.com(206.216.59.136)
by dfw-ix2.ix.netcom.com via smap (V1.3) id rma017057; Sat Jan 10 00:45:42 1998
Date: Fri, 09 Jan 1998 22:49:40 +0000 (PST8PDT)
From: "Jon A. Lambert" <jlsysinc@ix.netcom.com>
Subject: [MUD-Dev] Unique items
In-reply-to: <34B734CD.8C2@dial.pipex.com>
Sender: mud-dev <mud-dev@null.net>
To: mud-dev@null.net
Reply-to: mud-dev@null.net
Message-id: <199801100645.AAA17073@dfw-ix2.ix.netcom.com>
Organization: JL Systems, Inc.
MIME-version: 1.0
X-Mailer: Pegasus Mail for Win32 (v2.54)
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
X-OldDate: Sat, 10 Jan 1998 01:48:08 -4
Comments: Authenticated sender is <jlsysinc@popd.ix.netcom.com>
X-Listname: mud-dev@null.net
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
--Boundary_(ID_IIcS8PYuNiX87FgM5dCsMg)--