Working picnic 6: Ender 'Player Relations: Being a Benevolent Dictator'

Almost an entire hour of discussion, in the form of me rambling on.


"Nothing is idiot-proof. There is always a better idiot."
Ender@M*U*S*H

Sorry for the delay in posting the log.
That's the end of the Managing your MUSH series. I really enjoyed it and am very grateful to all those who contributed in some way, whether by speaking, discussing or simply observing.

I hope to run another series of events soon in a different vein, so look out for announcements here.

If I can help anyone else to run an event or set up a project on M*U*S*H, let me know! I can't code, but I can help advise or point you in the right direction :)

Here's the log from the last session - 'you' in the log is me, Elvira:

Êlvïrå readies everything and gingerly hands out Ender's tiny tacos

Ender says, "Tiny Tacos in the Grove, All's Right in the World."

You say, "Ok, a very good evening and welcome to tonight's Managing your MUSH working picnic which looks to be the sixth and last in the series. Thank you all for turning out for these events. I've enjoyed

them a lot and learnt plenty from them, and I hope everyone's managed to take something from them :)"

You say, "Logs of all the previous events are up on my blog at community.pennmush.org"

(10/225) Space Oddity Êlvïrå says, "Working picnic now starting at Linden Grove. Last call :D"

You say, "Tonight's picnic is being led by Ender who will be speaking on the subject 'Player Relations: Being a Benevolent Dictator'"

You say, "There will be time for discussion following the talk so hang on to your questions until Ender's finished if possible. I hand over to: Ender!"

Êlvïrå claps and steps down

Cuiorne has connected.

Linden Grove(#159RntJ)
[http://mush.pennmush.org/~alansz/mush/lindengrove.gif]
Although you can observe oaks, elms, maples, and walnuts, the ~~1~~
linden is clearly the ruler of the grove. Tall silver lindens stretch ~111~
to dizzying heights above the other trees, and shorter, bushier ~1X11
"little lindens" offer a pleasant combination of shade and sunlight 1111~
beneath their many small leaves. ~111~
A babbling brook flows on an easterly course through the grove. To the
west, a dripping sound indicates its source. Oranges, reds, and golds light
the fair weather clouds, shadowed in purple, around the setting sun. A soft
breeze blows from the west. There is a full moon tonight.

Players here (+glance for short descriptions):
Elvira Karae Teal
qa'toq Mike Raven
Vadiv Porthos Damascus
Impster Tanaku Ender
Tyr Trinsec Raevnos
Cheetah Cuiorne Wilco
Molikai

Ender nods, taking the stage. "Good morning, afternoon, evening, or endless night between the stars, as your case may be. I am Ender. I am here to talk to you about the concept of Player Relations. This will

be unlike most lectures, in that I have no walls of text for you. We'll start at one point, and end up at another. If we are lucky, we will have learned something on the way."

Ender says, "Player Relations is the current buzzword for 'keeping everyone happy and the game running.' It is the adjuicator, the newbie helper, the RP judge, and the voice of the staff. It is... a

balancing act. Who else has something for what "player relations" conjures in their head?"

Karae says, "The soft voice of reason to stand between players and staff, when things get heated."

Raven says, "The unfortunate who gets blamed by both sides."

Ender nods. "Anyone else? Yes, this is a departure, and yes, I am asking for input." He nods to Raven, as well. "Someone's gotta take the blame."

Cuiorne raises hand and chimes in "Setting expectations, especially on what the world/game is and is not"

Ender nods. "Another thing that people probably noticed was the dictator part. While many of you have concepts that have no dictator, it is my experience in games that ultimately, the game is a dictatorship.

How this dictatorship is run will determine if you're a tin pot dictator running a game with 2 players, one of those players being your alt, or if you are a Ceaser, running an empire of hundreds of players

who enjoy life in the Empire.

Impster consults his bingo card and marks off a few spots.

Ender says, "To that end, lets explore my rambling. To me, a MUSH is a dictatorship. I run it, you play it, and if you don't like it, you can leave. Sounds pretty damn brutal, doesn't it? Not a fun game to

play on, right?"

Raven says, "Depends."

Cuiorne says, "That establishes the expectations:) Than as long as the dictator is fair with the treatment of players - would be fine with me."

Êlvïrå points at news policy aup2: * This is Javelin's game. Play by his rules or find a game that has rules you like better.
Êlvïrå :)

Ruggs has arrived.

From afar, Cuiorne grins "perfect!"

Ender nods. "This is the job of your player relations staff, which should include everyone on staff in some way. You can be a brutal dictator, but as long as people are fair and the rules are understood,

then people will play. And Elvira brings up my next point. M*U*S*H is a dictatorship. Javelin is a Ceaser, not a third country dictator cutting people's limbs off cause they looked wrong at some girl he

might want."

Ender says, "But, player relations is more than knocking heads, obviously. Its about being there for the players, helping them to get into the game and have fun. I've seen, in the past, too many people talk

about PR as if its strictly an enforcement position."

Long distance to Cuiorne: Elvira nodnods :)

