armageddon

One of the things I’ve decided to do over the next six months is release a number of my stories in small mini-collections in electronic form. Each of these will consist of 2-3 already published stories, with 1-2 ones original to the collection. The first is Halloween Quartet, which contains “Whose Face This Is I Do Not Know” (appeared originally in Clarkesworld), “Niobe in the Rain” (appeared originally in Serpentarius), “So Glad We Had This Time Together” (appeared originally in Apex Digest), and “Pumpkin Knight,” which is original to the collection.

The next one will be Desert Quartet, which will contain “Aquila’s Ring,” (originally appeared in Light and Shadow II), “Karaluvian Fale” (appeared originally in Giganotasaurus), “Her Eyes Like Sky and Coal and Moonlight” (the title story from my second collection), and “Mirabai the Twice-Lived,” which is original to that collection. It’ll also contain an essay about the world in which all of those stories are set, that of Armageddon MUD, and my experience working with it.

Other e-projects in the works: a mini-collection of flash, a mini-collection of superhero stories, and something collecting blog musings about fiction.

Why do this? Because I do think electronic publishing is clearly the way the industry is going. I’m curious about the power to sell one’s work that it promises the author and I’d like to get in on what seems to be at least the first or second, if not ground, floor of the movement.

I’m lucky in that I have a little bit of a name, acquired through publishing short stories. I don’t know that this would work for someone with no already established platform. And I don’t expect to make a vast sum of money from them. But I do expect there to be a slow trickle. At least – that’s my hope.

How will I spread the word of them? I’ve learned a little from publicizing Near + Far, but I’m not sure how relentless I want to be about pushing these. I’ll certainly talk about the experience of putting them together on here, and will be mentioning them on social networks as well as on my mailing list. Suggestions are welcome, as always 😉

If you want to sign up for that mailing list, by the way, which will come no more than once a month and mention new publications and classes, fill it out here:

#mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif; }
/* Add your own MailChimp form style overrides in your site stylesheet or in this style block.
We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */

This essay originally appeared in the January 2000 issue of Imaginary Realities.

In 1999, one of the Armageddon MUD coders, Morgenes, put in a command that has no effect on a player at all. It doesn’t get you gold (or obsidian, in our mud’s case), doesn’t raise your skills, doesn’t open the mystic portal to the realm of Waterdeep, or anything at all like that. Yet it was a change that would end up becoming one of the most popular (and most copied) commands ever on the mud, with at least one thread on our discussion board devoted to lavish praise of it from players and staff alike.

The command was ‘think.’ Its syntax is simple. The player types think ‘Woah, hey, did I just see a coin lying in the road back there?’ and gets this back: ‘You think ‘Woah, hey, did I just see a coin lying in the road back there?’ Easy, no? And at first glance, somewhat pointless.

To explain the immense popularity of this command, one needs to understand that Armageddon MUD is more than role play intensive. It’s role play required, and players who fail to stay in character or interrupt the flow of the vast interactive story that staff and players are spinning together usually mend their ways fast. Or are asked to leave the story, usually not in a particularly polite manner. Armageddon’s had the reputation of having the rudest immortal staff on the net for a long time, and while that’s changed considerably, there are, I suspect, staff members who still cherish that attitude to a degree. Players who aren’t staying in character find out fast that it’s not appropriate, or appreciated, on Arm.

Given this, think has proven invaluable to the players whose actions might be incomprehensible to the staff. If a staff member happens to be monitoring a player, and glimpses a few thinks here and there, they know what’s going on and why, precisely, that crazed Krathi is sitting out in the desert. She’s waiting for a vision, which she might choose to supply of her own accord via think, or with which a staff member might help. Why did that elf suddenly take off running? He thought he saw a mantis, gythka staff in mandible, approaching his hiding place. Think not only helps the player solidify what it is she’s doing, but lets the staff know what’s going on as well.

Beyond that, the command’s entertaining and helps the player flesh out the character. Is he thinking ‘Did that templar just look at me?’ If so, he may scurry back into the Labyrinth to hide from the unwanted attention. Perhaps while that wily gypsy is trying to sell her a luck charm, the player’s sitting there thinking hard on how to sell the gypsy out to the dreaded Blackmoon. Personal beliefs, spiritual beliefs, reactions to other characters – all of these, and more, get played out via the think command in a way they never were before. One of my favorite moments was monitoring a conversation between a pretentious noble and the commoner they were upbraiding, who while keeping their eyes downcast was thinking of the multitude of ways that noble could be humiliated.

