December 1998

• Hex-grid mapping Matthew R. Sheahan
• • Hex-grid mapping Jon Leonard
  • • Hex-grid mapping James Wilson
    • • Hex-grid mapping Jon Leonard
      • • Hex-grid mapping James Wilson
        • • Hex-grid mapping Par Winzell
          • Hex-grid mapping quzah [sotfhome]
          • Hex-grid mapping Nathan F Yospe
  • Hex-grid mapping Ling
  • • Hex-grid mapping Jon A. Lambert
    • Hex-grid mapping Nathan F Yospe
    • Hex-grid mapping Alberto Barsella
• Hex-grid mapping (example from PSL empire) Pericolo DiMorte
• • Hex-grid mapping (example from PSL empire) Nathan F Yospe
  • Hex-grid mapping (example from PSL empire) quzah [sotfhome]
  • • Hex-grid mapping (example from PSL empire) Pericolo DiMorte
    • • Hex-grid mapping (example from PSL empire) James Wilson
• ADMIN: Personalities... J C Lawrence
• Hex-grid mapping (fwd) Nathan F Yospe
• • Hex-grid mapping (fwd) J C Lawrence
• Electric Communities' E Ola Fosheim Grøstad
• Electric Communities' E Ola Fosheim Grøstad
• mud client development systems Sunny Gulati
• • mud client development systems Caliban Tiresias Darklock
  • mud client development systems Chris Gray
  • • mud client development systems greear@cyberhighway.net
    • mud client development systems Sunny Gulati
    • • mud client development systems Benjamin D. Wiechel
      • mud client development systems Sunny Gulati
      • • mud client development systems J C Lawrence
        • mud client development systems Per Vognsen
        • • mud client development systems Sunny Gulati
          • • mud client development systems Scatter
            • mud client development systems Per Vognsen
  • mud client development systems Chris Gray
  • • mud client development systems Jon Leonard
  • mud client development systems Bruce Mitchener, Jr.
  • • mud client development systems Sunny Gulati
  • mud client development systems Chris Gray
• Stack-Based NPC AI Eli Stevens {KiZurich}
• • Stack-Based NPC AI Mark Gritter
  • Stack-Based NPC AI Marc Hernandez
  • Stack-Based NPC AI Richard Woolcock
  • • Stack-Based NPC AI Par Winzell
    • • Stack-Based NPC AI David Bennett
    • Stack-Based NPC AI Mik Clarke
  • Stack-Based NPC AI Felix A. Croes
• Introduction Mik Clarke
• • Introduction Adam J. Thornton
  • • Introduction Mik Clarke
    • • Introduction ApplePiMan@aol.com
      • • Introduction Mik Clarke
• Thought Treasure Adam Wiggins
• Netscape's "Gecko" Browsing Engine (fwd) Nathan F Yospe
• • Netscape's "Gecko" Browsing Engine (fwd) Adam Wiggins
  • • Netscape's "Gecko" Browsing Engine (fwd) Bruce Mitchener, Jr.
    • Netscape's "Gecko" Browsing Engine (fwd) greear@cyberhighway.net
• Error tolerant UDP data streams J C Lawrence
• • Error tolerant UDP data streams James Wilson
  • • Error tolerant UDP data streams J C Lawrence
  • Error tolerant UDP data streams Ola Fosheim Grøstad