Ender says, "This should show, actually, that Player Relations is less a fixed positional idea, and more something that everyone should be doing. You can have dedicated PR personnel. You can have, within

that personnel structure, those who enforce your rules and those who promote RP."

Ender says, "Your PR staff, dedicated or everyone, should also be looking at the user interface. Because that's how the game relates to the players. Talk with your coders, have your coders talk with you.

Ensure that stuff is easy to work with. I am horrible at this. On several games, I have powered armor that requires a bunch of @flags to operate, as it does stuff like @tel me around, @emit and @pemit. My

commands are all +ashi/*. Some poor SOB PR Admin once tried to use my armor object, and finally went, "How the hell do you work this thing?!" That's bad interface. Imagine if this was a globals code?"

Ender says, "If nobody can work your code, that's a player relations problem. Especially if you have rules like, 'If its not coded, it doesn't happen.' Well, that rule is great, and PR is in charge of

enforcing it... So they should also be dealing with the disconnect between how the players and the code relates. Yeah, I'm gonna hit you over the head with "relates.""

Ender says, "Without maintaining any semblance of segues, lets talk about softcode. Would anyone consider the MUSH softcode security, either global or player objects or attributes, a player relations

problem? Or is this strictly something for the coders?"

You say, "I think problems with the security might be a player relations problem..."
You say, "FOr example, dealing with a player who intentionally hacks something. Or alternatively, if a piece of code harms a player or character in some way, unfairly"

Ender nods. "I believe it too."

You say, "Or if it prevents a player from doing something they should be able to do or in some other way makes a player lose faith in the game"

Ender says, "You bring up a good point. If you're running an IC game... Part of the responsibility of the administration is to make it fair, or at least make it _appear_ fair."

Ender says, "When I was on Strange New Worlds, I worked for Starfleet Engineering Command. The Starfleeet Master Computer was an IC object, and SNW's administration would scream 'If you can do it in the

code, you can do it!' Big mistake. I simply gave myself level 10 access by using an open set() attribute. I had the ability to enter any SF facility or ship, because the computer let me. I knew every prefix

code, something that allows for remote access to vessels. I basically had the computer access of an Admiral, as a Captain.""

Ender says, "I routinely scream that you can secure your softcode using best practices. And that you should do it. Perform code audits. Ensure that the 5 year old can't break your code in new and interesting

ways. Be savvy to code attacks. Not everyone out there is going to @nuke your DB and scream KLUDGEMUSH FOREVER. Someone might just give themselves level 10 access on your super duper computer and then steal

a ship."

Ender says, "Or edit their hitpoints to over 9000."

qa'toq says, "TWINK!!!!"

Ender says, "Now, I promised people that I'd talk about my insane concept for security practices. I don't actually suggest anyone try this."

Ender idly shoots qa'toq in the head. "Twinks are people who do not have the mandate of heaven." Holstering his sidearm and continuing, Ender says, "Its really simple. Those bits that we think of as staff?

Lose them. Players do not need wizard. Hell, they might not even need royalty. Login as #1. Create one or two players with long passwords. Set the wizard. Figure out who absolutely needs to control every

object on the game other than #1. Then give them the password to build their globals code."

Ender says, "If you're inventive and have a good understanding, you can create empire/faction level zone master rooms and zone master objects, and use those as 'local wizards.' The point being, limit the

amount of control that people have."

Ender says, "This is the point where you all go, 'wtf, lose my wiz bit? Whyfor?' Now, how many of you actually use your wiz bit's ability to read/write any object in the DB, control any object in the DB

(@fo, etc)?"

Ender says, "Anyone?"

Raven does building and coding both, hooks up new building to the IC grid, puts globals in the master room, and the like. Our zones are geographical rather than functional.

Karae blushes, and doesn't actually have a running MUSH atm.

You say, "no need to blush, Karae :)"

Ender points to Raven, "Do you use builder characters, or do staff own rooms and objects?"

Raven says, "Different builders for different geographical locations."
qa'toq says, "ewww, builder characters ftw"
Ender says, "So, if I were to @nuke you today, what would you lose?"

Ruggs agrees, actually. And too often wizbits can become temptation to peek here and there at player objects. It's better to remove the temptation, but still have it there when you need it.
Raven says, "Not too bad. I try to @chown everything to the builders for the reason that I may not be there forever."

Ender laughs. "I come from TrekMUSHes. I've had to examine players to see why their uniform wasn't working with the multi-descer, and damn if they didn't have a meticiolusly detailed nude desc."

Raven doesn't believe in coders making themselves indispensible.

Ender says, "So, I think we've covered everything I was going to ramble on. To recap..."

qa'toq says, "boooo! i want my money back, this lecture wasn't long enough!"

Ender says, "We're not done."

qa'toq says, "oh, nevermind then"
qa'toq says, "continue"

Ender says, "M*U*S*Hes can be a dictatorship, either some African Junta or Rome. It really depends on how fair your policies are and how well your staff and game relates to its players. You can be hard, but

if you are fair, people will want to play there. If you are soft, but not fair, then people will get pissed off quick and leave. And then we get into problems."

Ender says, "Player Relations is a buzzword. Its more than just enforcing the rules. Its being there for the players, ensuring that they're having a good time and that the game (staff, code, theme, and

building) is up and running. That it works. That I'm not suddenly getting 9000 hitpoints or calling do_kill_player() cause you left a bug."

Ender says, "Security is an important aspect of player relations. Nobody wants to play on a game where any idiot can cheat. Unless they are a better cheat."
Ender says, "And finally, think about how you use your bit. Is Wizard a title, or is it simply a flag used to control permissions for objects the object does not own?"
Ender says, "Lets do some discussion, Elvira, and field some questions."
Ender says, "And somebody wake qa'toq, I shot him on stun."

qa'toq is awake
Karae pokes qa'toq with a blunt spoon.
Stoko has arrived.
qa'toq is idle again now to go for a meeting with his work mate

You say, "let's do it, Ender. Anyone got any questions or comments? :)"
Ender says, "Questions, people, you must have some."
You say, "I think everyone's scared you might shoot them ;)"
Ender says, "I only shoot qa'toq."

Ruggs was surprised you weren't banned after the Captain/Admiral trick, personally. How did the MU handle it?

Ender says, "They were in the middle of an OOC civil war, and ICly I was the right hand of God."

Ruggs says, "Not to be hostile...I'm just surprised. And ouch. :)"
Ender says, "It also took them 4 RL months to notice."
Ender nods.

Mike says, "They can't really punish you after saying that anything you can make the code do is legal, though, without a big PR battle."

Ender idly notes that I was the right hand of Raster, not Teech.

Ender nods, "And they were failing on the whole concept of PR in the first place."

Ender says, "Does anyone remember the MUSH Documentation Project?"

Tyr says, "Yes."

You say, "I have a question :)"

Mike says, "The name rings a bell, but i don't recall the details much."
Ender says, "Pray continue, Elvira."

Disraeli has connected.

You say, "Ok to bring this back to the topic of management... there's a concept in management theory that everyone in a company is a part-time marketer. To what extent are all the staff on a MUSH player

relations? Is it appropriate to have an antisocial code wizard for example?"

Mike says, "Goes back to something Ender said before, IMHO. Code wizard? Yes. Code staffer? No."

Ender says, "The antisocial code wizard needs to be trained in UI and best security practices. He's also going to need to learn how, or know how, to interface with the dedicated PR staff."

Ender says, "There's a level of responsibility, yes, but unless you're paying your staff, it should be what they're personally comfortable with."
Ruggs says, "I suppose if antisocial means quiet and sticking to a small room, then I wouldn't see the harm. If it mean harmful in cude or harmful commentary or actions then yes."

Ruggs says, "Or as long as they can interface well with the rest of staff. I suppose that 'reclusive' would be alright, while actively hurtful to the social sphere wouldn't be?"

Mike says, "You need to be comfortable that any one staffer can handle a situation/question/problem that might arise if they're the only one on when it happens and someome types +staff to look for help. They

don't have to be perfect or know everything, but at least diffuse a situation politely until someone who can deal with it fully gets on."

Ender nods.
Ender says, "I enjoy the +saction system."

Karae looks blankly at Ender.

You say, "+help sanction, Karae :)"

Ender says, "Oh, here we go. :) Sanction System is a creation of a friend of mine, here on M*U*S*H."

Ender has recoded it, from scratch or from his code, over and over again each MUSH I start.

You say, "actually no. Hang on"

Ender says, "Mine is even MORE convoluted than this one, as its automated."

Ender says, "news policy sanction"
You say, "that's the sausage"

Ender says, "So, here's what would happen with an idiot player in my convoluted system. Non-PR admin Bob sees Idiot_Player say, 'Words Words Words' on Public, against the AUP."
Ender says, "He types +sanction/channel Idiot_Player=No you cannot say 'words words words' on public."

Ender says, "A bbpost is made on a board that only admin can read. The player is @pemitted and @mailed a copy of the sanction. No, he doesn't know who did it. If its his first channel offense, its a warning

and includes the suggestion to read rules channels."

Ender says, "Second offense, the channel code stops working for him for 15 minutes, and a PR admin will follow up and see what the disconnect is."
Ender says, "Third offense, 60 minutes. Fourth offense is goodbye channels!"
Ender says, "It'll turn your channels off, your ability to go IC off, or your account off."

Êlvïrå interjects for a moment :)

Tyr wonders why Ender brought up the MDP.

Ender says, "We'll get to that, but first Elvira. :)"

Êlvïrå has to idle a while, but just wanted to say, 'Thanks everyone for coming. And thanks to Ender for a unique talk. It's been a great series and I've really enjoyed it. Logs as always will be posted on

CPO (community.pennmush.org). This is the end of the working picnics for now. I may come back for another season if there's enough interest. I'm also thinking of doing a series of MUSH Showcases so if anyone

wants to do a presentation about their own MUSH, have a chat with me and maybe we can make it happen"

Ruggs cheers for Elvira!
Ender nods.
Tyr says, "Thanks, Elv."
Mike says, "Thanks, Elv. Was a really interesting series, did a great job :)"
Ruggs's enjoyed the chats I've been to. I realize it must have taken quite a bit of work to set all this up.
Ender says, "Remember, folks. I typed and rambled on for an hour, anyone can. I even shot a man!"
You say, "I've really enjoyed them too. They've been quite varied. Remember though, anyone is welcome to do a presentation or event on M*U*S*H. If you want to set something up yourself and want some advice

or help, do let me know."
You say, "Ok, that's it. Carry on with the discussion :)"

Thanks, Ender, for a thought-provoking discussion. I'm sorry I missed it. I like your broad concept of player relations.

Thanks, Elvira, for hosting this series. There were great presentations and I think it's a nice example of how to use M*U*S*H to bring something to the community.