[MUD-Dev] Virtual machine design

Eli Stevens {KiZurich} c718157 at showme.missouri.edu
Sat Apr 17 18:15:04 CEST 1999

> -----Original Message-----
> From: mud-dev-admin at kanga.nu [mailto:mud-dev-admin at kanga.nu]On Behalf Of
> Felix A. Croes


>  - Any change can be made without taking the mud down, and takes effect
>    immediately.  If necessary, it can also be instantly undone.  A well-
>    run mud doesn't have to reboot.  This is particularly interesting
>    for commercial muds, where downtime means loss of revenue and/or
>    customer dissatisfaction.

I was wondering what the general consensus on "not having to reboot" meant
to the list.  Obviously, if the power goes off to the system the MUD is on,
the MUD will have to reboot.  What must be supported on-the-fly for a MUD to
be considered rebootless?

Also, for those of us who are slowly cranking on our own code, what features
are the most important to be able to do while the server is running?

For example, adding, modifying etc. rooms in the game world.  Or fiddling
with item stats (like base damage for generic longswords, or whatever).

Silence is almost functional networking code
Eli - mailto:c718157 at showme.missouri.edu
-No man is an island as long as he is on at least one mailing list

MUD-Dev maillist  -  MUD-Dev at kanga.nu

More information about the mud-dev-archive mailing list