• ADMIN: (IMPORTNANT) Server down time and possible service interruption J C Lawrence
• [DevMUD] Error tolerant UDP data streams Darren Henderson
• MUD Design doc (long) Thinus Barnard
• • MUD Design doc (long) Benjamin D. Wiechel
  • • MUD Design doc (long) Thinus Barnard
    • • MUD Design doc (long) J C Lawrence
      • • MUD Design doc (long) Koster, Raph
        • MUD Design doc (long) Emil Eifrem
        • • MUD Design doc (long) Adam Wiggins
          • • MUD Design doc (long) Michael Willey
            • • MUD Design doc (long) Adam Wiggins
              • • MUD Design doc (long) J C Lawrence
          • MUD Design doc (long) Mik Clarke
          • • MUD Design doc (long) Caliban Tiresias Darklock
            • • MUD Design doc (long) Thinus Barnard
              • • MUD Design doc (long) Mik Clarke
              • MUD Design doc (long) Mik Clarke
              • • MUD Design doc (long) Travis Casey
                • MUD Design doc (long) Nathan F Yospe
                • • MUD Design doc (long) Mik Clarke
                  • • MUD Design doc (long) Nathan F Yospe
                    • • MUD Design doc (long) Mik Clarke
                      • • MUD Design doc (long) Nathan F Yospe
                        • • MUD Design doc (long) Mik Clarke
                        • MUD Design doc (long) Adam Wiggins
                        • MUD Design doc (long) J C Lawrence
                        • • MUD Design doc (long) Ling
                          • • MUD Design doc (long) J C Lawrence
                            • • MUD Design doc (long) Koster, Raph
                              • • MUD Design doc (long) J C Lawrence
                          • MUD Design doc (long) Mik Clarke
                          • • MUD Design doc (long) J C Lawrence
          • MUD Design doc (long) J C Lawrence
          • • MUD Design doc (long) Emil Eifrem
            • • MUD Design doc (long) Travis Casey
              • • MUD Design doc (long) Emil Eifrem
                • • MUD Design doc (long) Travis Casey
                  • • MUD Design doc (long) Emil Eifrem
                    • • MUD Design doc (long) Travis S. Casey
                      • • MUD Design doc (long) Caliban Tiresias Darklock
                      • MUD Design doc (long) Marian Griffith
              • MUD Design doc (long) Koster, Raph
  • MUD Design doc (long) Chris Gray
  • • MUD Design doc (long) Sunny Gulati
    • • MUD Design doc (long) J C Lawrence
  • MUD Design doc (long) Chris Gray
  • MUD Design doc (long) Benjamin D. Wiechel
  • • MUD Design doc (long) J C Lawrence
  • MUD Design doc (long) Nathan F Yospe
  • MUD Design doc (long) Chris Gray
  • • MUD Design doc (long) Emil Eifrem
  • MUD Design doc (long) Chris Gray
  • • MUD Design doc (long) Mik Clarke
  • MUD Design doc (long) Chris Gray
  • • MUD Design doc (long) Caliban Tiresias Darklock
• Hex grids. quzah [softhome]
• small dev-mud invite Chris Gray
• • small dev-mud invite J C Lawrence
• mud client development systems Sunny Gulati
• • mud client development systems Jay Carlson
  • mud client development systems J C Lawrence
• AFAP: As fast as possible, non linear... quzah [softhome]
• • AFAP: As fast as possible, non linear... Jon Leonard
  • • AFAP: As fast as possible, non linear... quzah [softhome]
  • AFAP: As fast as possible, non linear... Mik Clarke
  • • AFAP: As fast as possible, non linear... Alex Oren
  • AFAP: As fast as possible, non linear... Dan Shiovitz
  • AFAP: As fast as possible, non linear... Mik Clarke
  • • AFAP: As fast as possible, non linear... quzah [softhome]
    • AFAP: As fast as possible, non linear... quzah [softhome]
    • • AFAP: As fast as possible, non linear... Greg Connor
      • • AFAP: As fast as possible, non linear... quzah [softhome]
• Graphic design, client questions Thinus Barnard
• • Graphic design, client questions Caliban Tiresias Darklock
  • • Graphic design, client questions Jo Dillon
    • • Graphic design, client questions Caliban Tiresias Darklock
      • • Graphic design, client questions Jo Dillon
    • Graphic design, client questions Thinus Barnard
    • • Graphic design, client questions Sunny Gulati
      • • Graphic design, client questions J C Lawrence
      • Graphic design, client questions Caliban Tiresias Darklock
      • Graphic design, client questions J C Lawrence
    • Graphic design, client questions J C Lawrence
    • Graphic design, client questions Jay Carlson
  • Graphic design, client questions Ben Greear
