[Forwarded message from Matthew Kerwin] >From: "Michael Barton" <[EMAIL PROTECTED]> >Date: Sun, 17 Mar 2002 23:41:03 -0600 <snip> >The MOO/Mush VR scheme is a really interesting way of handling code. >But I think you'd have more luck starting from a MOO and working >toward a MUD than starting with ROM and working toward a MOO, >simply because the overhead of creating the VR would be a lot >higher than adding a combat system etc to a MOO. That's been suggested to me by someone else, and I personally thought it sounded like a better idea, but I didn't want alienate anyone who though ROM was the better system to use as a base. The question then becomes: would people actually be as interested in it? I know MOOs often tend to have a stigma surrounding them with the MUD community (not all players, but enough). And RP MOOs have a similar stigma within a lot of the MOO community. Would a hybrid system actually get players? Also, would anyone (especially the license holders) have any problem with programmers using the ROM combat system as a guideline to code an RP MOO? I know a lot of people could consider it stealing. I suppose using it as a 'general guideline' would keep you well and truly clear of the grey area surrounding licensing (and since each MOO database is unique, there are no licenses on them); but using the same numbers (to achieve the same balance) and the same combat algorithms would be pushing it a bit. Naming rooms is another issue altogether and I don't even want to think about it. >The Mob/obj/room progs in ROM are a good addition, but obviously >much more limiting than what can be done on a MOO, even if they are >extended greatly. >Developing an interface to expose some of your mud internals to a >perl/python/tcl/etc scripting environment could be a nice compromise >if you want to work from ROM, cutting out a lot of the development >time. Then just plug some sort of abstract event engine into ROM to >drive the scripting and you're golden.
Would that work any better than a MOO, or is it just a fix for those who prefer sticking with ROM instead of porting the whole thing to MOO Code? Matty - who doesn't have the time or resources to do any of this anyway, but might when he gets his computer back ----- I'm not dead.
