I get a lot of reactions to “Don’t Prep Plots” that basically go like this: “Oh, yeah. I don’t want to railroad my players, but…”

The justification or rationalization which follows the “but” varies. There’s a consistent recognition that roleplaying games aren’t really designed for linear, predetermined plots, but since the vast majority of the media we consume is purely linear (even most of the “interactive” stuff) those creative instincts get buried pretty deep in us.

One of the most common versions of the “but” I hear is, “But I don’t want them to kill my bad guy!” The justifications for this vary from a strictly predetermined “finale” that’s being ruined to the more seductive version of convincing yourself that your players won’t be “satisfied” if the bad guy is “prematurely” knocked off.

These instincts aren’t necessarily wrong: Pulp fiction is filled with scenes where the heroes impotently watch the bad guys escape, building the sense of rivalry between them and baiting our appetite for the finale of the story. It’s an effective trope.

But I don’t think railroading is the only way to achieve that trope at the gaming table. Nor do I think it’s the most effective: When you push your thumb onto the scales of fate in order to predetermine the outcome of your game, you deflate the value of that outcome. If you do it poorly (or simply do it often enough), the anger and frustration of the players will stop being focused on the NPC villain and start focusing on you. The value of the trope becomes depreciated when it’s achieved through artificial ends.

CREATING MEMORABLE VILLAINS

What I recommend instead is a three-pronged approach:

First, build tension between the PCs and the villain without using direct confrontations between them. Give the bad guy minions. Have the bad guy do horrible things to people, places, and organizations that the PCs care about off-screen. Social interactions in situations where the PCs won’t be able to simply shoot them in the head without serious consequences also work well to build a personal relationship. (As do taunting communiques and phone calls.)

Second, when you’re prepping your scenarios include lots of bad guys. You’re probably doing this any way, so the real key here is to simply refrain from pre-investing one of these guys as the “big villain”. Basically, don’t get attached to any of your antagonists: Assume that the first time they’re in a position where the PCs might kill them that the PCs will definitely kill them. (This attitude will help to break any railroading habits you may still be secretly harboring.)

Third, remember that people in the real world usually don’t fight to the death. Have your bad guys run away. And not just your “big villain” (since you won’t have one of those any way): Unless their back is truly to the wall, most of the people your PCs fight should try to escape once a fight turns against them. (If you’re finding it hard to break the “fight to your last hit point” habit, try experimenting with some morale rules.) Most of them will probably still end up with a bullet in the back of their heads, but some of them will manage to escape.

The ones that escape? Those are your memorable villains. Those are your major antagonists.

This is the crucial inversion: Instead of figuring out who your major bad guy is and then predetermining that they will escape to wreak their vengeance, what’s happening here is that the guy who escapes to wreak their vengeance becomes the major bad guy.

MEDIA FAUX-EXAMPLES

Consider Die Hard for a moment. As written, this film is a great example of our first principle: The antagonism between John McClane and Hans Gruber is established almost entirely without any direct interaction between the two of them: Gruber takes McClane’s wife hostage. They talk to each other through telecommunication devices. Gruber sends his thugs to fight McClane elsewhere in the building.

The exception to this is the scene where Gruber pretends to be one of the hostages. This is actually a really clever device that heightens the conflict between McClane and Gruber by allowing them to directly interact with each other. But if this was a game table, what would happen if the PCs saw through Gruber’s bluff and put a bullet through his forehead right then and there?

It doesn’t matter.

Remember our second principle? Lots of bad guys. So now Die Hard becomes the story of the hot-headed Karl Vreski taking control of Gruber’s delicate operation and blowing it up in a mad pursuit for vengeance. Maybe he starts killing hostages and becomes the most memorable villain of the campaign when he throws McClane’s wife off the top of Nakatomi Plaza.

Okay, so cycling through the org-chart of Villains, Inc. works when you’re facing a team of bad guys. But what if the PCs really are just facing off against a single nemesis?

First off, remember that not every challenge needs to be of epic proportions: Sometimes you run into some goblins in the woods and you kill them and you move on. You don’t need every goblin to murder the priestess’ cousin or become the sworn blood-enemy of the paladin.

