<!-- MHonArc v2.4.4 -->
<!--X-Subject: [MUD-Dev] Re: mobile movement -->
<!--X-From-R13: Zvat <Y.Z.Zb-94Nfghqrag.yobeb.np.hx> -->
<!--X-Date: Sun, 17 Jan 1999 04:44:12 -0800 -->
<!--X-Message-Id: Pine.SOL.3.96.990117121827.1362B-100000@sun-cc203 -->
<!--X-Content-Type: text/plain -->
<!--X-Reference: 199901132233.OAA25953#under,engr.sgi.com -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, [MUD-Dev] Re: mobile movement</title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:K.L.Lo-94#student,lboro.ac.uk">
</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="msg00214.html">Previous</a>
| <a href="msg00216.html">Next</a>
]
Thread:
[ <a href="msg00141.html">Previous</a>
| <a href="msg00133.html">Next</a>
]
Index:
[ <A HREF="author.html#00215">Author</A>
| <A HREF="#00215">Date</A>
| <A HREF="thread.html#00215">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>[MUD-Dev] Re: mobile movement</H1>
<HR>
<!--X-Subject-Header-End-->
<!--X-Head-of-Message-->
<UL>
<LI><em>To</em>: <A HREF="mailto:mud-dev#kanga,nu">mud-dev#kanga,nu</A></LI>
<LI><em>Subject</em>: [MUD-Dev] Re: mobile movement </LI>
<LI><em>From</em>: Ling <<A HREF="mailto:K.L.Lo-94#student,lboro.ac.uk">K.L.Lo-94#student,lboro.ac.uk</A>></LI>
<LI><em>Date</em>: Sun, 17 Jan 1999 12:44:03 +0000 (BST)</LI>
<LI><em>Reply-To</em>: <A HREF="mailto:mud-dev#kanga,nu">mud-dev#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 Wed, 13 Jan 1999, J C Lawrence wrote:
> On Wed, 13 Jan 1999 01:33:30 +0000 (BST)
> Ling <K.L.Lo-94#student,lboro.ac.uk> wrote:
>
> > On Tue, 12 Jan 1999, J C Lawrence wrote:
[snip snip! recap: stuff about highways]
> An even cheaper solution, generalised for room and coordinate
> systems:
>
> 1) Quantise your world into cells. If you run a room based world,
> rooms are your cells. If you're coordinate based, use any
> convenient tesselating shape shape that maps cheaply to your world
> You can even vary the tesselation type as needed. The key
> requirements are that it MUST be cheap to devolve an arbitrary
> location into a cell reference, and it must be cheap to maintain a
> simple DB under that reference.
Do you quantise your co-ord based mud world into cells at the moment? If
so, are they oblong cells or irregular 3D blobs? How do you store mana
density? On a domain basis? Or do they look like globes, pin pricks in
space with a radius and falloff?
> 2) Upon an object (say player character) entering a cell a tuple
> is created which contains an ObjectID, EntryDirection, and
> EntryTimestamp. This tuple can be hung off the object (as versus
> the cell). If the tuple is hung off the object then the ObjectId is
> not needed.
>
> 3) Upon an object leaving a cell, the above (#2) tuple is
> extracted and an ExitDirection and ExitTimeStamp added. The
> resulting tuple defines a vector, a speed and an owner.
>
> 4) Merge the tuple from #3 with a DB of such tuples hung off the
> cell reference. The result of the merge would be a vector and an
> associated list of timestamped ObjectID's. A rolling average can
> also be stored for each vector indicating the average transition
> speed of that vector (this has other more interesting uses unrelated
> to path finding).
Oh? Please enlighten!
> 5) Post-processing would remove older tuple sets from the cell DB,
> merging them into a single meta-set with an anonymous
> objectID/timestamp.
>
> 6) The meta-set in #5 would have a controlled decay rate
> (approaches zero in known time) which wuold computed and stored upon
> query by remote client or #5.
After some thought, the average for two vectors in opposite directions is
zero. This wouldn't be much of a problem for a true crossroad with four
directions and players running up, down, left and right. The above would
indicate any cell to have no net drift (assuming statistically players
will go from A to B as often as they go from B to A by foot).
Unfortunately, I have no great thoughts upon a solution to this possible
problem. I suppose it's all down to the post-processing data merging bit,
step #5. A good algorithm that will extract discrete directions players
tend to go is needed here.
> Now to create a highway or even path-to-object map starts to be
> pretty trivial and computation light (if data heavy):
>
> a) Get DB set for starting location.
> b) Get DB for target location.
> c) Select an arbitrary "path weight", where a path weight is the
> number of DB entries for a particular vector in a given cell.
> d) Build a graph of cells, starting from the starting location,
> and following and considering only vectors with a weight equal to or
> higher than the threshhold path weight.
> e) Simultaneously build a parallel graph, starting from the target
> location.
> f) Upon finding an intersection of the two graphs (hash tables are
> your friends), the minimised path route (ordered by maximum sum
> velocity from #4) is your path from source to target.
> g) You can of course continue growing the graphs and even store
> them globally for general reference.
Looks like a very large weather map. Npcs move with the grace of airships
in a very strong hurricane.
Another random thought I had. Link mana to be inversely proportional to
the traffic in a cell. Think of it as players leaving a wake in the mana
ocean. It'll make popular spots and highways contain less mana and
possibly safer places. Players will also find they're forced to go look
for new, exciting places while I'll refuse to come out of my cubby hole.
Side effect is that you could use the wake as a method to track people
down. Buzzing cities will have very little mana whilst the quiet village
will still have a good amount. It'll also make armies useful against
mages provided they can overrun the mana ocean (mages, never pick a fight
with an army on their home turf).
| Ling Lo (aka Stressed Lad)
_O_O_ kllo#iee,org
</PRE>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<HR>
<!--X-Follow-Ups-End-->
<!--X-References-->
<UL><LI><STRONG>References</STRONG>:
<UL>
<LI><STRONG><A NAME="00141" HREF="msg00141.html">[MUD-Dev] Re: mobile movement</A></STRONG>
<UL><LI><EM>From:</EM> J C Lawrence <claw#under,engr.sgi.com></LI></UL></LI>
</UL></LI></UL>
<!--X-References-End-->
<!--X-BotPNI-->
<UL>
<LI>Prev by Date:
<STRONG><A HREF="msg00214.html">[MUD-Dev] Re: Reputations, More Mazes</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00216.html">[MUD-Dev] Matrix Game</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00141.html">[MUD-Dev] Re: mobile movement</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00133.html">[MUD-Dev] Re: mobile movement</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00215"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00215"><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>[MUD-Dev] Re: mobile movement</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<ul compact>
<LI><strong><A NAME="00120" HREF="msg00120.html">[MUD-Dev] Re: mobile movement</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Wed 13 Jan 1999, 00:21 GMT
<UL>
<LI><strong><A NAME="00126" HREF="msg00126.html">[MUD-Dev] Re: mobile movement</A></strong>,
Ling <a href="mailto:K.L.Lo-94#student,lboro.ac.uk">K.L.Lo-94#student,lboro.ac.uk</a>, Wed 13 Jan 1999, 01:33 GMT
<UL>
<LI><strong><A NAME="00128" HREF="msg00128.html">[MUD-Dev] Re: mobile movement</A></strong>,
Marc Hernandez <a href="mailto:marc#ias,jb.com">marc#ias,jb.com</a>, Wed 13 Jan 1999, 04:26 GMT
</LI>
<LI><strong><A NAME="00141" HREF="msg00141.html">[MUD-Dev] Re: mobile movement</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Wed 13 Jan 1999, 22:33 GMT
<UL>
<LI><strong><A NAME="00215" HREF="msg00215.html">[MUD-Dev] Re: mobile movement</A></strong>,
Ling <a href="mailto:K.L.Lo-94#student,lboro.ac.uk">K.L.Lo-94#student,lboro.ac.uk</a>, Sun 17 Jan 1999, 12:44 GMT
</LI>
</UL>
</LI>
</UL>
</LI>
<LI><strong><A NAME="00133" HREF="msg00133.html">[MUD-Dev] Re: mobile movement</A></strong>,
Holly Sommer <a href="mailto:hsommer#micro,ti.com">hsommer#micro,ti.com</a>, Wed 13 Jan 1999, 16:13 GMT
</LI>
</UL>
</LI>
</ul>
</ul>
<LI><strong><A NAME="00129" HREF="msg00129.html">[MUD-Dev] Re: mobile movement</A></strong>,
Chris Gray <a href="mailto:cg#ami-cg,GraySage.Edmonton.AB.CA">cg#ami-cg,GraySage.Edmonton.AB.CA</a>, Wed 13 Jan 1999, 05:25 GMT
</LI>
<LI><strong><A NAME="00135" HREF="msg00135.html">[MUD-Dev] Re: mobile movement</A></strong>,
Caliban Tiresias Darklock <a href="mailto:caliban#darklock,com">caliban#darklock,com</a>, Wed 13 Jan 1999, 18:22 GMT
</LI>
<LI><strong><A NAME="00137" HREF="msg00137.html">[MUD-Dev] Re: mobile movement</A></strong>,
Koster, Raph <a href="mailto:rkoster#origin,ea.com">rkoster#origin,ea.com</a>, Wed 13 Jan 1999, 18:55 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>