• More Laws, was DIS: Client-Server vs Peer-to-Peer Koster, Raph
• • More Laws, was DIS: Client-Server vs Peer-to-Peer Ola Fosheim Grøstad
  • • More Laws, was DIS: Client-Server vs Peer-t o-Peer Koster, Raph
    • • More Laws, was DIS: Client-Server vs Peer-t o-Peer J C Lawrence
• More Laws Niklas Elmqvist
• • More Laws J C Lawrence
• Re[2]:MUD Design doc (long) Michael Willey
• • Re[2]:MUD Design doc (long) Adam Wiggins
  • Re[2]:MUD Design doc (long) Caliban Tiresias Darklock
  • • Re[2]:MUD Design doc (long) J C Lawrence
  • Re[2]:MUD Design doc (long) Sunny Gulati
  • • Re[2]:MUD Design doc (long) quzah [softhome]
    • • Re[2]:MUD Design doc (long) David Bennett
  • Re[2]:MUD Design doc (long) quzah [softhome]
• Some useful links Niklas Elmqvist
• Response (Was MUD Design doc (long)) Ola Fosheim Grøstad
• Response (Was MUD Design doc (long)) Chris Gray
• • Response (Was MUD Design doc (long)) J C Lawrence
• example custom protocol and its uses Chris Gray
• client stuff... Andrew Wilson
• Developing a MUD for the first time? Alex Oren
• Re[2]:MUD Design doc (long) J C Lawrence
• [DevMUD] Database module J C Lawrence
• • [DevMUD] Database module cynbe@muq.org
  • • [DevMUD] Database module J C Lawrence
    • • [DevMUD] Database module cynbe@muq.org
    • [DevMUD] Database module T. Alexander Popiel
    • [DevMUD] Database module Jay Carlson
    • • [DevMUD] Database module cynbe@muq.org
  • [DevMUD] Database module Felix A. Croes
• Re[2]:MUD Design doc (long) Caliban Tiresias Darklock
• [RRE]AAAI 1999 Fall Symposium: Narrative Intelligence Bruce Mitchener, Jr.
• (fwd) DESIGN: Proposed topic of Discussion (Injecting Pure Signal) J C Lawrence
• • (fwd) DESIGN: Proposed topic of Discussion (Injecting Pure Signal) Mik Clarke
• Terragen Vadim Tkachenko
• [RELEASE] Insanity To Infinity (I:I_OS) v.01a Bobby Bailey
• • [RELEASE] Insanity To Infinity (I:I_OS) v.01a Robin Carey
  • • [RELEASE] Insanity To Infinity (I:I_OS) v.01a Bobby Bailey
• META: 1998 Topic Summary Jon A. Lambert
• [RELEASE] Insanity To Infinity (I:I_OS) v.02a Bobby Bailey
• ADMIN: New text formatting rule for MUD-Dev J C Lawrence
• More Laws Jon A. Lambert
• • More Laws Travis Casey
• MUD Design doc - Combat Jon A. Lambert
• • MUD Design doc - Combat J C Lawrence
  • • MUD Design doc - Combat cynbe@muq.org
    • MUD Design doc - Combat Koster, Raph
    • • MUD Design doc - Combat Caliban Tiresias Darklock
      • • MUD Design doc - Combat quzah [softhome]
        • • MUD Design doc - Combat Caliban Tiresias Darklock
          • MUD Design doc - Combat T. Alexander Popiel
          • • MUD Design doc - Combat J C Lawrence
            • • MUD Design doc - Combat Koster, Raph
              • • MUD Design doc - Combat Adam Wiggins
                • MUD Design doc - Combat J C Lawrence
                • MUD Design doc - Combat quzah [softhome]
                • MUD Design doc - Combat Dr. Cat
                • • MUD Design doc - Combat T. Alexander Popiel
                  • • MUD Design doc - Combat Caliban Tiresias Darklock
                  • MUD Design doc - Combat J C Lawrence
      • MUD Design doc - Combat James Wilson
      • • MUD Design doc - Combat Nathan F Yospe
        • • MUD Design doc - Combat James Wilson
          • • MUD Design doc - Combat Nathan F Yospe
            • MUD Design doc - Combat diablo@best.com
            • MUD Design doc - Combat Kristen Koster
  • MUD Design doc - Combat Chris Gray
  • • MUD Design doc - Combat Scatter
  • MUD Design doc - Combat Koster, Raph
  • • MUD Design doc - Combat Kristen Koster
  • MUD Design doc - Combat Caliban Tiresias Darklock
  • • MUD Design doc - Combat T. Alexander Popiel
