Impster's blog

-- Logging started at Sun Feb 17 14:28:36 -0800 2008 --
Êlvïrå says, "Ok, well, welcome everyone to the second in the series of
Managing your MUSH. Logs of the first event were posted on
community.pennmush.org."

Êlvïrå says, "Impster is going to talk about MU* Organisation and the Social
Contract. I don't know any more details than that, so I'm quite excited to
hear what he's going to say. Following his talk, there will be time for
questions and discussion."

Êlvïrå checks everyone's sitting comfortably and has plenty of nice picnic
snacks.

So earlier I said @stielock don’t SUSPECT. But let me tell you what I /really/ think :p.

The thing about @sitelock/SUSPECT and other things like that in my opinion it tends to give new Head Wiz a false since of security kind of along the lines that Microsoft sends out updates to fix things and my parents don’t think that a router is really needed for their one little computer. Just plug the thing right into the DSL line.

So up until now most of these posts have been fairly nice and simple . . . But now for a subject that may rub some the wrong way

@set name=SUSPECT

Now why would you do this? Now there may be very legitimate reasons for setting someone SUSPECT like you think someone is trying to subvert your code/database and you want proof. Honestly for me if you feel that you need to set someone SUSPECT then your better off @booting/@sitelock the person. To me SUSPECT boils down to one simple thing. You want to spy on that person. Now again I don’t normally use MUX but I had been told that MUX doesn’t log commands like Penn does but when I looked at the changes on the tinymux.org I found this:

Ok first off this is not intended to be antagonistic but hopefully thought provoking. I am not intending to point fingers at any one person and it seems like this has become more or less the standard way of doing things for right or wrong. This is merely just my opinion and I may be using something that is a bit extreme but I think it is a good comparison.

Once upon a time. . .

Many years ago. . .

The OGR mu* used to hold training sessions for lack of a better term. And they've been saved on here for better or worse ;). I had completely forgotten about this command until I stumbled across it in the +help files. It was a bit broke but I think I've fixed it again. To review these logs see +help logs.

First off I'd like to thank Collette @ M*U*S*H for writing these up for me so many months ago. Someday soon I hope to actually use them in a successful game ;)

Staff are permitted to be dark. Staff are permitted to be dark and listening on channels. Staff are not permitted to be dark in a room with a scene or conversation without announcing themselves.

So. . not to offend anyone and not to point fingers. I thought I put together some basic rules that I think Mu*'s should at least consider when putting a game together or taking over an existing one. Some games need 'em more than others. . .

So I was convinced to help out at OGR/Gateway and should have my head examined. But in trying to give back something to the community I thought I'd try to make my own Care and Feeding list. Hopefully get some response and some feedback to what others have run into and I'm also going to throw what I've posted up here as well. I'm not going to put other people's responses from the Gateway +BB though because I don't feel like I have the right to do that. But they are more than welcome to add it here as well :D.

The original Care and Feeding that people did back in 98 can be found here:

So, I decided to close my latest attempt at a game. The funny thing is since that time in the last 3 days 4 different games have asked me to look at things for them. I suppose I should be honored. But I keep seeing things that gave me issues. So I thought I’d put together a little post about things I learned from my failed games. For those of you that don't know me from jack. I'll give you a little BG on me to start with