> used to extend LPMUDs It would be probably better to say it was used to implement LPMUDs (still is, BTW). Driver without a mudlib - written in LPC - was not

> used to extend LPMUDs It would be probably better to say it was used to implement LPMUDs (still is, BTW). Driver without a mudlib - written in LPC - was not very useful at all. > special wizard's staff A driver of the MUD I worked on had a special set of objects used for introspection/reflection: you could inspect object state, set it's attributes and evaluate arbitrary code "inside the object". These were invoked as normal global commands IIRC. Now I wish we had it coded as a wizard's staff, too :) > almost Emacs-like interactive environment Also similar to image-based Smalltalk or Lisp. It's a pity that it wasn't used to build a Smalltalk-like graphic environment, but in its text form this environment was awesome, too. > the text editor it came with (an ed clone) was terrible OMG, please don't remind me of this. I had to learn ed, because on our MUD we had no FTP access for some time and it was a tragic experience. I was only able to live with it thanks to MUSHClient, which did a great job at handling large amount of text and I mostly just copied the code to notepad and then pasted it back after modification. But, on the flip side, I could never understand why people don't like Vi - it's so much better than ed! ;)