This Weekend's Classes: Beginnings & Endings (Saturday) and Character Building Workshop (Sunday)

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’m working on revising my fantasy novel, The Moon’s Accomplice, into a big ol’ sprawling fantasy trilogy. This is a rough stab at Book One, and I would love any feedback on what’s missing or needs tweaking. One of the things I’ve been doing is reading other big ol’ sprawling fantasy novels: the Robert Jordan/Brandon Sanderson Wheel of Time series, George R. R. Martin’s Game of Thrones, Pat Rothfuss’s The Name of the Wind and The Wise Man’s Fear, David Edding’s Belgariad and Robin Hobb’s work. I’m trying to figure out what makes for a successful series. What other series would you suggest looking at? (Note that I have read the LotR a bajillion times.)

Things that seem common to all of them:

• Engaging, interesting characters, and plenty of time in their heads
• Landscapes and marvels, plenty of “eyeball kicks“
• Ups and downs, characters enduring vicissitudes and working to do their best in spite of them

Book One begins as Shyra, a Dryad, is brought to the city of Tabat in chains, aboard a steamboat. She doesn’t know why she and a handful of her sisters have been brought to the seaport, but she senses that it’s to no good. They’re already enslaved by a social system where humans rule, asserting their Gods-given right over animals and Beasts, the category into which all intelligent magical creatures like Dryads are relegated.

At the same time far to the north on what the Tabatians consider the rough frontier, young Teo is having similar forebodings ““ his sister is very ill and no one will meet his eyes when speaking of the cure. Teo’s already been rejected by the village because he’s failed to exhibit the shapeshifting powers most of them possess. Finally he discovers that he’s been promised to the Temples of the Moon in Tabat as an acolyte/indentured servant if his sister recovers.

Bella Kanto, premier Gladiator of Tabat, finds herself confronted by a disturbing omen in the form of a lobotomized young Centaur that’s been sold to the Brides of Steel, Tabat’s all-female gladiatorial academy. She goes to see her cousin, Leonoa, a prominent Tabatian artist, only to find Leonoa embroiled in a scandalous love affair. Leonoa shrugs aside conversation, struggling to finish up a few last canvases for a show opening in a few days.

Imprisoned in the Duke’s menagerie, Shyra learns that she and the other Dryads are meant to root and become trees, which will be harvested and fed to the great engine that fuels many of Tabat’s technologies, such as the great Waterfall below the Duke’s castle, the mechanized gondola system that moves the inhabitants from one city terrace to another, and the street lights that show any sign of sorcery or shapeshifter activity on the main streets.

Meanwhile, Teo contemplates fleeing the village. He starts out to do so, only to encounter the Moon priest, Nero, to whom he’s been promised on the road. He and Nero embark on the journey and the stern but sympathetic priest tries to instruct him on the matters he’ll need to know to survive life in the Temple. When Nero breaks his leg, progress is slowed, and even more so when he falls prey to a parasitic fairy in the wilderness. When they arrive at a river town, Nero puts Teo aboard a trade boat, the Eloquent Swan, and entrusts the pilot Archis with getting Teo to the city.

Shyra’s escape is more successful. She manages to slip out of the menagerie and make her way outside Tabat, although she is pursued by the Duke’s Huntress, a relentless and skilled tracker. Nonetheless, Shyra makes her way to the mountains to the northeast of Tabat, where she finds a camp of other escaped Beasts.

When a student of hers from the Brides of Steel is killed in a riot, guilt wracks Bella, particularly since she helped instigate the riot. Political unrest haunts the city, caused by upcoming events: the first election of the Mayor of Tabat, at which point the Duke will reluctantly step down and relinquish his hereditary rule. Bella and the head of the Brides of Steel, Myrila, have a severe falling out. Bella feels she’s been let down by Myrila at a time when she’s facing the pressure of the annual Spring Games. If she assumes the role of Winter and wins, as she has for the past fifteen years, spring will not come to Tabat for another six weeks, impacting trade in a way none of Tabat’s merchants appreciate.

The fireworks of Bella’s victory light the sky the night Teo arrives in Tabat, where he’s entrusted by Archis to Skilto, a merchant-mage handling the Swan’s cargo, more Dryad logs bound for the College of Mages. Skilto lets the boy escape during an accident with one of the logs. Skilto gives the boy’s fate little mind. He’s got his own set of problems, with his father threatening to stop paying his tuition to the College unless Skilto agrees to marry. He’s about to investigate the three candidates presented to him: socialite Lilia Delarose, merchant Marta Lavender, and merchant-historian Ariadne Nittlescent.

Shyra adjusts to life among the escaped Beasts. She’s heartened to hear that they have a plan to free Tabat’s Beasts. They will first infiltrate the city, disguised as the members of the Circus of the Autumn Moon, one of many entertainment troupes drawn to Tabat by the political campaigns and the amount of money being spent on courting political favor. She meets the man who will oversee the Moon, sinister and secretive Murga, whose origins are unknown.

Resolute to avoid the semi-enslavement of Temple life and make his own fate in Tabat, Teo wanders the streets and narrowly escapes being press-ganged. He adapts to life on the streets, begging and scavenging food where he can. He is befriended by a young artist, but disaster follows when his shapeshifting powers unexpectedly manifest. Teo finds himself emperiled by agents of the Duke intent on finding sorcerers and shapeshifters in the city and takes refuge in the Autumn Moon.

A troubled Bella tries to divert herself by taking her friend and sometimes lover Ariadne Nittlescent to the opening of Leonoa’s art show. Skilto and Marta arrive as well, only to find the place the site of a riot incited by the political nature of Leonoa’s paintings, which depict Beasts assuming human roles. Aided by two other gladiators, Bella holds the crowd back long enough to let Leonoa and the other attendees escape.

Skilto’s tried two candidates and found them lacking, although he’s drawn into friendship with Marta Lavender’s father Milosh. When he meets Ariadne at a party, he realizes that she’s the one he’s interested in. Ariadne pays him little mind. She’s too busy thinking about the decision her mother Emilee has made to push Ariadne into political office. Ariadne’s occupied enough with the history of Tabat she’s writing and, unbeknownst to her mother, running a lucrative publishing house specializing in lurid accounts of Bella’s adventures. She’s working on a new book as well, Archis’ account of life on a frontier boat.

Bella agrees to a favor for a lover she picked up at the gallery, only to find herself faced with charges of smuggling deadly sorcerous ingredients. The Duke informs her that he’s sending her with an expedition to the frontier at the end of Book One. Bella’s disgrace leads to a rift between Skilto and Ariadne, deepened when Skilto discovers Archis is courting her as well. Murga hints that he knows Teo’s secret, but Teo avoids any direct discussion of it as he fights to fit in with daily circus life.