I’ve seen other benefits as well. At least one character has accidentally typed talk instead of think, and found themselves saying aloud what’s in their head, leading to assorted and interesting results. It slows down some of the fast typists, who otherwise tend to overwhelm other players with the multitude of their emotes and speeches. Some players use it while sleeping, to create intricate and sometimes lurid dreams. We’ve some plans to tie think into the psionic skills on the mud eventually, though that’s a far and future notion. But the benefit to the role playing of the mud has been tremendous. I’d urge other role playing muds to at least…think about putting this command in.

This essay originally appeared in the June 2001 issue of Imaginary Realities.

While finding new immortals for a MUD, MUSH, MOO or MURPE generally isn’t a problem, finding ones who will be a lasting and productive part of the team is. The first couple of weeks for a new staff member on a multiplayer game are the ones where the most mental adjustments are made, and the actions of other staff are often a crucial factor in whether or not those staff stick around. Armageddon MUD provides a good example of how this process can be made as painless as possible for both new and established staff members.

New immortals on Armageddon have undergone a fairly selective process to get there. When a gap is perceived, I post on our discussion board what the gaps are and who is being considered to fill them. In considering candidates, we look for the following:

• Imagination, creativity and writing talent
• Knowledge of the game and its world
• Ability to function as part of the team, including the ability to work with other people, to take input/criticism without feeling diminished or angry and a willingness to work within our guidelines and rules.
• A history of both integrity and trustworthiness
• Sufficient time and energy to dedicate for the game

At this point, I usually feel out the various candidates to see if there’s any of them who would not want to be on staff. Some people prefer to play, and do not wish to come on staff since the mystery of the game would be lost for them. If they’re interested and I haven’t seen past examples of their writing style, I might ask them to write up two or three possible small plotlines and send them to me as a sample. Other staff members post their impressions of the candidates or email in reactions to me, and in a week or so, we come to a consensus about which candidate(s) to approach.

Once that’s done, we set up the new immortal so they can start to read through our documentation, see what’s happening on the immortal discussion board, etc. Then they can log on and begin poking around, usually with another staff member walking them through the basic commands, questions, etc.

People come onto the Armageddon staff at the level of Storyteller. Storytellers run plots and clans, animate NPCs, build (etc). There’s a bewildering medley of options and expectations for a new immortal, so we assign a primary and secondary mentor, usually staff members who have been around for a while and who can answer questions. A lot of time they’re pointing people to the documenation.

We’ve got a lot of documentation, to the point where some new immortals have described it as daunting. But much of that documentation is devoted to helping the new imm: building and procedure guidelines, information about features in the world in the form of Who Is/What is pages and histories of the major clans and noble houses, tutorials for creating objects, NPCs, rooms, and documents. When a new immortal appears, I point them towards specific documents (the immortal discussion board, the guidelines for new staff members, the staff contract, and the mission statement) that I prefer that they read before logging on for the first time.

My feeling as far as new immortals go is that acclimating is much, much easier if they have some definite things they’re supposed to be doing. These should not be overly daunting. Running a clan, for example, requires a lot of organization and coming up to speed, so something smaller, such as helping with one aspect of a clan, or writing NPCs for it, may be a much better initial project.

Additional projects might include: asking them to come up with two or three mini plotlines to run, right off the bat; asking them to work with a plotline already in progress, which has already been planned and sketched out by someone who needs assistance running it; working with npcs in a particular area in order to get a feel for it; filling in gaps in the documentation. Generally, I try not to make these projects building an area, unless it’s a very small project that fits inside another one, like a couple of houses or an oasis.

Giving new staff feedback on what they’re doing is important, but during the initial stage this is not so crucial as is making sure they have resources and teachers who can help them get up to speed on things as painlessly and quickly as possible. Towards this end, make sure they know the rest of the team — I post on the immortal board to let people know who’s coming on board and what they’ll be working on. It’s good if the new staff member posts an introduction themself, with information like what they’re interested in working on, what their areas of expertise are, how they started playing the game, experience with past MUDs, and so on.

It’s also important that new staff know what’s expected of them, in terms of work and conduct. Documentation can help enormously here, but again, it’s having people that can explain things that is the most valuable resource.

In short:

• choose new staff carefully
• make sure new staff members have access to the information and resources they need
• work with them on coming up with clear, measurable tasks so they know what you’re expecting from them

