[MUD-Dev] Re: Levelless MUDs
Adam Wiggins
adam at angel.com
Thu Jun 18 11:39:53 CEST 1998
On Tue, 16 Jun 1998, J C Lawrence wrote:
> Adam Wiggins<adam at angel.com> wrote:
> > [Holly:]
> >> How do you handle things like spells, where caster vs. target
> >> level is what determines effectiveness?
>
> > Lots and lots of skills. Ie: Biffy's fireball at Bubba is a roll of
> > Biffy's spellcasting skill, Biffy's fire-realm skill, Bubba's
> > spellcraft knowledge skill, Bubba's dodge skill, Bubba's agility,
> > Biffy's intelligence, Biffy's agility, and Bubba's resistance to
> > fire. You can see already how this is more difficult to balance,
> > due to so many more parameters. But IMO this makes the game more
> > fun to work on (from an admin's point of view), and more fun to play
> > (from a player's point of view).
>
> There is a large minefield lurking under the covers here. Its
> incredibly easy when dealing with a large number of factors to have
> the final value effectively be an average of their values. The result
> is that no single factor has a significant effect on the final result.
> This spells doom, as it means that for Bubba to increase his
> effectiveness with fireballs to any statistically noticable degree he
> has to significantly alter the values of several of the factors before
> the balance changes noticably.
Indeed. The best way I've found to have both a large number of factors
affecting a situation, and yet still have each one be signifigant, is to
have them affect the situation in very different ways, many if which will
be mutually exclusive with one another.
For example:
Biffy casts a fireball at Bubba.
The computer makes some rolls, and comes up with a successful fireball,
diameter 1 meter, velocity 10 m/s, aimed at Bubba with a "trueness" of
85%. (If it's a fully 3D world, probably graphical, this would just be a
vector of the direction it is traveling, which can then be compared to
Bubba's or anyone else's position to see whom it hits.) The fireball will
last for six seconds, and during that time has a surface heat of 1500
degrees Kelvin. (Some or all of these parameters may be combined or
measured in different units, depending upon what your target's rolls are
going to be like.)
Bubba notices Biffy casting the fireball one second before she actually
releases it, thanks to his perception stat and knowledge of spellcraft.
At this point his reflexes and dodge skill may allow him to predict where
the fireball will be flying, and then leap to (relative) safety. Rolls
are made on his dodge skill, reflexes stat, and perception stat. This
alone is enough to save him - except, wait, he's wearing the Extra Heavy
Armor of Fireball Turning! Thus his perception is hampered (that darn
visor just seems to obscure things), the speed at which he moves is very
slow (he will certainly be doing no jumping), and in fact, he's already
disabled dodging blows in combat as he knows it to be a tiring and
fruitless endevour. However, his armor *does* serve a purpose - it was
made for just this situation, and is able to deflect the fireball
relatively harmlessly (although it does leave him a bit warm inside his
suit, and manages to knock him off his feet, which could be a problem
depending on what Biffy does next).
In essence, you can build up very complex combat (or, in fact, anything -
this is the most obvious example however) by using a series of fairly
simple compares. Consider typical D&D combat:
Biffy swings at Bubba.
Her thac0+hitroll is compared against Bubba's armor class.
If it succeeds, her weapon dice+strength bonus+damroll is subtracted from
Bubba's hitpoints.
How about:
Biffy swings at Bubba.
Biffy rolls an "effectiveness" value on the swing, which is (1d100 + her
skill with her weapon + her agility) * (her strength / her weapon weight).
If in a situation where he is able to dodge, Bubba rolls a number based on
1d100 + his dodge skill + his agility. This is compared to Biffy's
effectiveness roll, and if higher, the blow is written off as a miss.
If the blow connects, the effectiveness value is considered a "directness"
of attack. It is clamped to the [1..100] range, where 1 is 1% of the
total force behind the blow connecting, and 100 is 100% of the force
connecting. A hit location is rolled on Bubba's body (possibly taking
into account Biffy's attempt to aim at a specific bodypart, Bubba's
ability to deflect damage to chosen bodyparts, and their relative sizes).
Damage is rolled by multiplying effectiveness by Biffy's damage constant
(possibly strength, damroll, weapon sharpness, or other factors).
A hit is rolled against Bubba's armor. A sturdyness value of the armor is
either retrived from the armor, or constructed based on it's material,
thickness, quality, and magical bonuses. If this amount is larger than
the damage of Biffy's blow, the blow was completely absorbed. If it is
smaller, then subtract the number from the damage and proceed.
Divide the remaining damage by Bubba's constituion and apply it to his
hitpoints.
The nice thing about this is that you could use only a single value for
each step, or you could enter some complex formulas with several values
including stats, skills, magical bonuses, the phase of the moon, etc.
> The only effective solutiuon I've found to this is expensive: Set up a
> whole bunch of nested loops, one each per factor, and permute. Plot
> the results. See if the results really look the way you want them to.
> Yes, you could probably do the same thing with Mathmatica or similar.
> It doesn't vary the basic approach, just the expression.
You really have to have a head for visualizing curves. Unfortunately, I
don't. Luckily, my partner does. He does what he calls "massaging the
formulas" where he doodles on his sketchpad for a couple hours and comes
back with a forumla that generates exactly the kind of curve that we want.
If you're not so mathematically inclined, like I, I suggest sticking to
easily plottable two-variable curves based on log or squares.
> > And, one might still refer to Bubba as being a "high-level player"
> > if he's got a good fire resistance, a good dodge skill, a great
> > spellcraft skill, etc. But it's much more than a single number now
> > - Bubba might be terrible a dodging fireballs, but an excellent
> > thief. He's still "high level", he's just not good at avoiding
> > nasty fire spells.
>
> <nod>
>
> Appropriate use of a few moderately good skills can be far more
> effective that bumbling use of a mix of extremely good and bad skills.
True in Real Life (no one cares that Michael Jordan is a reasonbly good
golfer), and even more true on a MUD. The characters that can do *one*
thing, *really* well are both more impressive and more popular than those
that can do most things fairly well. IMO this is a good thing; the only
stumbling block is the jack-of-all-trades effect, which is usually
curtailed by an arbitrary and frequently unsatisfactory limit.
> >> I'd like to hear legitimate pros and cons, not "oh, it's cool" or
> >> "I hated it, it sucked."
>
> > IMO systems based on more complex metrics (generally meaning
> > skill-based) are about 1000% more fulfulling for both the creator
> > and the player.
>
> I generally view it as a question of flavour and thereby involvement.
Right. In this case more DOES equal better. (Naturally you have to
maintain the actual quality of each factor, else you risk it turning into
a mess of numbers with no reasonable relationships to one another or the
tasks players put their characters to.)
Adam
More information about the mud-dev-archive
mailing list