From: Mike O'B. <ob...@ru...> - 2001-06-07 23:25:20
|
Some considerable poking around (due in part to my very rusty MOO programming skills) has let me to the conclusion that a few changes are needed before you can successfully edit MOO code, or in-MOO mail or notes. There is a property on programmers which is managed by the command @editoption. In particular, new programmers have the +local flag grandfathered, which means that the MOO tries to jam the verb code down to the client for local editing. However, the CVW MOO as delivered uses some authentication code I've never seen before - certainly it's not supported by TinyFugue, or the CVW client. Rooting around on cvw.sourceforge.net, I came across a Java MUD client named "mudsy", which looks like it might be the source of that authentication. Changing the flag to "-local", in order to use the regular MOO editing rooms, does not work in CVW. The room description of the Generic Editor, #48, has been changed to a null string ("") instead of an empty list ({}), as it is on other MOOs. This property is inherited by the Mail Room, the Verb Editor and the Note Editor, and this causes them to blow up (ok, ok, give a traceback) when examined, or when you try to enter them. The fastest solution is to have Admin enter the command: ;#48.description={} Then you'll be able to edit MOO code normally, I think. N.B. I haven't actually tested this! I don't feel like actually adding or changing MOO code till I give myself a refresher course. I've made the above change on our CVW MOO, though. Mike O'Brien |