by Cat Rambo (Sanvean of Armageddon and Krrx
This article originally appeared in the March 2000 issue of Imaginary Realities.

Lately, I have been contemplating how clans fit into role playing muds–particularly in getting players acclimated to the mud and helping them survive in that environment. The following conversation takes place between myself and a staff member of Armageddon mud who revamped a defunct clan, the T’zai Byn, and transformed it into an active and well-loved clan. The Byn is perhaps one of the best clans for new players, as well as an experience praised by the vast majority of its participants. (This is the first of three musings on the nature of clans, and what being in/running one means to a player/immortal, with the second discussing a cultural clan, where players begin the game having been born into the clan, and the third outlining some conclusions and problems with clans on role playing muds.)

Sanvean: First off, why were you interested in reviving the Byn, and what sort of clan did you want it to be?

Krrx: Probably the key thing is that I have a passion for the concept. It started when I played in the T’zai Byn a few years ago. I enjoyed playing in a fighting unit where you and your comrades faced death regularly, and had to work together to survive. While I have had very enjoyable times in other clans, I would still rate the Byn as the highlight.

Sanvean: What was the first step in getting them restarted?

Krrx: I outlined what the clan would be–what role and ‘flavor’ it would have. Of course, this was all documented. As the concept developed, the documentation changed. The documents today are quite different from how they were at first. I had ideas about what I wanted the clan to be like, but they didn’t ‘fit in’ as well as they could have with the game world. Nessalin had a big influence on how the clan turned out. The Byn are a lot more low class than I first planned, and the documents reflect that.

Sanvean: How did Nessalin change your intentions?

Krrx: My original vision was of an elite mercenary unit, with a lot of ‘high class’ things. Nessalin encouraged me towards a low class, gritty, down-and-dirty vision of the clan, which fit in better with Armageddon’s overall flavor.

Sanvean: As I recall, you were worried at first that they would not take off.

Krrx: Yes. When restarting the clan, it struck me that to achieve its goals effectively, the clan would have to have strict rules, and that people might not be able to handle it. One example is the regulation where members are not allowed into the ‘rinth, and are not allowed to leave Allanak unless certain criteria are met. The ‘rinth and the wilderness are two areas where a lot of new player characters die, because they insist on wandering in dangerous places alone. It thus makes sense, both in character and out of character, to have rules that limit going to those places.

Sanvean: Speaking of rules, one of the things you have done very well is making the Byn self-regulating. Did you plan on that?

Krrx: To an extent, yes. There are two points here. The first is that I have recruited clan leaders very, very carefully. The second is that because they are trustworthy players, they will help enforce the rules anyway.

Sanvean: When you are looking for players who will make good player character leaders, what do you look for, then?

Krrx: The key things I look for are: (1) out of character trustworthiness, (2) a very high standard of role playing, and (3) regular playing. Of course, it must be appropriate in character that the player character move into leadership. I can elaborate on those points if you like.

Sanvean: Please do!

Krrx: First, out of character trustworthiness. I have put a lot of work into this clan, and I will not put in leadership anyone who does not respect the work I put in, and is not willing to do likewise themselves. Another reason for this criterion is because I am not on-line 24 hours a day. If something happens, I need an honest, trustworthy viewpoint to rely on.

Sanvean: How do you know you can trust them?

Krrx: Trust is not something that can be guaranteed, but I do my best to screen players. I look at past player characters that the player has played. I chat to other staff members about them, particularly if the player played a player character in their clan. If someone is trustworthy, they tend to show it in the way they play the game.

Onto the second point–a very high standard of role playing. Armageddon is a role play intensive mud, with a very high overall standard of role playing. While many players entering the clan do not have this standard, it is a requirement for leadership. If people see leaders role playing well, they will tend to do likewise.

Sanvean: Good role playing seems to mean different things to different people. What is your definition?

Krrx: Good role playing? Thinking and acting in character. Immersing yourself in the role of your player character, and not just playing it like a robot in some shoot-em-up.

Onto the third point–regular playing. This does not mean leaders have to play Armageddon for 6 hours every day. I do, however, expect them to appear in the game fairly regularly. You can not lead if you are not around to lead. Common sense, really.

To sum up, one theme is that I have set limitations on the clan, with the idea that playing within those limitations actually gives players more freedom. It is why we have the law in real life. The law prevents idiots from ruining life for the rest of us. At face value, the law seems restrictive–you are not allowed to drive if you have drunk too much alcohol, for instance. But it is restrictive because: (1) it is logical and sensible, and (2) it protects the greater good–people generally do not like to get killed by drunk drivers.

One of the desires expressed at the very first Armageddon player-staff meeting I ever attended was a yen to move away from “a hack and slash economy,” where players made their income by selling the gear off NPCs (and the occasional PC) that they had killed. How, one immortal noted, could the world be realistic when there was no coded reflection of the material underpinnings of it? How to create this economic reflection was a question that remained in the air for several years, and it was not until discussion of implementing crafting code came up that such a move seemed possible.

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.