Second, even the most memorable villains from fiction were often part of Villains, Inc. even when that isn’t immediately obvious. For example, consider Dracula: Wouldn’t it be really unsatisfying if Jonathan Harker sneaked into Dracula’s tomb at the beginning of the book and staked him through the heart before he ever went to England? I mean… this is the Dracula, right?

Remember, though, that Dracula is only the Dracula because that didn’t happen at the hypothetical gaming table. We didn’t know that he would become obsessed with Harker’s wife and kill Mina’s best friend in pursuit of her. We discovered that during play. So let’s pretend that play had gone a different way: Harker stakes Dracula and heads back to England, satisfied that he’s destroyed an ancient evil. It’s a beautiful, happy ending…

… until the Brides of Dracula pursue him to England seeking bloody vengeance.

As a final example, remember that you need to embrace the whole package: You have to allow your bad guys to die indiscriminately and you need to include lots of bad guys in your scenario. If you only prep the “big villains” and then allow them to die indiscriminately, what you end up with are the Star Wars prequels: Darth Maul is replaced by Count Dooku is replaced by General Grievous… and none of them ever achieve enough narrative weight to make you really care whether they live or die.

EXAMPLES FROM THE TABLE

As I’ve mentioned in the past, faux-examples from other forms of media can be useful due to the common understanding of the source material, but can be somewhat misleading because the official version of events from the original media lends a patina of canonicity that shouldn’t be true of actual tabletop scenarios. So let me also take this opportunity to offer a handful of examples from my Ptolus: In the Shadow of the Spire campaign.

SILION: Silion was a cult leader. Using our first principle, I built her up in a variety of ways: Her name was referenced in early foreshadowing. The PCs tangled with her thugs and were targeted for retaliation by her organization. She was also incorporated into the background of a new PC joining the campaign, becoming responsible for murdering the PCs’ family and destroying their village.

Eventually, the PCs managed to track down her lair. They snuck in, found her digging through a box of archaeological artifacts, rolled a critical hit, and put an arrow through the back of her skull. She literally never even got a chance to look them in the face.

My players gleefully tell this story at almost every opportunity. They love it. It’s one of their favorite moments from the entire campaign.

Why did it work? Because when you heavily invest a villain through foreshadowing, the payoff of defeating them is massively satisfying. It can be argued that this sort of thing might not work as well in other media (although consider that Luke’s actual confrontation with the Emperor in Return of the Jedi, after building up to it over the course of three films, lasts almost no time at all), but in a roleplaying game the audience is synonymous with the protagonist. Your players don’t want to be handed their quarry on a plate, but a quick kill shot isn’t a gimme: It’s a reward for all the work that got them to the point where they could take the shot.

ARVETH: Arveth was a mook. She was captured by the PCs, questioned by Tithenmamiwen, and then cut loose. When Elestra tried to sneak back and slit Arveth’s throat to stop her from warning the other cultists, Tithenmamiwen stopped her.

But then the cultists caught up with Arveth: Believing that she had betrayed them to the PCs, they tortured her and even cut out her eye. Eventually concluding that Arveth was still loyal to their cause, the cult gave her a team of assassins and sent her to kill Tithenmamiwen. This was our second principle: Use lots of bad guys and develop the ones who survive. (In some other campaign, Arveth could have easily been cut down randomly during combat and completely forgotten by the next session.)

Arveth nearly succeeded in her assassination attempt before the rest of the party showed up. While the rest of her team held the party at bay, Arveth managed to escape (barely evading Tithenmamiwen’s angry pursuit). This was our third principle: When they’re losing a fight, have your bad guys run away.

At this point, things transitioned to the first principle: Arveth used a magical artifact to send horrible nightmares to Tithenmamiwen (often featuring Arveth cutting out Tithenmamiwen’s eye). She issued threats to Tithenmamiwen’s friends. She placed a bounty on her head.

The PCs would fight her again. This time Arveth was teamed up with a medusa who turned two of the party members to stone. Arveth carved an eye out of each of the statues before making her escape once again.

By this point, of course, the PCs were absolutely furious. Tithenmamiwen, in particular, had a rage which burned so white hot that her alignment shifted: She had shown this bitch mercy and she was repaid with endless torment. I don’t think I’ve ever seen such intense hatred focused towards an NPC before. It reshaped the entire course of the campaign.

