<!-- MHonArc v2.4.4 -->
<!--X-Subject: Re: [MUD-Dev] There can be.. only ONE! -->
<!--X-From-R13: [ngg Qunggreyrl <znggNzcp.qla.zy.bet> -->
<!--X-Date: Sun, 19 Apr 1998 14:57:55 +0000 -->
<!--X-Message-Id: Pine.LNX.3.96.980419154823.656A-100000#mpc,dyn.ml.org -->
<!--X-Content-Type: text/plain -->
<!--X-Reference: 199804180020.RAA174204#under,engr.sgi.com -->
<!--X-Head-End-->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html>
<head>
<title>MUD-Dev message, Re: [MUD-Dev] There can be.. only ONE!</title>
<!-- meta name="robots" content="noindex,nofollow" -->
<link rev="made" href="mailto:matt#mpc,dyn.ml.org">
</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="msg00211.html">Previous</a>
| <a href="msg00213.html">Next</a>
]
Thread:
[ <a href="msg00784.html">Previous</a>
| <a href="msg00216.html">Next</a>
]
Index:
[ <A HREF="author.html#00212">Author</A>
| <A HREF="#00212">Date</A>
| <A HREF="thread.html#00212">Thread</A>
]
<!--X-TopPNI-End-->
<!--X-MsgBody-->
<!--X-Subject-Header-Begin-->
<H1>Re: [MUD-Dev] There can be.. only ONE!</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] There can be.. only ONE! </LI>
<LI><em>From</em>: Matt Chatterley <<A HREF="mailto:matt#mpc,dyn.ml.org">matt#mpc,dyn.ml.org</A>></LI>
<LI><em>Date</em>: Sun, 19 Apr 1998 15:57:17 +0000 (GMT)</LI>
<LI><em>Reply-To</em>: <A HREF="mailto:neddy#itl,net">neddy#itl,net</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 Fri, 17 Apr 1998, J C Lawrence wrote:
> On Fri, 17 Apr 1998 15:36:38 PST8PDT
> Matt Chatterley<matt#mpc,dyn.ml.org> wrote:
> > On Thu, 16 Apr 1998, J C Lawrence wrote:
> >> On Wed, 15 Apr 1998 19:27:02 PST8PDT Matt
> >> Chatterley<matt#mpc,dyn.ml.org> wrote:
[Snip]
> >> The result is that from a player perspective the world has a chance
> >> of totally changing all about them every twenty minutes, but they
> >> are guaranteed that *within* that 20 minute period the world will
> >> remain relatively constant. This effectively fracts the game into
> >> segments each a multiple of 20 minutes long, each segment being
> >> based on a new world map.
>
> > Hmm, quite interesting.
>
> The intentions is to emphasise the ability of the players to adapt and
> quickly orient to become most rapidly combat ready. In such a world a
> tightly coordinated *team* of such players would be a fearsome
> opponent.
Very much so. You rapidly switch the situation which they are in, and then
leave it for a period of time. Their ability to react to the changes,
reorganise, be able to defend themselves, and then be able to go hunting.
Good coordination becomes key.
> Thought: Possibility of dividing team kills among members? Straight
> division of kill count by membership poses obvious problems (I join
> successful team and then go hide for the duration: I still profit.).
> Possibly divving or awarding kills among all team members within a
> radius defined by the victim's score?
Ahh, but if the information about the kill is made public to that team,
say via their comm-system, whatever it is (after all, we are taking
reasonable liberties with reality already - take another one to improve
this):
%101hz%: UggUgg slays Ooble, bringing glory to the team!
Then UggUggs points for killing his victim are divided amidst the team. If
certain team members are not seen, and never named, other members may
decide that a spot of 'justice' is in order, and evict them forcefully.
OTOH perhaps players who are nearby etc and appear to have been giving an
'assist' should also be named. Hmm, perhaps just giving points to those is
a good idea..
> > The system will certainly be coordinate based, and may or may not
> > use a custom client (completely undecided - the first incarnations
> > will probably work with any telnet-happy thing). My next question,
> > or issue to resolve relates to how to tackle placing players when
> > they enter the game - from a safe room into random coordinates?
>
> First thought: Throw the players into the game at a couple miles of
> altitude. Give them crude trajectory controls. Have impact/landing
> generally not be fatal (or if fatal, non penalising). this gives the
> new player an instant physical world context.
Heh, heh, heh. I quite like this. Or perhaps make them parachute down. And
pull the cord themselves. An instant impression that the world is as cruel
and unforgiving as the concrete that paves it? ;)
> >> I'd be more tempted to do an equation ala:
> >>
> >> The power of a newly popped weapon is inversely proportional to the
> >> time remaining to the current world map _IF_ the map is due to
> >> change next cycle, and is otherwise constant/pre-set.
> >>
> >> The result would be that players in the final minutes of a world's
> >> life would be toting planet busters, a few minutes before that a
> >> few-dozen-megaton nukes, and etc on down. This also gives the chap
> >> who manages to find the "ultimate" weapon in the last 30 seconds of
> >> the world-life the chance to kill *EVERYBODY* in one single trigger
> >> pull.
>
> > Yeah. Given a continuous world, and assuming I go with the
> > 'basically human' players and weapons/equipment (as opposed to an
> > idea which KaVir sparked - 'robot' players who collect 'add-ons'),
> > I'm not sure how I'd approach this.
>
> You're still going to grow/shrink the world with population changes?
> Are those world growths going to be gradual or sudden? You can
> probably figure some way to still key that to the propulation change
> mechanics.
Good idea. Since I decided to ditch a room base in favour of coordinates,
doing things like this has become so much easier that it is no longer a
technical consideration, but purely a game-design one. Still debating the
sort of game - really between something 'multidimensional' (aka several
zones, different weapons which only work in certain zones..) and above
named robot theme. The latter captures my imagination more. :)
> >> Ahh, but older well established players who are members of
> >> successful teams are ALSO anonymous to members of different
> >> teams...
>
> > Yup. Everyone should be anonymous to begin with, and in general. I
> > quite like the 'account' separate from PC approach, although this
> > causes problems with maintaing teams. Hmm.
>
> Nahh. Everybody is *ALWAYS* anonymous _except_ to members of their
> own team.
So the notion of 'names' doesnt even exist, except within teams?
> Note: In reaction to Raph's recent UOL tales: Allow team members to
> (optionally) have clearly visible (to all, not just team members) tags
> as to their affiliation: arm bands, uniforms, body-types, floating
> bubbles...
Yeah. I'm thinking along the lines of putting most of the 'game
configuration' from the player side into teams.. Quake 'skins' and so
forth are hugely popular..
> > Although theres nothing bad about them being targets, it would be
> > 'bad' (from some points of view, I suppose) for them to be targets
> > *to a greater extent* than anyone else. :)
>
> That's why everyone is anonymous to all but team members. The above
> extra ID characteristics would make those teams that adopt them
> definite identifiers, making them targets -- but some might like that
> discinction.
Right.
[Snip rest]
--
Regards,
-Matt Chatterley
Spod: <A HREF="http://user.super.net.uk/~neddy/spod/spod.html">http://user.super.net.uk/~neddy/spod/spod.html</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="00216" HREF="msg00216.html">[MUD-Dev] Re: There can be.. only ONE!</A></strong>
<ul compact><li><em>From:</em> J C Lawrence <claw#under,engr.sgi.com></li></ul>
</UL></LI></UL>
<!--X-Follow-Ups-End-->
<!--X-References-->
<UL><LI><STRONG>References</STRONG>:
<UL>
<LI><STRONG><A NAME="00208" HREF="msg00208.html">Re: [MUD-Dev] There can be.. only ONE!</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="msg00211.html">Re: [MUD-Dev] There can be.. only ONE!</A></STRONG>
</LI>
<LI>Next by Date:
<STRONG><A HREF="msg00213.html">Re: [MUD-Dev] There can be.. only ONE!</A></STRONG>
</LI>
<LI>Prev by thread:
<STRONG><A HREF="msg00784.html">[MUD-Dev] Re: There can be.. only ONE!</A></STRONG>
</LI>
<LI>Next by thread:
<STRONG><A HREF="msg00216.html">[MUD-Dev] Re: There can be.. only ONE!</A></STRONG>
</LI>
<LI>Index(es):
<UL>
<LI><A HREF="index.html#00212"><STRONG>Date</STRONG></A></LI>
<LI><A HREF="thread.html#00212"><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] There can be.. only ONE!</STRONG>, <EM>(continued)</EM>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<ul compact>
<LI><strong><A NAME="00208" HREF="msg00208.html">Re: [MUD-Dev] There can be.. only ONE!</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Sat 18 Apr 1998, 00:20 GMT
<UL>
<LI><strong><A NAME="00211" HREF="msg00211.html">Re: [MUD-Dev] There can be.. only ONE!</A></strong>,
Ling <a href="mailto:K.L.Lo-94#student,lboro.ac.uk">K.L.Lo-94#student,lboro.ac.uk</a>, Sun 19 Apr 1998, 13:54 GMT
<UL>
<LI><strong><A NAME="00213" HREF="msg00213.html">Re: [MUD-Dev] There can be.. only ONE!</A></strong>,
Matt Chatterley <a href="mailto:matt#mpc,dyn.ml.org">matt#mpc,dyn.ml.org</a>, Sun 19 Apr 1998, 15:01 GMT
</LI>
<LI><strong><A NAME="00784" HREF="msg00784.html">[MUD-Dev] Re: There can be.. only ONE!</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Wed 22 Apr 1998, 18:49 GMT
</LI>
</UL>
</LI>
<LI><strong><A NAME="00212" HREF="msg00212.html">Re: [MUD-Dev] There can be.. only ONE!</A></strong>,
Matt Chatterley <a href="mailto:matt#mpc,dyn.ml.org">matt#mpc,dyn.ml.org</a>, Sun 19 Apr 1998, 14:57 GMT
<UL>
<LI><strong><A NAME="00216" HREF="msg00216.html">[MUD-Dev] Re: There can be.. only ONE!</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Wed 22 Apr 1998, 18:56 GMT
</LI>
</UL>
</LI>
</UL>
</LI>
<LI><strong><A NAME="00585" HREF="msg00585.html">[MUD-Dev] Re: There can be.. only ONE!</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Wed 22 Apr 1998, 18:33 GMT
</LI>
</ul>
</ul>
</ul>
</ul>
</ul>
</LI>
<LI><strong><A NAME="00135" HREF="msg00135.html">Personality modelling</A></strong>,
Oliver Jowett <a href="mailto:oliver#jowett,manawatu.planet.co.nz">oliver#jowett,manawatu.planet.co.nz</a>, Sun 12 Apr 1998, 00:36 GMT
<UL>
<LI><strong><A NAME="00166" HREF="msg00166.html">Re: [MUD-Dev] Personality modelling</A></strong>,
J C Lawrence <a href="mailto:claw#under,engr.sgi.com">claw#under,engr.sgi.com</a>, Wed 15 Apr 1998, 01:14 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>
