I am all in favour of an easy life. Although I have never played 5e it [D&D] hasn’t changed that much in past 40+ years that I cannot look at a stat block and think I know what that does.
One of the things that I don’t like having to make up on the fly when gaming is NPCs. There is always the danger that the players seek out an NPC early in a game session and before you know it you have been playing them for 3-4hrs and you have no stats or details.
Books of NPCs are always useful and the more detail the better. One of the most popular Rolemaster books was Heroes and Rogues that detailed 24 NPCs at 7 different levels complete with backstories.
Rolemaster NPCs are not much use to most people. 5e NPCs are far more accessible because, in my circles at least, D&D is a bit of a common background. If you are playing any regular fantasy rpg it will not take a great deal of effort to convert from 5e to your favourite rules. For many people of course 5e is their favourite rules. I have heard that a lot of people play it.
This week I found The Friend Folio by Sean Van Damme and Elizabeth Kost. The book details fully worked ‘sidekick’ NPCs. They are pretty much drop in and ready to go. The book contains 20 sidekicks and is very well presented (see below).
Now, I don’t know what a Shadar-kai Expert is, but I don’t need to know. I can pick that bard up and run with it/him without having to fall back on improvising something and then having to pick my notes apart after the session to build the character.
I have been gaming with the same group for 36 years now. This means that a) they know most of the stereotypes I come up with when I have to improvise and b) they know the Heroes and Rogues NPCs because they have either met them or used them themselves over the past three decades.
This set gives me a whole new set of personalities to play with.
Handling chivalry in RPGs is hard. Genre fiction loves chivalry and honor almost as much as it loves jaded pessimism – and it often shoves the two philosophies together in ways that seem to clash. The classic example is the paladin and the rogue. How’s a GM supposed to have both in the same party without one of them (usually the paladin) looking like a moron? A real-life incident from 1351 may help shed some light on how to walk this tightrope.
The Hundred Years’ War between England and France (1337-1453) was a famously awful mess. Millions died, countless towns were burned (sometimes multiple times), and the whole affair settled remarkably little. Yet the leadership of both sides were ostensibly bound by the laws of chivalry, which theoretically ought to have limited the violence. It’s a great example of how honorable combat usually doesn’t hold up in the real world. Yet amid the blood and the grime, there was a bright spot: the Combat of the Thirty, an example of chivalry held up for centuries to come.
In 1351, an English castellan (lord of a castle) in Brittany was riding past a fortress occupied by Breton forces fighting for France. When he saw that no one inside the castle was going to come out and fight, the Englishman called up to the Bretons on the ramparts to ask if there was anyone inside who might want to joust with him “for the love of their ladies”. The joust he was proposing was no tournament game, but a deadly bout with steel-tipped lances!
The Bretons politely declined, but offered
a counterproposal. “We will choose twenty or thirty of our
companions in the garrison and we will go to an open field, and there we will
fight as long as we can endure it; and let God give the victory to the better
of us.” The two sides agreed on a date and time, then parted.
The day of the combat, both sides arrived with thirty men-at-arms. The fighters didn’t pair off or anything: it was just a giant scrum of two teams of thirty men trying to kill each other. They fought mounted and afoot, with swords, daggers, spears, and axes. The fighting lasted for hours. Over a dozen people died. The French side ultimately won, but literally all the combatants who survived were badly wounded.
The outcome had no impact on the broader
course of the war. Indeed, it wasn’t intended to. This was sixty guys getting
together to beat the stuffing out of each other for no other reason than the
joy of combat and the glory they would earn for living up to a chivalric ideal.
And glory they did earn! In the context of the era, what these sixty combatants did was the pinnacle of chivalric achievement, made grander still by the backdrop of an incredibly un-chivalric war. More than twenty years later, a French historian recorded that one of the combatants still held a place of unique honor at the court of King Charles V specifically because of the knight’s participation in the Combat of the Thirty. Ironically, though King Charles may have valued chivalry highly, his successes in the Hundred Years’ War were arguably due to his unchivalrous pragmatism.
The central takeaway from the Combat of the
Thirty is this: your campaign doesn’t have to be tonally consistent to be
believable. Even in the midst of a hideously unchivalrous period in
Western history, chivalrous acts still occurred. At your table, you can have
your Jedi behave honorably and your bounty hunter be ruthlessly pragmatic and
give both a decent shot at success.
The most fun campaigns support a diversity
of PC worldviews. If you’re playing Song of Ice and Fire Roleplay, you can have
an idealistic Brienne-type PC and a nihilistic Sandor Clegane-type PC in the
same party without ever determining which one of them is ‘right’ about how the
world works. Indeed, it’s more fun if you don’t. A campaign with a single
underlying philosophy strikes only a single note. A campaign that strikes many
notes doesn’t get old as quickly – and it has a little more tension too.
The Combat of the Thirty shows us that a
campaign with only a single worldview isn’t realistic. And experience shows us
it’s less fun.
For more RPG content grounded in real-world history and folklore, head over to the Molten Sulfur Blog, where Tristan publishes adventure hooks, adventure sites, and NPCs every Tuesday.
All quotes are from the Chroniques of the 14th-century historian Jean Froissart.
You all know the drill by now. I drop off the face of the Earth for a year, and come August when the stars are right, I awaken from my slumber and crawl back to the blog to share my stories and ideas form RPG a Day. Now it is #RPGaDay2019, and I’ve been doing this since 2015. Here is the first post from #RPGaDay2015.
Back then I posted most days, but for the last three years, I’ve been doing video entries for RPG a Day. In recent years I began to do two posts for each day, one in Spanish for the Desde la FosaYouTube channel, part of an RPG project here in Puerto Rico with a couple of friends, and the English videos I would post in my personal YouTube channel. I’ve always collected them here in the blog, and I plan to do it again this year.
For #RPGaDay2019, the creator Autocratik changed things around, and instead of phrases or questions each day. Instead, we have one-word prompts that give participants leeway on how they interpret the concept and their response. It’s been great and reading the posts and watching videos form participants I can tell the format has been a success.
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.