Arveth was a mook no more.

When she finally died, the cheers of the players rocked the house. They literally took her miniature as a trophy so that it could never be used in a game again.

WUNTAD: Finally, here’s an example of me breaking (or at least bending) my own rules. Following the scenario laid out in the excellent Night of Dissolution campaign by Monte Cook, Wuntad and a gang of other chaos cultists show up just as the PCs finish clearing out a dungeon. The intention of the scenario is really clear: The PCs have been beat up. Wuntad and his cultists should have a really easy time of beating them into unconsciousness and then stealing several key items that the PCs had taken from the dungeon.

Stealing the PCs’ stuff? That’s pretty much guaranteed to piss them off for the rest of eternity.

Deliberately designing an interaction to create a major villain is against my “rules”. But it worked.

What I consider the key thing here, however, is that I still wasn’t invested in a particular outcome: Common sense showed that the outcome was likely, but I still wasn’t predetermining it.

What if Wuntad had died? Well, I had reinforced the scenario by following my other design principles: He was supported by lots of bad guys (including Silion from the example above). If he had died, somebody else would have stepped in and taken control of the cults. (Which is not to say that these characters are interchangeable: Killing Wuntad would have made the PCs a major target in the campaign a lot sooner. Factions within the cults probably would have broken away from the new leadership. And so forth.)

Similarly, returning to one of our faux-examples for a moment, common sense tells you that the leader of the terrorists who have taken over the Nakatomi Plaza is more likely to become John McClane’s nemesis than one of his mooks. You don’t have to abandon that common sense in order to follow the principles of RPG villainy.

FURTHER READING
The Railroading Manifesto
Node-Based Scenario Design
Gamemastery 101

Go to Part 1

Every piece of evidence surrounding the authorship of Richard II: Thomas of Woodstock points to one of two truths:

(1) If the play was written in the early 1590’s, then Shakespeare must have written it. (If not, then its deep similarities to later Shakespearean plays would indicate that Shakespeare spent the bulk of his career cribbing from the work of an anonymous and apparently forgotten playwright.)

(2) If the play was written after 1600, then Shakespeare probably did not write it. (The relative crudity of the play coupled to such a late date makes it unlikely as the sequel to the polished Richard II, and makes it far more plausible that the play’s similarities are the result of someone cribbing from Shakespeare’s mature works.)

But in the absence of any certainty regarding the play’s authorship, why should it be included in the Complete Readings of William Shakespeare?

Partly because we believe that staging the apocrypha gives a unique and exciting opportunity to see plays which are rarely or never performed. If an apocryphal play like Richard II: Thomas of Woodstock was, in fact, written by Shakespeare, then it’s an important part of the project’s goal to include it. But even if it is not, such plays are an important part of the American Shakespeare Repertory’s mission to provide the rich, Elizabethan context in which Shakespeare’s plays were originally staged.

Which is the other reason we believe it’s important to stage Richard II: Thomas of Woodstock. Amidst all the uncertainty, there is one thing we can be sure of: There was a play on the London stage dramatizing the events surrounding Thomas of Woodstock’s death. If it wasn’t Richard II: Thomas of Woodstock, then it was some other play covering the same ground.

Whether or not that play was by Shakespeare, it would have been fresh in the minds of those who saw the premiere of Richard II — a part of the cultural gestalt created by Elizabethan theater. It’s a context which has been largely, if not entirely, inaccessible for the past 400 years. But it’s a context which the Complete Readings of William Shakespeare is uniquely suited to restore.

Originally posted September 18th, 2010.

The Human Concordat was originally conceived and pitched to Shadis magazine as the first “AlterWorld”. My idea was to create a new “mini-setting” that would nestle into an existing setting and then develop that setting over the course of 12-18 issues of the magazine with more detailed articles and adventure scenarios. Additional AlterWorlds would have followed. The two ideas I remember being discussed were a city for the World of Darkness (which would have included material for all the different World of Darkness games) and an isolated planet in the Mechwarrior universe.

