May 1998
- OT: CGDC Adam Wiggins
- OT: CGDC Mike Sellers
- There can be.. only ONE! (fwd) Ling
- There can be.. only ONE! (fwd) Matt Chatterley
- Some thoughts on languages and users - was: Ma Jon A. Lambert
- Some thoughts on languages and users - was: Ma Chris Gray
- Some thoughts on languages and users - was: Ma Adam Wiggins
- Some thoughts on languages and users - was: Ma J C Lawrence
- (fwd) AD: [custom graphical] whitestar Crossfi Jon A. Lambert
- LIST: The "MUD-DEV" MUD Development mailing list J C Lawrence
- Wired, UO, Mike Sellers
- Wired, UO, John Bertoglio
- Wired, UO, and Internet Gaming (was OT: Dr. Cat
- Wired, UO, and Internet Gaming (was OT: Koster, Raph
- Wired, UO, and Internet Gaming (was OT: J C Lawrence
- Wired, UO, and Internet Gaming (was OT: John Bertoglio
- OT: Supporting articles found for UOL play style Jon A. Lambert
- PK's: A solution? J C Lawrence
- Preview of Asheron's Call J C Lawrence
- Asheron's Call Interview with Toby Ragaini, Lead Designer, and Jon Grande, Product Planner. J C Lawrence
- Character maintinence - expenditure of resources Adam Wiggins
- Character maintinence - expenditure of resources Dan Shiovitz
- Character maintinence - expenditure of resources Adam Wiggins
- Character maintinence - expenditure of resources J C Lawrence
- Character maintinence - expenditure of resources Koster, Raph
- Character maintinence - expenditure of resources J C Lawrence
- Character maintinence - expenditure of resources John Bertoglio
- Character maintinence - expenditure of resources J C Lawrence
- Motivations for Creating Mud-Like Worllds and Servers | John Bertoglio
- FW: (Fwd) Bouncing mail J C Lawrence
- FW: (Fwd) Bouncing mail John Bertoglio
- FW: (Fwd) Bouncing mail Matt Chatterley
- FW: (Fwd) Bouncing mail s001gmu@nova.wright.edu
- FW: (Fwd) Bouncing mail J C Lawrence
- FW: (Fwd) Bouncing mail s001gmu@nova.wright.edu
- FW: (Fwd) Bouncing mail J C Lawrence
- Character development [was ] Koster, Raph
- Motivations for Creating Mud-Like Worlds and Servers Holly Sommer
- META -- membership Jay Sax
- META -- membership Koster, Raph
- META -- membership J C Lawrence
- Motivations (was something else...) s001gmu@nova.wright.edu
- Motivations (was something else...) Richard Woolcock
- client UI written in server's language (was Some thoughts...) Erik Ostrom
- Some thoughts on languages and users - was: Ma J C Lawrence
- Some thoughts on languages and users - was: Ma Travis S. Casey
- Some thoughts on languages and users - was: Ma J C Lawrence
- META: Character of the list's membership J C Lawrence
- quickie CGDC report Mike Sellers
- quickie CGDC report Adam Wiggins
- Some essays I've written lately Koster, Raph
- Some essays I've written lately Koster, Raph
- Some essays I've written lately Koster, Raph
- Some essays I've written lately Koster, Raph
- Some essays I've written lately Koster, Raph
- Some essays I've written lately J C Lawrence
- Some essays I've written lately Koster, Raph
- Some essays I've written lately J C Lawrence
- Some essays I've written lately J C Lawrence
- Frandel 3D (fwd) Holly Sommer
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is Raph Koster
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is Koster, Raph
- MURKLE: Wot it is Dr. Cat
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is Shawn Halpenny
- MURKLE: Wot it is Mike Sellers
- MURKLE: Wot it is Nathan F Yospe
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is Chris Gray
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is Chris Gray
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is Ling
- MURKLE: Wot it is Oliver Jowett
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is Ling
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is Ling
- MURKLE: Wot it is J C Lawrence
- MURKLE: Wot it is jacob langthorn
- MURKLE: Wot it is Jon A. Lambert
- MURKLE: Wot it is J C Lawrence
- We're Tiny, we're Toonie, we're all a little Loonie! Ling
- META: Search features of the MUD-Dev archive J C Lawrence
- CGDC, a summary Adam Wiggins
- CGDC, a summary Koster, Raph
- CGDC, a summary Holly Sommer
- CGDC, a summary Caliban Tiresias Darklock
- CGDC, a summary J C Lawrence
- CGDC, a summary Chris Gray
- CGDC, a summary J C Lawrence
- CGDC, a summary Marian Griffith
- CGDC, a summary J C Lawrence
- CGDC, a summary Koster, Raph
- CGDC, a summary J C Lawrence
- CGDC, a summary J C Lawrence
- CGDC, a summary Mike Sellers
- CGDC, a summary J C Lawrence
- CGDC, a summary Chris Gray
- CGDC, a summary Travis S. Casey
- CGDC, a summary Koster, Raph
- CGDC, a summary Adam Wiggins
- CGDC, a summary Koster, Raph
- CGDC, a summary Chris Gray
- CGDC, a summary Koster, Raph
- CGDC, a summary John Bertoglio
- CGDC, a summary s001gmu@nova.wright.edu
- CGDC, a summary John Bertoglio
- CGDC, a summary Koster, Raph
- CGDC, a summary s001gmu@nova.wright.edu
- CGDC, a summary J C Lawrence
- CGDC, a summary John Bertoglio
- CGDC, a summary Koster, Raph
- CGDC, a summary Joel Kelso
- CGDC, a summary J C Lawrence
- CGDC, a summary Marian Griffith
- CGDC, a summary J C Lawrence
- CGDC, a summary Marian Griffith
- CGDC, a summary Jon A. Lambert
- CGDC, a summary J C Lawrence
- CGDC, a summary J C Lawrence
- CGDC, a summary J C Lawrence
- CGDC, a summary Adam Wiggins
- CGDC, a summary Jon A. Lambert
- CGDC, a summary Orion Henry
- MUD mentation system Matthew R. Sheahan
- How to handle log-outs in a totally dynamic world. Ben Greear
- How to handle log-outs in a totally dynamic world. John Bertoglio
- How to handle log-outs in a totally dynamic world. Ben Greear
- How to handle log-outs in a totally dynamic world. Dan Shiovitz
- How to handle log-outs in a totally dynamic world. Ben Greear
- How to handle log-outs in a totally dynamic world. Adam Wiggins
- How to handle log-outs in a totally dynamic world. Vadim Tkachenko
- How to handle log-outs in a totally dynamic world. Richard Woolcock
- How to handle log-outs in a totally dynamic world. Ben Greear
- How to handle log-outs in a totally dynamic world. Dan Shiovitz
- How to handle log-outs in a totally dynamic world. J C Lawrence
- On tanks... J C Lawrence
- On tanks... Ling
- More on LetsSystems J C Lawrence
- Attributes: Sanity Holly Sommer
- Attributes: Sanity Travis S. Casey
- Attributes: Sanity Holly Sommer
- Attributes: Sanity Holly Sommer
- Attributes: Sanity Adam Wiggins
- Attributes: Sanity Travis S. Casey
- Attributes: Sanity Holly Sommer
- Attributes: Sanity Holly Sommer
- mudschools Marian Griffith
- mudschools Matt Chatterley
- Mudschool Ling
- Using HTML for a Mud character generator John Bertoglio
- Using HTML for a Mud character generator s001gmu@nova.wright.edu
- Using HTML for a Mud character generator John Bertoglio
- Using HTML for a Mud character generator Holly Sommer
- Using HTML for a Mud character generator John Bertoglio
- Using HTML for a Mud character generator s001gmu@nova.wright.edu
- Using HTML for a Mud character generator Vadim Tkachenko
- Using HTML for a Mud character generator John Bertoglio
- Using HTML for a Mud character generator J C Lawrence
- Using HTML for a Mud character generator Vadim Tkachenko
- Using HTML for a Mud character generator John Bertoglio
- Using HTML for a Mud character generator Robert Woods
- Leaving characters in play Joel Kelso
- Leaving characters in play Ben Greear
- Leaving characters in play John Bertoglio
- Leaving characters in play Adam Wiggins
- Leaving characters in play J C Lawrence
- Leaving characters in play John Bertoglio
From: J C Lawrence <claw@under.engr.sgi.com>
To: mud-dev@kanga.nu <mud-dev@kanga.nu>
Date: Friday, May 15, 1998 6:11 PM
>On Thu, 14 May 1998 11:21:17 -0700 (PDT)
>Adam Wiggins<adam@angel.com> wrote:
>
>> On Tue, 12 May 1998, John Bertoglio wrote:
>
>> A couple of things. First, I think that the stuff above is pretty
>> different from VGA Planets. It doesn't fix any problems (at least,
>> from where I'm sitting) incured by leaving people in game all the
>> time. They can certainly set some standing orders for things their
>> character will do while they are away, but you don't need an
>> order-based combat system for this to work. Secondly, getting the
>> above to actually work seamlessly in the mud environment might be
>> tricky. Ie: while in combat, are *all* commands that you give
>> orders? If not, doesn't that mean that players will quickly figure
>> out commands to hurt their opponents outside of the combat scheme?
>
>It is this point which ghas persuaded me to almost entirely move away
>from round based combat. I refuse to place the entire game and all
>players on a pacing clock (humans shall not wait for machines), but
>not using a global clock while using usably long combat rounds opens
>the combat system for all sorts of interesting abuse due to the
>inconsistant time scales.
Minor point with confusion. Do you mean time scale as in real time (seconds
ticking on a clock) or another concept I am (obiously) unfamilier with.
Inconsistant time scales (real time vrs how long thing take to happen in a
game) are a reality in virtually every game I have ever seen on computers
with the possible exception of the most carefully crafted simulators
including those in commercial and military use. If you issue a command,
drink jug and the connection is quick, the screen quickly returns something
like "The jug is now empty". Now I know some of you out there could drain a
jug in a few miliseconds...but most of us can't. Most of us cannot work our
way up to the top of a 10,000 ft mountain in the time it takes to type
"CLIMB" or "UP" five times.
Less minor point and confusion. Perhaps I am missing something. My system
uses what I would call round based combat but is controled (usually) by
player command and inititive. Some quick questions. I guess most would
consider round-based combat to be similar to a boxing match where the
rounds are discrete chunks of time. I think more like a wargamer...a combat
round is a period in which a certain number of actions are executed by the
combatants and then resolved. Of course, the computer makes simultaneous
movement possible, something which has never been adequately modeled (in a
playable fashion) in board games. Our combat round consists of a certain
number of action points. Every action requested by the player consumes
action points. Actions can be interuppted, canceled due to combat results
and delayed. When the points are used up, the round is over. The amount of
AP in a round varies according to the capabilities of the combatants,
inititive, surprise, etc. Combat rounds are resolved quickly by the server.
Typing speed is not a major issue unless the combat profile chosen (a wimpy
variant on the JCL combat package) is not working out...and even then type
[>K 5] and you have changed to combat profile 5 (which you have carefully
designed for just this situation. ).
>Opening the combat to being entirely untimed conversely allows spam
>attacks and tends to guarantee that the fastest twitch will win. Not
>good. Further, as discussed earlier, I can't distinguish between
>combat and non-combat commands as even utterly innocuous commands will
>be used heavily in combat ("drop mana consumers"), and very
>combat-centric commands will be used peacibly (cf UggUgg's fight)..
This is the only way I can see to build a sensible parser. Besides...it is
fun to type KILL TORCH...and have torch be extinguished as opposed to
attacking it with a rock.
>I don't have a good design. The best I can think of so far is:
>
> -- No first blows are fatal.
Why? You hit a bunny with a halbred and you either miss or have a binary
bunny.
(OT aside: There is a (probably) apocraphal story about a dentist who had a
ranch outside of a major city in Arizona. This was during 60's when people
were still digging bomb shelters. Anyway, doing his patriotic duty, he
installs a 20mm antiaircraft gun on a motorized traverse in his back yard
(several thousand acres of desert). When asked by a reporter what he
installed the gun for he replied: "I use it to hunt jack rabbits. I don't
hit them very often...but boy when I do!")
Now when our system is finished, I guarantee that no player will score a
one hit kill on another player...but that is a different story.
> -- First blows may be nearly fatal.
Of course.
> -- Second blows can be fatal, but its very very unlikely, especially
>if the first blow was nearly fatal.
Sounds like you are considering manipulating fate (luck) in combat
fortunes. I see this a partial solution to PK...Operant conditioning..."I
got womped by a newbie with a dagger! Bummer. He took all my stuff."
> -- Arrange these probabilities appropriately to force most combats
>to the 15 - 20 seconds point.
I disagree here. Let combat spin off on its own. I (barely) recall a movie
which had Sean Connery in single combat with a bad guy. Both were in full
armor fighting in the middle of a hot, grassy field. Neither could get the
better of the other. The fight took quite a while. At the end, both were so
exausted the could not stand. A similar fight could happen in our system
with carefully matched opponents. Fatigue happens even if damage doesn't.
Fighters could dance around each other for five minutes (RT) using
defensive attack profiles until one was taunted into launching a real
attack or they fell into a heap and were killed by a nasty bunny.
> -- The game dynamically defines a "combat state" which is hidden
>from the player and is used only for event process control.
We define a combat state mostly to record the fight and trigger automatic
combat events for engaged pairs (every combat creates its own event) who
fail to execute a command.
> -- Combat state is initiated upon a definitely combat-oriented
>command from any party (kill, fight, hit, damaging spell, etc).
Exactly. Looking at the archives, this seems to be a problem for people.
Lots of discussion of intent, accidents, etc. There is some fuzzy ground:
Is "THROW KNIFE TO BUBBA" equivilant to "THROW KNIFE AT BUBBA"? Looks like
we are going to drill down beyond the verb level and create the combat
event when the combat programs are called.
> -- Combat state is declared for both target and source.
We just create an entry in a data table for each combat, attacker and
defender. We create as separate entry for each combat so if BUBBA fights
three hobbits, three events are spawned. If Hobbit 1 decides to flee, that
event is closed out. If #1 decides to join BUBBA and attack his former
buddies, cool. Their combat event is closed and new ones created.
> -- Combat state's only effect is to enforce timings of actions. It
>takes XXX time to swing a sword, YYY time to cast a spell etc.
Because I can't control time (stateless, you know), we use action points.
(BTW, an action can take so many points it takes three (or more) rounds to
fire.) This frees the players from the twitch factor. It also creates a
more leisurely (some would say slow) combat feel.
> -- Combat state is torn down when one part dies or leaves the
>immediate vicinity. (ie combat state does not apply to long distance
>battles, only proximate)
I don't think distance is a factor unless you mean really long distance. I
wouldn't consider the Unibomber involved in combat with his victims. Same
thing if someone thoughtfully mails my character a mana sink spell which
triggers when the letter is opened. If Boffo is shooting arrows at Bubba
from 100 yards away and Bubba is unaware of his position (Boffo is well
concealed, or Bubba is just clueless) a combat object is created. Bubba
cannot retaliate, but he can use his action points to flee, seek cover, set
off a smoke bomb or jump up and down and shout "unfair".
>I don't like it. I really don't like it. But its the best I've got
>right now.
>--
>J C Lawrence Internet: claw@null.net
>(Contractor) Internet: coder@ibm.net
>---------(*) Internet: claw@under.engr.sgi.com
>...Honourary Member of Clan McFud -- Teamer's Avenging Monolith...
>
>--
(I have a huge, somewhat incoherent post on a combat system started on my
workstation at work. I should be able to poach enough time to post it next
week sometime. It could even be coherent by then...It references a lot of
past posts and might even be interesting.)
John Bertoglio
>MUD-Dev: Advancing an unrealised future.
--
MUD-Dev: Advancing an unrealised future. - Leaving characters in play Travis S. Casey
- Leaving characters in play Adam Wiggins
- Leaving characters in play John Bertoglio
- Leaving characters in play J C Lawrence
- Leaving characters in play J C Lawrence
- Leaving characters in play Travis S. Casey
- Leaving characters in play J C Lawrence
- Leaving characters in play D. B. Brown
- Leaving characters in play Travis S. Casey
- Leaving characters in play Adam Wiggins
- Leaving characters in play John Bertoglio
- Leaving characters in play Jon A. Lambert
- Leaving characters in play s001gmu@nova.wright.edu
- Leaving characters in play Ben Greear
- Request "unsubscribe calvin@orinconhi.com mud-dev" Petidomo Mailing List Server
- Natural Language Processing (NLP) Shawn Halpenny
- Is There a There in Cyberspace? J C Lawrence
- Is There a There in Cyberspace? Jon A. Lambert
- Is There a There in Cyberspace? J C Lawrence
- [OT] Web Pages Jon A. Lambert
- AR Mining System John Bertoglio
- AR Mining System Oliver Jowett
- AR Mining System John Bertoglio
- mudschools Mike Sellers
- Using HTML for a Mud character generator Travis S. Casey
- Character creation, was: Mudschool Richard Woolcock
- Character creation, was: Mudschool Jon A. Lambert
- Onchat -- Java based chat room. J C Lawrence
- A short introduction of a (quite) long-time lurker Per Vognsen
- [MUD-Dev]World Size and The "Hot House" Factor Was PK and my "Mobless MUD" idea John Bertoglio
- mudschools jacob langthorn
- world concept jacob langthorn
- world concept Jo Dillon
- world concept J C Lawrence
- world concept Holly Sommer
- world concept jacob langthorn
- OT: Java multithreading performance Vadim Tkachenko
- OT: Java multithreading performance Ben Greear
- OT: Java multithreading performance Vadim Tkachenko
- OT: Java multithreading performance Chris Gray
- OT: Java multithreading performance Vadim Tkachenko
- OT: Java multithreading performance Chris Gray
- OT: Java multithreading performance Vadim Tkachenko
- OT: Java multithreading performance Chris Gray
- OT: Java multithreading performance Ben Greear
- OT: Java multithreading performance Jon A. Lambert
- OT: Java multithreading performance Chris Gray
- OT: Java multithreading performance Vadim Tkachenko
- OT: Java multithreading performance J C Lawrence
- META: Lost messages J C Lawrence
- Titanic's demise (was MURKLE: Wot it is) Mike Sellers
- Titanic's demise (was MURKLE: Wot it is) Koster, Raph
- mudschools jacob langthorn
- mudschools Marian Griffith
- mudschools Mike Sellers
- mudschools Marian Griffith
- mudschools Robert Woods
- mudschools Mike Sellers
- mudschools Robert Woods
- mudschools Robert Woods
- mudschools Caliban Tiresias Darklock
- MUD Schools Adam Casbarian
- MUD Schools Chris Lloyd
- MUD Schools Jon Lambert
- Combat Was Leaving characters in play Orion Henry
- Combat Was Leaving characters in play Oliver Jowett
- Combat Was Leaving characters in play Orion Henry
- Combat Was Leaving characters in play Oliver Jowett
- Combat Was Leaving characters in play D. B. Brown
- Combat Was Leaving characters in play Orion Henry
- Combat Was Leaving characters in play Adam Wiggins
- Combat Was Leaving characters in play J C Lawrence
- Combat Was Leaving characters in play Orion Henry
- Combat Was Leaving characters in play Adam Wiggins
- Combat Was Leaving characters in play Travis S. Casey
- Combat Was Leaving characters in play Adam Wiggins
- Combat Was Leaving characters in play Travis S. Casey
- Combat Was Leaving characters in play Adam Wiggins
- Bad Game Designer, No Twinkie! -- By Ernest Adams J C Lawrence
- Bad Game Designer, No Twinkie! -- By Ernest Adams T. Alexander Popiel
- Bad Game Designer, No Twinkie! -- By Ernest Adams J C Lawrence
- Bad Game Designer, No Twinkie! -- By Ernest Adams John Bertoglio
- Bad Game Designer, No Twinkie! -- By Ernest Adams Caliban Tiresias Darklock
- Bad Game Designer, No Twinkie! -- By Ernest Adams John Bertoglio
- Bad Game Designer, No Twinkie! -- By Ernest Ada ms Koster, Raph
- Bad Game Designer, No Twinkie! -- By Ernest Adams Caliban Tiresias Darklock
- Bad Game Designer, No Twinkie! -- By ErnestAdam s Koster, Raph
- Bad Game Designer, No Twinkie! -- By Ernest Ada ms J C Lawrence
- Bad Game Designer, No Twinkie! -- By Ernest Adams J C Lawrence
- Bad Game Designer, No Twinkie! -- By Ernest Adams John Bertoglio
- Java multithreading test source Vadim Tkachenko
- Java multithreading test source J C Lawrence
- Java multithreading test source Vadim Tkachenko
- Java multithreading test source Ben Greear
- Java multithreading test source Vadim Tkachenko
- Java multithreading test source Chris Gray
- Mud Tales John Bertoglio
- Nested coorindate space model J C Lawrence
- Nested coorindate space model Ling
- Nested coorindate space model J C Lawrence
- Nested coorindate space model Ling
- Nested coorindate space model Michael Hohensee
- Nested coorindate space model J C Lawrence
- Nested coorindate space model Michael Hohensee
- Nested coorindate space model Jason Goodwin
- Nested coorindate space model J C Lawrence
- Nested coorindate space model Michael Hohensee
- Nested coorindate space model J C Lawrence
- Nested coorindate space model Benjamin D. Wiechel
- Nested coorindate space model J C Lawrence
- Nested coorindate space model Michael Hohensee
- Now For Something Completely Different: PK with style John Bertoglio
- Sex in Games -- ya gotta, um, yeah J C Lawrence
- Combat in the Abandoned Realms John Bertoglio
- A Metaphysics System s001gmu@nova.wright.edu
- META: New list features J C Lawrence
- OT: Java multithreading test source Jon A. Lambert
- OT: Java multithreading test source Mike Sellers
- OT: Java multithreading test source Ben Greear
- OT: Java multithreading test source Jon A. Lambert
- OT: Java multithreading test source Jon A. Lambert
- OT: Java multithreading test source Jon A. Lambert
- OT: Java multithreading test source Jon A. Lambert
- OT: Java multithreading test source Ben Greear
- OT: Java multithreading test source John Bertoglio
- OT: Java multithreading test source Vadim Tkachenko
- OT: Java multithreading test source Jon A. Lambert
- OT: Java multithreading test source Ben Greear
- Plug: Got my java client to work using the java-plugin. Ben Greear
- UO's rep system, was: CGDC Koster, Raph
- UO's rep system, was: CGDC J C Lawrence
- BIAP Chat/Chat Pro (fwd) Nathan F Yospe
- BIAP Chat/Chat Pro (fwd) Holly Sommer
- Tutorial for Multi-User Environments Niklas Elmqvist
- Tutorial for Multi-User Environments Niklas Elmqvist
- skill system Andrew C.M. McClintock
- skill system Jo Dillon
- skill system Andrew C.M. McClintock
- skill system Adam Wiggins
- skill system Marian Griffith
- skill system J C Lawrence
- skill system Jon A. Lambert
- skill system John Bertoglio
- skill system J C Lawrence
- skill system s001gmu@nova.wright.edu
- skill system Adam Wiggins
- skill system Katrina McClelan
- skill system Richard Woolcock
- skill system Koster, Raph
- skill system John Bertoglio
- skill system Adam Wiggins
- skill system Mike Sellers
- skill system Richard Woolcock
- skill system Adam Wiggins
- skill system Richard Woolcock
- skill system Katrina McClelan
- skill system Adam Wiggins
- skill system Richard Woolcock
- skill system Katrina McClelan
- skill system Adam Wiggins
- skill system Dan Shiovitz
- skill system Adam Wiggins
- skill system Richard Woolcock
- skill system Adam Wiggins
- skill system Richard Woolcock
- skill system J C Lawrence
- skill system s001gmu@nova.wright.edu
- skill system J C Lawrence
- skill system John Bertoglio