Being Epic

This article originally appeared in the now-defunct online magazine Imaginary Realities. It talks about MUD administration, and draws on my experience working with Armageddon MUD, the world of Zalanthas. For those who don’t know what a MUD is, it’s a text-based roleplaying game. Here’s the wikipedia article on MUDs.

One of the sad truths of the mud world is that there are never enough coders. Builders aplenty, brimming with fresh idealism and plans for entire zones, appear (and sometimes disappear) at the drop of a hat. But coders are the unicorns of the mudding world, seldom glimpsed and ardently pursued. We are lucky enough to have three dedicated coders on Armageddon MUD: Morgenes, Tenebrius and Tiernan, as well as a few other staff members willing and able to wade through the bugs file and tinker with things upon occasion. How, then, does an administrator keep these rare beasts happy? The following four steps may help.

1) Communicate: When asking for new code, try to let the coders know exactly what is desired. For example, instead of ‘Let’s make archery more complicated,” a staff member might propose “Let’s put a range on archery, so the farther away the target is, the harder it is to shoot it.” A full description of the the idea, perhaps including examples, such as fake logs showing what the idea will look like when being used, helps make sure the originator of the idea and the coder are on the same track as far as things like syntax and usage are concerned.

The same holds true for bugs. Describing how it’s supposed to work as well to how it’s working right now helps clarify ideas. Coders want to know if the bug is REALLY a bug, or something being reported because it doesn’t work as the reporter feels it should.

With bugs, give the coders as much information as possible, including how to reproduce the bug. Examples by way of logs are great, and if they include some form of error message (or message that they’re getting that shows it’s an error), it often allows the coder to track down what section of the code needs to be worked on.

Make sure people aren’t bumping into each other. On Armageddon, we’ve got a coder’s board, where people post changes as they make them. This alerts fellow team members to what they’re doing and is also helpful if unexpected bugs crop up, enabling people to track exactly what got changed and when. Two people should not be working on the same idea at once unless they know it, and can divvy up the work accordingly.

2) Have a purpose: Will it get used? Is it something players are asking for? This one is a matter of ego, but we’re all human and we all do have egos. Seeing their work getting used, regularly and as envisioned, is a reward beyond any thanks or congratulations other staff members can give a coder. Track player requests, through entries in the bugs/ideas/typos files as well as emails to the account and posts on the general discussion board in order to convince a coder that the players want, and will use, something.

Generally, with new ideas figure out how they are moving towards some goal. A piece of code like a new skill is going to sound more interesting if it fits into some overall purpose, such as a master plan of non-combat related skills for the economy than it would if it is just a random idea. You are also going to end up getting more out of the idea if it is part of a greater whole.

Make it innovative. Some coders like to be trail breakers, to feel that they’re not just playing catch-up with another mud, but are creating ideas and concepts new to the mud community. Some ideas get requested to ‘balance’ things out between groups: guilds, or races, or mount speed. When a coder starts to feel like the code they’re doing that day only works to nullify a change made last week, then they’re going to start wondering what they will be asked to implement tomorrow.

3) Share the work: Do as much of the grunt work as you can for the coders, including helping thoroughly test, providing help files and documentation, and fleshing things out. In testing, give coders information about what is not working and how to recreate the result. Be precise about what needs to be changed: not ‘the plague of locusts spell needs to do more damage’, but ‘it needs to do about twice the damage it is now.’ When something requires a new help file or modification of an existing help file, do not expect the coder to do it, but supply it yourself. If it is something that requires building, provide the items. Teamwork of this kind, when it is working well, is terrific, and will often produce amazingly cool results.

4) Appreciate: Good coders can never be praised sufficiently. We try to make sure that players know who is responsible for new and interesting changes, by posting information about them in the news as well as in our weekly update, which is a mailing our players can subscribe to, which provides information about changes, staff and world news, upcoming recommended playing times, etc. When players write in with compliments or feedback on a code change, make sure that the note gets passed along to the person , as well as that the coder knows how cool or slick you think the ideas they have implemented are as well.

There is a tendency sometimes to regard coders as resources that spit out code at request. But the fact of the matter is that treating coders in that way will frustrate both sides, leading coders to become discouraged and unmotivated to implement new ideas and builders to feel that their coding needs are not being met. These four points may help avoid such frustration.