The idea was that the extended focus on a single campaign resource would create a unique audience for the magazine. What I found appealing about the AlterWorld concept was that it would allow me to explore radical ideas for settings that the original creators weren’t interested in: For example, when I first read Fading Suns I was fascinated by the idea of a gate connection opening up that would lead not just to one world, but to an entire lost civilization of worlds. And, thus, the Human Concordat was born.

Shadis folded in 1998, however, and the Human Concordat got shelved. About a year later I repackaged the pitch for Pyramid Magazine. They weren’t interested in the AlterWorld concept, but they expressed interest in the “Human Concordat” as a stand-alone article.The only problem was that it was too long for their budget: They asked me to cut it down to roughly half the size so that they could afford to pay me. I made a counter-offer: They would pay me for the article length they wanted and I’d give the rest of it to them for free.

In order to see the material realized the way I wanted it, I also personally commissioned the artwork for the various religious and political symbols. (The gorgeous jumpweb map by Keith Johnson I can take no credit for, however.)

Part 1 – The Fall
Part 2 – Government & Religion
Part 3 – Worlds of the Concordat
Part 4 – More Worlds of the Concordat
Part 5 – The Concordat as Campaign Setting

As a young author, I secretly held the hope that the article would prove to be such a huge success that Pyramid would come back and ask me to develop more material in the setting. Unsurprisingly, that never happened.

One thing that never got executed properly: The symbol for the Seven Pearls was supposed to be varied for each of the Pearls. This is what it ended up looking like:

But the original conception was that each planet in the Pearls would have a variation in which its corresponding circle-star would be the largest on the string. (So Lyonesse would have the first circle-star larger than the others, while Leicester would have had the second circle-star larger than the others.)

Reading through The Human Concordat today, I can also see that the setting comes across as significantly more utopian than I’d originally intended: The “culture of universal acceptance and emancipation” should have its dark side. (You might also note the number of terraforming engine problems found throughout the setting. The bit about terraforming technology being “the one true secret which remains, as yet, unmastered by Concordat scientists” was also unfulfilled foreshadowing.)

As a final point of miscellaneous interest, here’s my original rough draft of the Concordat jumpweb map:

Which you can compare to Keith Johnson’s superb work:

(click for larger version)

Tagline: Let us review the review policy.

Okay, this one needs some explanation. On January 25th, 2000, John Wick gave an interview at the Gaming Outpost. (Although now defunct, the Gaming Outpost was a major online RPG nexus at the time.) As part of that interview, John Wick issued “The Official John Wick Review Policy”. This notably included stuff like claiming that reviewers should never say they didn’t like something. That no one should ever read a review. That no one should ever write a review. And then a strong suggestion that nobody (including fans) should express an opinion about an RPG unless they had personally published an RPG.

There were also a couple pieces of advice that weren’t complete shit.

This “review policy” came out shortly after Wick’s game 7th Sea had been inundated with bad reviews. The “Official John Wick Review Policy” poured gasoline on the fire: Wick was trying to tell an entire community of people who were disappointed with his game that they literally weren’t allowed to have an opinion about it because they hadn’t put in the “blood, sweat, and tears that make up the creative process”. I decided it would be particularly clever if I couched my own commentary on the “thou shalt not write a review” review policy in the form of a review.

So this particular review was written very much in a historical moment. I’m uncertain that it has any real meaning 15 years later, but if I’m archiving all of my historical content here on the Alexandrian, then I guess I should archive all of it.

(This is a review of The Official John Wick Review Policy, which was included as part of a Gaming Outpost interview which can be located here. You might want to go there before you read this – or after. Then again, you might not.)

John Wick’s Review Policy sucks.

What else can I say? The very idea of Wick dictating the policies people will be using to review his own material is nauseating. He seems to think that his opinion has some sort of relevance to the rest of us. I just didn’t like it.

And you won’t like it either. I guarantee it.

Not that that matters, because if you’re reading this you’re a brain dead asshole. Didn’t you read Rules #5 and #6? What part of “never read reviews” didn’t you get? This is clearly being written by someone who has no idea of the blood, sweat, and tears that makes up the creative process (as if that somehow has some relevance to the merits of a product; as if the Cleveland Browns should have been in the Superbowl because they really, really wanted to be good and worked really, really hard). And I definitely have a personal agenda to condemn the product in question, considering that I am – by default – one of those evil reviewers. I violated Rule #7 (“never write a review”) right off the bat, so why are you paying any attention to me?

