<!-- MHonArc v2.4.4 -->
<!--X-Subject: Re: Re[2]: [MUD-Dev] The grass is always greener in the other field -->
<!--X-From-R13: Oqnz Ivttvaf <nqnzNnatry.pbz> -->
<!--X-Date: Tue, 21 Dec 1999 14:59:31 -0800 -->
<!--X-Message-Id: Pine.SGI.3.96.991221110646.16438F-100000@zazu.angel.com -->
<!--X-Content-Type: text/plain -->
<!--X-Reference: 16911.991220@io.com -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, Re: Re[2]: [MUD-Dev] The grass is always greener in the other </title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:adam@angel.com">
</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="msg00714.html">Previous</a>
| <a href="msg00716.html">Next</a>
]
Thread:
[ <a href="msg00705.html">Previous</a>
| <a href="msg00735.html">Next</a>
]
Index:
[ <A HREF="author.html#00713">Author</A>
| <A HREF="#00713">Date</A>
| <A HREF="thread.html#00713">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>Re: Re[2]: [MUD-Dev] The grass is always greener in the other field</H1>
<HR>
<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->
<UL>
<LI><em>To</em>: J C Lawrence <<A HREF="mailto:mud-dev#kanga,nu">mud-dev#kanga,nu</A>></LI>
<LI><em>Subject</em>: Re: Re[2]: [MUD-Dev] The grass is always greener in the other field</LI>
<LI><em>From</em>: Adam Wiggins <<A HREF="mailto:adam#angel,com">adam#angel,com</A>></LI>
<LI><em>Date</em>: Tue, 21 Dec 1999 11:33:20 -0800 (PST)</LI>
<LI><em>Reply-To</em>: <A HREF="mailto:mud-dev#kanga,nu">mud-dev#kanga,nu</A></LI>
<LI><em>Sender</em>: <A HREF="mailto:mud-dev-admin#kanga,nu">mud-dev-admin#kanga,nu</A></LI>
</UL>
<!--X-Head-of-Message-End-->
<!--X-Head-Body-Sep-Begin-->
<HR>
<!--X-Head-Body-Sep-End-->
<!--X-Body-of-Message-->
<PRE>
On Mon, 20 Dec 1999, Travis Casey wrote:
> Which may be enough, if you simply don't want someone to spam the lock
> to quickly pick it. The real problem here is not the ability to keep
> trying to pick a lock until you succeed -- it's the fact that each
> attempt takes so little time.
>
> In the real world, lockpicking is a variable activity -- sometimes
> picking a particular lock takes me just a few seconds, sometimes it
> takes me a few minutes. Almost any key-type lock can be picked by
> someone who knows how to pick locks, given sufficient time -- it's
> that time that's important, though. The longer it takes to pick a
> lock, the greater the chance is that you will be noticed.
Indeed. I set up lockpicking to be a fairly involved process, which is
also difficult and expensive to learn, and even a master takes a while
to get a given lock open. Since I'm assuming that the readership here
is a bit too laz^H^H^Hbusy to log on and see for themselves, here's
a couple of (undoctored!) transcripts:
A beginner vs. a medium-difficulty lock:
You begin picking the lock on the door with a set of tin lockpicks.
You slide one of the lockpicks into the top of the keyhole.
While pushing in the bottom pick, you fumble the top one and it slips out.
(The mechanism on this one is pretty complicated.)
You slide one of the lockpicks into the top of the keyhole.
You fumble, and a set of tin lockpicks snaps off in the lock!
A medium-skill lockpicker vs. a tough padlock:
You begin picking the lock on the door with a set of steel lockpicks.
You lift the padlock and thrust one of your lockpicks into the dark
keyhole.
Supporting the padlock with the first lockpick, you push in the second
one.
Holding the lock steady with the left pick, you twist the right one
searchingly.
You fumble and almost drop a set of steel lockpicks.
And an expert vs. a medium-difficulty lock:
You begin picking the lock on a small iron chest with a set of steel
lockpicks.
You slide one of the lockpicks into the top of the keyhole.
You slide the other lockpick into the bottom of the keyhole.
Carefully, you bend the bottom pick downwards, feeling for the latch.
There is a faint scrape as the bottom pick encounters resistance.
You push in the top pick, twisting it slowly against the release.
You hear a metalic rasp as the mechanism releases the teeth-guard.
A faint click sounds as you complete your handywork on the lock.
You gain 200 experience points.
There are a pretty decent number of variations on this theme due to
several different types of locks, lockpicks, varying skill level, size,
and agility of the characters.
> (Of course, there are also some other factors -- e.g., on some locks,
> it's possible for the pins to fall into the cylinder when the lock is
> turned 180 degrees, which may cause the mechanism to jam and require
> disassembling the lock to make it work properly again. Nonetheless,
> barring such problems, any standard lock can be picked given
> sufficient time.)
Hmmm...jamming, I hadn't thought of that! Gonna have to steal that
when I get around to improving lockpicking again.
> To my knowledge, no mud has yet tried hidden numbers and deliberately
> obscured formulas -- and while it makes no sense to assume that such
> an attempt would be 100% successful, it also makes no sense to assume
> that it would be 100% unsuccessful. We can speculate either way, but
> we won't know what would happen until someone tries it.
*shrug* That's pretty much what I do. Very little is shown in actual
numbers, but almost all "stats" on characters or objects can be determined
through various informational commands.
So far I've had little problems with players "uncovering" the formulas,
which is not surprising due to the large number of variables used in
each one. (Lockpicking, for example, takes into acount about a dozen
different variables.) If anything, the problem has been confusion over
why certain tasks are more difficult for one character than another.
For example, most players try to create large (tall/meaty) characters
since they have increased health and better range in combat. However,
this hurts almost all of the stealthy-type skills, including lockpicking.
Despite messages about "your hands are too big for this tiny little lock..."
as well as specifically mentioning the negative impact of size on stealthy
skills in the info files, most players get confused by features like
this.
> You can also fight scripting in other ways, if you want to -- e.g.,
> limiting the rate at which commands can be entered, and possibly
> queuing "extra" commands to be processed later.
I think I described my task system some time ago on this list (I seem
to recall an example involving Bubba and digging of the Panama canal),
but it's pretty much what you are describing here. It has worked
out remarkably well on many fronts, although it still has some glitchyness
(certain tasks stacking doesn't make much sense, for example).
The lockpick examples, above, show this to a certain extent, although
I didn't enter any commands during the execution to show task interruption
or queueing. Check the archives (I know I've shown examples before),
or log on and experiment with it yourself.
Adam
_______________________________________________
MUD-Dev maillist - MUD-Dev#kanga,nu
<A HREF="http://www.kanga.nu/lists/listinfo/mud-dev">http://www.kanga.nu/lists/listinfo/mud-dev</A>
</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="00735" HREF="msg00735.html">Re: Re[2]: [MUD-Dev] The grass is always greener in the other field</A></strong>
<ul compact><li><em>From:</em> J C Lawrence <claw@cp.net></li></ul>
</UL></LI></UL>
<!--X-Follow-Ups-End-->
<!--X-References-->
<UL><LI><STRONG>References</STRONG>:
<UL>
<LI><STRONG><A NAME="00705" HREF="msg00705.html">Re[2]: [MUD-Dev] The grass is always greener in the other field</A></STRONG>
<UL><LI><EM>From:</EM> Travis Casey <efindel@io.com></LI></UL></LI>
</UL></LI></UL>
<!--X-References-End-->
<!--X-BotPNI-->
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg00714.html">Re: [MUD-Dev] Fair/Unfair? Scenarios (fwd)</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00716.html">Re: [MUD-Dev] Originality/Points of Reference (was Classes and Races and more (a BIG list) (fwd))</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00705.html">Re[2]: [MUD-Dev] The grass is always greener in the other field</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00735.html">Re: Re[2]: [MUD-Dev] The grass is always greener in the other field</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00713"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00713"><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 grass is always greener in the other field</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<LI><strong><A NAME="00649" HREF="msg00649.html">RE: [MUD-Dev] The grass is always greener in the other field</A></strong>,
Adam Wiggins <a href="mailto:adam@angel.com">adam@angel.com</a>, Fri 17 Dec 1999, 23:00 GMT
</LI>
<LI><strong><A NAME="00658" HREF="msg00658.html">RE: [MUD-Dev] The grass is always greener in the other field</A></strong>,
Ian Macintosh <a href="mailto:iman@issystems.co.nz">iman@issystems.co.nz</a>, Sat 18 Dec 1999, 04:26 GMT
<UL>
<LI><strong><A NAME="00666" HREF="msg00666.html">Re: [MUD-Dev] The grass is always greener in the other field</A></strong>,
J C Lawrence <a href="mailto:claw@kanga.nu">claw@kanga.nu</a>, Sat 18 Dec 1999, 06:37 GMT
<UL>
<LI><strong><A NAME="00705" HREF="msg00705.html">Re[2]: [MUD-Dev] The grass is always greener in the other field</A></strong>,
Travis Casey <a href="mailto:efindel@io.com">efindel@io.com</a>, Tue 21 Dec 1999, 17:38 GMT
<UL>
<LI><strong><A NAME="00713" HREF="msg00713.html">Re: Re[2]: [MUD-Dev] The grass is always greener in the other field</A></strong>,
Adam Wiggins <a href="mailto:adam@angel.com">adam@angel.com</a>, Tue 21 Dec 1999, 22:59 GMT
<UL>
<LI><strong><A NAME="00735" HREF="msg00735.html">Re: Re[2]: [MUD-Dev] The grass is always greener in the other field</A></strong>,
J C Lawrence <a href="mailto:claw@cp.net">claw@cp.net</a>, Wed 22 Dec 1999, 23:16 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00733" HREF="msg00733.html">Re: Re[2]: [MUD-Dev] The grass is always greener in the other field</A></strong>,
J C Lawrence <a href="mailto:claw@cp.net">claw@cp.net</a>, Wed 22 Dec 1999, 23:02 GMT
<UL>
<LI><strong><A NAME="00744" HREF="msg00744.html">RE: Re[2]: [MUD-Dev] The grass is always greener in the other field</A></strong>,
Joe Andrieu <a href="mailto:joe@andrieu.net">joe@andrieu.net</a>, Thu 23 Dec 1999, 00:45 GMT
</LI>
<LI><strong><A NAME="00754" HREF="msg00754.html">Re[4]: [MUD-Dev] The grass is always greener in the other field</A></strong>,
Travis Casey <a href="mailto:efindel@io.com">efindel@io.com</a>, Thu 23 Dec 1999, 05:39 GMT
</LI>
</UL>
</LI>
</UL>
</LI>
</UL>
</LI>
</UL>
</LI>
</ul>
</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>