This article originally appeared in the April 2001 issue of Imaginary Realities.
© 2002 Cat Rambo. All rights reserved.

I spend at least a little time each day looking at social media news and new stuff and track the most useful links here. If you enjoyed last week’s Pinterest Analytics post, are interested in using that social network more effectively, and have an hour where you need something to listen to, I recommend this webinar. Among other things, I found out why people do those long tall pictures/infographics (which was obvious once I thought about it, so everyone else in the world may have already figured that out).

So here’s some thoughts after spending some time poking at an app provided by Seomoz.org, Followerwonk, a Twitter Analytics tool.

So – why be interested in analytics of any kind, whether it’s Google, Pinterest, Facebook, or Twitter? Because numbers let you know what works and what doesn’t in driving traffic to your site. Figure out what works and do more of that. Figure out what doesn’t work and do less.

Followerwonk gives you a number to track, Social Authority, that measures your influence on Twitter. Its formula is based on three factors:

1. The retweet rate for a user’s last few hundred tweets
2. How recent those tweets were
3. A somewhat nebulous thing that Followerwonk explains as “A retweet-based model trained on user profile data), which I believe is their way of saying, “Part of our algorithm is hidden so users can’t game it, but there’s something there, really.”

Personally, I’m wondering whether someone favoriting your tweet has any influence. Based on what they’re saying here, it doesn’t, and it seems like it should.

But you don’t want to know your social authority score so much as someone else’s. Followerwonk is intended to help you identify followers with a high social authority score so you can target them with your message.

With that in mind, here are the main capabilities:

• Search Twitter bios: Identify people with specific keywords in their bios or other traits such as number of followers, age of account (Followerwonk notes about this figure: “The age of an account is an interesting way to measure value. Users who have been on Twitter for a while are early adopters, and generally more valuable than newbies. As well, there is a higher percentage of spam accounts in newer user segments (as Twitter has not yet cleared them out).”), and Social Authority. This is actually pretty powerful. You can narrow things down by geographical location and set min/max number of tweets, followers, and following.
• Compare users: Compare several Twitter users in terms of the users they follow or those who follow them. It’s certainly always nice to see a Venn diagram and know those days in math class learning what they are wasn’t wasted, but I don’t know that I found this report particularly useful, except that it did indicate I should be RTing and @connecting more.
• Analyze followers: Here Followerwonk lets you analyze your or any other user’s followers or who is being followed. You can see them on a map, which is nifty, and I’ve included an example of one. I learned, unsurprising, that my largest group of followers occurs in the same geographical region I’m in, but also, surprisingly, that the next largest group is in the Southern United States. Other ways to sort them includes by gender, social authority rank, follower/following accounts, tweet numbers, language, the time they’re most active, as well as a couple of interesting word clouds generated through bio information.
• Track followers: Changes to your social graph are presented in this tab, but only if you’re paying for this functionality. Otherwise all you can do is see this data for the Twitter user @followerwonk.
• Sort followers: Again, paid functionality, which lets you sort a follower list by social authority, tweets, number following/followed by, and account age.

As with many tools, here you’re been given a taste in order to persuade you to cough up for the paid version. If I had the budget for it, Followerwonk is definitely worth paying for, and it’s just part of the tools from a SEOMoz Pro membership – but they run $99 a month, which is going to be outside the reach for most people working on their own publicity. For a deeper look at Followerwonk, try Gianluca Fiorelli’s How I Use Followerwonk and Why I Love It.

Other Social Media Links of Interest:

I’m looking at this tool and will be writing it up in the future: Buffer, which lets you schedule Facebook, Twitter, LinkedIn, and App.net with the free version, and up to twelve networks with the paid version.

An excellent piece on Goodreads for promotion that should interest writers.

A massive trove of SEO links that I am still going through.

Beth Barany provides some tips for shy writers on how to promote your book on Twitter.

Are you a writer interested in finding out how to effectively promote yourself via the Internet? Sign up for my Building an Online Presence for Writers class. It’s taught online via Google Hangouts and the next session is Sunday, 9:30-11:30 AM PST, July 14.