Of course — don’t blink now! — Wick has definitely written reviews before (some of which can be found in his columns right here on RPGNet) – so he’s a hypocrite. I can’t testify with absolute certainty that he has ever read a review – but I suspect so, which makes him a hypocrite twice over. And if he hasn’t, then he’s speaking from ignorance.

Which just makes him an idiot.

Which brings us to Rule #9: “Before you buy a book, read a few pages first.” A good point. Feel free to go check out the policy itself before continuing. I’ll wait.

Dum de dum. Ho de do. Dum dee-dee.

…

Ho, ho, ho!

…

You’re back? Great.

You may have realized that I’m not showing much restraint here. Initially I was worried about this, but then I realized that: (1) According to Wick there is no such thing as an objective review. (2) He was going to be “pissed off” about a negative “slam”/review no matter what it said. I’d feel sorry that I was causing him so much mental anguish, but if he’d stop putting together diatribes like this then it wouldn’t be necessary for others to tear them to pieces.

We’ll have to skip Rule #10 because this isn’t a roleplaying game we’re reviewing.

And we’ll have to skip Rule #11 because Wick is repeating himself.

Which brings us to Rule #12, in which Wick reviews Pendragon, Over the Edge, Ars Magica, Conspiracy X, Call of Cthulu, Champions, Twilight: 2000, Delta Green, the James Bond RPG, and Brave New World. See Rule #7 and draw some conclusions about Wick.

Then go back and read Rules #5 and #6, in which Wick bizarrely tells you that you shouldn’t even be reading this Official John Wick Review Policy.

Oh well, I was ignoring him anyway. On to Rule #13!

“Rule #13: If you’ve never gone through the grueling process of writing, designing, developing and publishing a roleplaying game, you don’t have the knowledge necessary to properly critique one.”

First off, if a bridge collapses the first time someone walks on it you don’t need to be an engineering major to figure out that there was something wrong with the bridge. Second, I find it truly bizarre that you need all that expertise to be qualified – in Wick’s opinions – to critique them (for example, why are only self-publishers allowed?). Finally, this whole thing leads to the oddity where it’s all right to critique a game, but you shouldn’t review it.

Rule #14 tells us that we have the right to express our opinions and the right to not express our opinions. Quite right. Rule #14.5 tells us that if we choose to “disregard these rights” (by both expressing and not expressing our opinion? by half expressing our opinion? what?) “anything you say can and will be used against you”.

Ah, poetic justice.

Rule #15 tells us that you need to defend your opinions – you need to justify them. Again, quite right. Pity Wick never seems to follow his own advice. Despite Rule #16: “All of the above rules apply to everyone. Including me.”

Style: 2
Substance: 1

Author: John Wick
Company/Publisher: Gaming Outpost
Cost: Free!
Page Count: n/a
ISBN: n/a

Originally Posted: 2000/01/28

Kaboom! Unsurprisingly, my caustic and ironic response to Wick’s diatribe provoked fierce responses. Wick himself notably failed to see the humor in a review of his review policy which systematically violated every single one of the absurd “rules” that he had proposed for reviews. We exchanged a number of heated comments back and forth across a variety of online forums.

The interesting thing is that, within a few weeks, John Wick and I had gotten over it: We had our argument and then we moved on. When I went to Gencon later that year, John was releasing his truly excellent Orkworld game. I shook his hand, we talked briefly, and he signed the book, “You review this and I’ll break your legs!” We laughed, chatted some more, and then I wandered off to read the book.

For a large number of people, though, John Wick and I were arch-enemies locked in an eternal feud. When my positive review of Orkworld appeared, I got several e-mails from people who were wondering if I’d “sold out” or if RPGNet had “forced” me to write a positive review. Some of it completely bizarre stuff; most of it just confusion.

It should be noted that Wick’s handling of the situation stood in marked contrast to the attitude of Sovereign Press at the same convention. (Which I describe at the end of my review of Sovereign Stone.)

For an explanation of where these reviews came from and why you can no longer find them at RPGNet, click here.