• Levels versus Skills, who uses them and when. Till Eulenspiegel
• • Levels versus Skills, who uses them and when. Travis Casey
  • • Levels versus Skills, who uses them and when. Koster, Raph
    • • Levels versus Skills, who uses them and when. Adam Wiggins
      • • Levels versus Skills, who uses them and when. Marian Griffith
      • Levels versus Skills, who uses them and when. Andy Cink
      • • Levels versus Skills, who uses them and when. Ling
        • • Levels versus Skills, who uses them and when. Till Eulenspiegel
          • • Levels versus Skills, who uses them and when. Andy Cink
        • Levels versus Skills, who uses them and when. Caliban Tiresias Darklock
        • Levels versus Skills, who uses them and when. Justin Robinson
        • • Levels versus Skills, who uses them and when. Andy Cink
          • • Levels versus Skills, who uses them and when. Mik Clarke
            • • Levels versus Skills, who uses them and when. J C Lawrence
              • • Levels versus Skills, who uses them and when. Koster, Raph
                • • Levels versus Skills, who uses them and when. J C Lawrence
                  • • Levels versus Skills, who uses them and when. Koster, Raph
                    • • Levels versus Skills, who uses them and when. Adam Wiggins
                      • • Levels versus Skills, who uses them and when. Marian Griffith
                        • • Levels versus Skills, who uses them and when. J C Lawrence
                          • • Levels versus Skills, who uses them and when. Marian Griffith
                            • • Levels versus Skills, who uses them and when. J C Lawrence
                            • Levels versus Skills, who uses them and when. Alex Oren
                        • Levels versus Skills, who uses them and when. Mik Clarke
                        • • Levels versus Skills, who uses them and when. Adam Wiggins
                          • • Levels versus Skills, who uses them and when. J C Lawrence
                            • • Levels versus Skills, who uses them and when. Koster, Raph
                              • Levels versus Skills, who uses them and when. Mik Clarke
                              • • Levels versus Skills, who uses them and when. Matt Wallace
                                • Levels versus Skills, who uses them and when. Adam Wiggins
                              • Levels versus Skills, who uses them and when. Adam Wiggins
                      • Levels versus Skills, who uses them and when. Marian Griffith
                      • • Levels versus Skills, who uses them and when. J C Lawrence
                        • Levels versus Skills, who uses them and when. Koster, Raph
                  • Levels versus Skills, who uses them and when. Caliban Tiresias Darklock
                  • Levels versus Skills, who uses them and when. Andy Cink
                  • • Levels versus Skills, who uses them and when. Koster, Raph
                    • • Levels versus Skills, who uses them and when. Caliban Tiresias Darklock
                      • • Levels versus Skills, who uses them and when. J C Lawrence
                        • • Levels versus Skills, who uses them and when. Caliban Tiresias Darklock
                      • Levels versus Skills, who uses them and when. Andy Cink
                      • • Levels versus Skills, who uses them and when. Koster, Raph
                        • Levels versus Skills, who uses them and when. Caliban Tiresias Darklock
                  • Levels versus Skills, who uses them and when. Marian Griffith
                  • • Levels versus Skills, who uses them and when. Caliban Tiresias Darklock
                    • Levels versus Skills, who uses them and when. Koster, Raph
                  • Levels versus Skills, who uses them and when. Mik Clarke
                  • • Levels versus Skills, who uses them and when. Koster, Raph
                    • • Levels versus Skills, who uses them and when. Adam Wiggins
                      • Levels versus Skills, who uses them and when. J C Lawrence
                      • • Levels versus Skills, who uses them and when. Holly Sommer
                        • • Levels versus Skills, who uses them and when. Adam Wiggins
                          • • Levels versus Skills, who uses them and when. J C Lawrence
                          • Levels versus Skills, who uses them and when. Mik Clarke
                      • Levels versus Skills, who uses them and when. Matt Wallace
                      • • Levels versus Skills, who uses them and when. J C Lawrence
                      • Levels versus Skills, who uses them and when. Mik Clarke
            • Levels versus Skills, who uses them and when. D. B. Brown
        • Levels versus Skills, who uses them and when. Mik Clarke
        • • Levels versus Skills, who uses them and when. J C Lawrence
        • Levels versus Skills, who uses them and when. J C Lawrence
        • • Levels versus Skills, who uses them and when. Vladimir Prelovac
          • • Levels versus Skills, who uses them and when. J C Lawrence
            • • Levels versus Skills, who uses them and when. Caliban Tiresias Darklock
              • • Levels versus Skills, who uses them and when. Nathan F Yospe
                • Levels versus Skills, who uses them and when. J C Lawrence
  • Levels versus Skills, who uses them and when. J C Lawrence
  • Levels versus Skills, who uses them and when. Jon A. Lambert
  • • Levels versus Skills, who uses them and when. Travis S. Casey
    • • Levels versus Skills, who uses them and when. Caliban Tiresias Darklock
  • Levels versus Skills, who uses them and when. J C Lawrence
  • Levels versus Skills, who uses them and when. Petri Virkkula
    >>>>> "Raph" == Koster, Raph<rkoster@origin.ea.com> writes:
    
    Raph> [And yes, right here someone is going to say they implemented
    Raph> remembering every room visited, or every room remembering who
    Raph> visited it, and don't have that problem, and once again I'll
    Raph> shudder at the data storage their mud entails.
    
    I couldn't left this one unanswered ;-)
    
    Our system contains multiple LPMud save files, one per "area"
    (in the practice per wizard). They take 1.3MB disk space, and
    not all of them are in the RAM at the same time (that depends
    how players are travelling around the mud). The save files
    contain object-path -> room number mapping. Room numbers are
    reserved dynamically, ie. when a room is first time ever
    entered it gets its unique room number. Currently there are
    over 13000 room numbers reserved (not all rooms give explore
    points).
    
    Every player object contains a bit string (6 bits
    stored in a byte). Thus a player who has explored all those
    13000 rooms takes around 2kB RAM. In the practice nobody has
    explored all of those rooms, see
    <URL:http://www.bat.org/Batmud/mudinfo/plaques/top_explorers.html>
    for real (though a bit old) percentages.
    
    The nice thing in the dynamic allocation of the room numbers
    is that the explore percentage rise steepens as players find
    unvisited rooms. For example, if player A has found 4 rooms
    out of 5 visited rooms and then finds a new unexplored room
    his/her explore percentage goes from (4/5) 80% to (5/6) 83%,
    not to 100%.
    
    Assuming an average 50% explore coverage, the mud takes around
    300*1kb00kB RAM with 300 peak player count (plus the
    object-path -> room number mappings) to maintain the explore
    system. With 24000 player base disk space required by per
    player data is around 24000*1kB$MB.
    
    Additionally we have a tracking system: all rooms keep
    player/monster movements for 5 minutes in the RAM. That data
    is not used by the explore system. Our tracking system is
    something like quzah was visioning, though we do not take
    account terrain type, only tracking skill percentage is used
    when a player (usually a ranger) tries to read tracks left by
    a fleeing player/monster.
    
    Is the system worth of the used RAM and disk space? I think
    so. Our machine has 1.25GB RAM and 17GB (mirrored) disk
    space. Long before RAM and disk space are exhausted we have
    run out of CPU power (and it is easier to buy more RAM
    and disk than CPU power).
    
    
    Petri