RPG Art Commissions Open!

I am hungry and don’t know how I’ll pay rent this month or next, so who wants character/monster portraits in black and white ink?

Here's a small portfolio showing a range of stuff I've done in a few different styles (see also my IG here). Following that are the details you'll need to know for working with me.

Tricks & Treats: Harvestland Horror

The final day of Halloween is less than a week away, so have another free Halloween-themed one shot adventure you can run before the end of the month. It took me a bit longer than expected, but this is the promised follow-up to my last Halloween adventure.

This scenario is built for use with a Lasers & Feelings hack called Tricks & Treats, created by Octava Oculta (Reddit username u/shardsofcrystal). It's an ultra-lite system fit for all ages or experience levels, and is great as a nostalgic little novelty adventure. Just follow that link, make a copy of the folder and its contents, and use the materials within to play a fun session of spooky adventure.

Here's the pitch: play as middle schoolers on a field trip to a pumpkin patch on the morning of Halloween, encounter a big horrifying monster that the grown-ups are helpless to stop, use your noggin to save the day. This is especially good if used as a sequel to the last adventure because all the students have aged a year and you can build on previous events and relationships. That said, most of my own players created new characters for this year, so do what you feel like.

Not sure when part 3 will come out, but one of my players suggested we also do some spooky adventures during tax season, the other Halloween. If anyone runs either of these adventures, I'd love to hear about it and how it goes.

-Dwiz

I Don't Think I'm Going to Allow Elves to be Playable Anymore

This is going to be a fraught post and I'm not sure I'll articulate everything I mean to clearly. That's not meant as a shield, it's just the truth. I'll try my best though. I know I have a very patient audience.

I mean, for one thing, we can start optimistically. There's lots of great fantasy fiction that's humans-only! A Song of Ice and Fire, Conan the Barbarian and most other Sword & Sorcery, Arthurian Mythology, most other real-world mythologies, most fairy tales and fairy tale-inspired fiction (e.g. Alice in Wonderland and Peter Pan and whatnot), most gothic fantasy/horror (e.g. Dracula), most pirate-y fiction, and so on. And others are human-centric to the point that things which may be called "dwarves" or "goblins" or whatever else are either clearly not societies or they're so peripheral to the action that "playing as one" wouldn't make much sense at all. Hellboy, Dark Souls, Darkest Dungeon, et cetera.

So if anything, it's really the default option, right? Elves and dwarves are the exception. Everyone should be asked to justify why they are including non-human player options, rather than me being asked why I'm not.

But here I am. I need to explain myself and it's going to be messy. If you're getting used to hearing arguments about orcs and dark elves a lot lately, this post is about that. I've been sitting on this post for a while now. This is going to take me a while to explain my line of thinking but please bear with me. There is a reason for each section in this post. 

Gritty Realism: Adventuring in Weeks, Not Days

Because apparently this is a 5E blog now, I'm going to talk about the Gritty Realism variant rule suggested in the DMG on page 267. But wait! Don't go! You know me better than that. Of course I'll find a way to make it relevant to you and your rules-lite artpunk post apocalyptic furry heartbreaker as well, since I know you don't play D&D 5E.

So there's a type of adventure scenario I like to call a "Die Hard plot." It's not a good name, but it's what I always think of. In the movie Die Hard, the whole ordeal takes place within a single evening. The movie almost happens in real time! It's a really jam-packed day. See also:

1. The Warriors
2. The Avengers (well, like 90% of it)
3. Night of the Living Dead
4. Clue
5. Dredd
6. The Goonies
7. Escape From New York
8. 24 (the TV show)

...and plenty of others. Now of course, lots of movies take place entirely within 1 day. But these ones here are specifically all movies that are a great model for D&D ADVENTURE! Sure, My Dinner With Andre takes place in one day, but that's because it's just a dinner conversation. These movies are set within a single day in spite of how much crazy shit happens within them.

Every movie on that list is great (and 24 is okay I guess), and you should steal from them occasionally. But the main appeal of Gritty Realism is that it affirms a simple truth: you can't run an entire campaign of just Die Hard plots. Or rather, I think you probably shouldn't.

I'd like to talk about this at length and help us all to appreciate this better.

It's All Levers

Your game is just a bunch of levers. Everything in it, every single thing, is just a lever that your players pull. Your prep work going into a session is a list of levers you know are in your world and what you know will happen if they're pulled. During the session, you'll see your players pull some of those levers and the answers in your prep notes will be useful. You'll also watch them discover levers you didn't know are in your world. If they pull those levers, then the effect may be obvious. But more likely, it's a conveniently delayed effect. Delayed until the next session begins, when you've had some time to think about what happens when that lever is pulled.

You go into every session with a list of known levers and answers. Your Players discover more, you write them down and stall until the session is over, and then go into the next session with answers for those levers and some other new ones.

The game is just levers.

-Dwiz

Tricks & Treats: Jack-o'-Lantern Nightmare

Happy first day of Halloween! Have a free Halloween-themed one shot adventure you can run this month, built for use with a Lasers & Feelings hack called Tricks & Treats, created by Octava Oculta (Reddit username u/shardsofcrystal). It's an ultra-lite system fit for all ages or experience levels, and I made a kick-ass adventure for it last year during lockdown. Just follow that link, make a copy of the folder and its contents, and use the materials within to play a fun session of spooky adventure.

Here's the pitch: play as middle schoolers going trick or treating in your typical North American suburban neighborhood, encounter a big horrifying monster that the grown-ups are helpless to stop, use your noggin to save the day. Stranger Things is a really useful comparison here, because it's the perfect balance of family-friendly adventure and supernatural horror. Basically, I aimed for "more tense and easy to take seriously than The Goonies" but "less violent and mature than Stephen King's It." When the monster is present, it should feel legitimately threatening, but at the same time, you won't see it tear a 9 year old in two pieces and spray blood everywhere.

At least, that's how I run it. It's your table, do whatever you like. Maybe you and your group would prefer a game where the monsters violently massacre the neighborhood, but you also decide that you don't want your players to get called a homophobic slur by a shitty 12 year old. Use your grown up judgment on what's best for your group and what you want out of the game.

A note on audience: hypothetically, you could run this adventure for a group of kids about the same age as the protagonists. Pretty easily, in fact, since it's such a simple rule system and the scenario is easy to grasp. However, I personally feel like the ideal audience is actually a group of adults, since much of the appeal of the adventure is 1) nostalgia, and 2) being able to laugh at the cringiness of middle schoolers.

In a couple weeks I'll be releasing my sequel to this adventure, so if you enjoy this one then stay tuned so you can run another one before the end of the month.

-Dwiz

Model United Nations: the Most Popular FKR Game

We don't actually have the numbers of how popular Model UN (MUN) is but we can reasonably guess there's as many as 180,000 people who participate in it just in the United States alone. It's played all around the world by students ranging from middle school up through university and has been around for many decades. And even if it turns out I'm totally wrong and the number of people playing Jim Parkin's ultra-lite Star Wars game actually outnumbers the people playing Model UN ten to one, the point is that Model UN has a Parks & Rec episode.

And yet I bet you don't know much about it. I bet you didn't know that it's an FKR game. And yes, it really is. Not in like a "you know, if you really think about it, it kinda fits the definition!" way or something cheeky like that. It's very straightforwardly an FKR game, and if more was known about its history (it's a bit murky tbh) then I strongly suspect we could probably trace its lineage back to the original Prussian kriegspiel games.

I have not written much about my experience with FKR games before. I've mentioned them here or there, and at least once have pissed off some of its fans. But I have actually spent many years using the FKR philosophy of play! Just not in the form I think that most people would imagine.

I've written about Model UN before so if you've read that post, you can skip this. But I decided to write all of this again for 2 reasons: 1) I think it needs another pass and I've written it better this time, and 2) I think it deserves a post of its own, independent of the context in which I wrote about it in that series. And I promise that if, after this article, it is clear that no one in the RPG community gives a shit about this then I'll shut up about it forever.

But if Model United Nations is one of those things you've always been vaguely aware of from pop culture or the club fair at your high school but you never really gave it much thought, then let me tell you all about it and how cool it is.

A rough outline of this post (with each of these containing some sub-sections):

1. What is Model United Nations?
2. The "mechanics" of how it works
3. What to take away from this for TTRPG stuff
4. Some fun stories where I gush indulgently

Iterative Design

If you work in any form of engineering then this is probably a familiar idea. I just want to talk about how valuable I find it to be when it comes to RPG design. I've always really liked that the standard in RPGs is to have new "editions", rather than straight-up sequels. And because it is, to greatly generalize, a fairly scrappy and accessible hobby, we get to do lots of communal collaboration. We build on each others' work. We actively encourage the theft of good ideas (within the bounds of intellectual property rights). Most RPGs list their "Rule 0" as being something along the lines of "the GM can and should ignore or change any part of the game they want to if they judge it best for their group." It's like you have a game designer at every table.

The problem is that a lot of folks are pretty amateur as game designers. The single biggest failing, I think, comes from this very gap: not enough would-be designers are engaging with iterative design.

You look at what's come before and you use it as a basis for what you'll create anew. You examine the previous version to understand its design, paying attention to the context which created it and asking yourself whether or not those same factors remain relevant. And at the very least, the common corollary to that rule 0 is this: "a good GM will first make an effort to understand the original rule's purpose before deciding to change it." All-too-often ignored wisdom.

I especially find this to be common in two cases: 1) people complaining about design they don't understand, and 2) people making poorly thought-out houserules. Let's talk about some examples.

The New School, the Old School, and 5th Edition D&D

This was easily the funniest picture I found for "Edition Wars"

People have short memories.

Actually, that's only part of it. People also need tribalism, and tribalism needs enemies. Also, lots of people are new to the hobby, so maybe they genuinely don't know.

I frequent a lot of OSR spaces online, and while it's far from a consensus, one of the most pervasive sentiments among this community is that 5E D&D is the devil. It's representative of all things we old schoolers hate in gaming, and is the ultimate metric to contrast one's own game against if you want to appeal to this crowd. At this point, "5E" has literally become shorthand for "new school" in, seemingly, most old schoolers' vocabularies.

Which is funny, because I was there when 5E came out in 2014, and at the time it was being called "old school." It was a "return to form" for the franchise. "The legacy edition." A victory for the OSR, who had finally conquered the mainstream. It pulled back many of the trends of 3rd and 4th edition D&D and abandoned the way of the new school in favor of trends that had been started by the grognards years before. It openly embraced many of the specific Zen moments from Matt Finch's A Quick Primer for Old School Gaming. Zak S, who got credited in the book as a consultant, went parading around GenCon with his entourage wearing shirts saying "Zak S saved D&D."

Don't believe me? Behold, some archaeology:

The Only Two Enemies You'll Ever Need

I have two types of enemies that I fall back on if I don't have something interesting or appropriate prepared:

A. Powerful but dumb

B. Weak but cunning

Between those two types, you can create nearly every type of OSR creature challenge you'll ever need. The key is that both types tell you about how the enemy thinks, which is the main thing the PCs must interact with. When you look at a big fancy statblock for some monster from a new school "Combat as Sport" game, you don't have any idea how it thinks. Well, pick one of these two.

Type A Enemy: Powerful But Dumb

I had a party of six different level 1 knaves all on a quest to go hunt down a troll. They were terrified, and the further they got into this quest, the more reasons they discovered to be terrified. The troll has a ton of HP and decent AC, does a lot of damage with a basic attack, but most importantly, is really fucking strong. A player tried chasing him down alone and got a tree thrown at them, shattering their arm. When the party tracked the troll down to its lair, they watched it being awoken by a damn fool NPC knave, whose spine was then compressed like an accordion.

But the players killed the troll with not a single tree thrown at them this time. Why's that? Because they talked to it, and they lied, and they made it angry, and they kept distracting it, and so on. They did everything they could to play on how dumb it was. My rule of thumb for a Type A enemy is this: any type of trickery the players attempt against it will succeed by default.

Type B Enemy: Weak But Cunning

The most frequent candidate I use for this type are NPC knaves, because I like to show the players a dark reflection of themselves. Other common choices are any kind of monstrous humanoid, such as frog folk or hobgoblins. The key is that each individual member is either roughly as powerful as a PC, or less.

In this example, I had three different level 1 knaves enter a dungeon that had been set up as the HQ of a band of brigands. Long story short, they had worked their way into the center of the dungeon and had either killed or scared off each NPC they'd come across, funneling all of them towards one corner of the dungeon where their leader tried to coordinate a counterattack. There ended up being a standoff in two dungeon chambers with a closed door in between them. The players were desperately holding the door shut on their side, as were the NPCs. Neither realized that the other was not trying to barge in. But that gave both sides the chance to prepare a surprise attack.

The players lost. They were simply not as clever as the NPCs. When the door swung open, they saw a brigand training a musket towards the ground, and a gunpowder horn rolled to their feet. The gun shot and hit the horn while the door was simultaneously slammed shut. One of the PCs died in the explosion.

My rule of thumb for a Type B enemy is this: they play like an experienced, skilled player would in their position. Retreat, ambush, strength in numbers, leverage resources, and NEVER FIND THEMSELVES IN A FAIR FIGHT.

-Dwiz

Happy Birthday Knight at the Opera: A Blog Retrospective

I started this blog two years ago. At that point, many people were already saying that the OSR / DIY D&D blogosphere was dying out, but they were probably being unnecessarily bleak. Still though, I was throwing my hat into a competitive ring with a small, small audience. Attention is hard to grab, so if you aren't a Grognardia or a Jeff Rients or maybe a Patrick Stuart then your chances of catching people's eye is pretty small.

Considering all that, this blog has done much better than I ever anticipated. It's not huge or anything but waking up to see your post has gotten 1000+ views overnight is pretty damn cool. That's 1000+ people who chose to read my nonsense in their cubicle on a Monday morning over a cup of coffee instead of doing something productive. That feels pretty good.

So for this blog's 2 year anniversary (as well as a celebration of my favorite holiday, Labor Day), I wanted to reflect and share wisdom. This post will have 3 parts: 1) How to Start a Blog, 2) Things I've Learned About Successful Blogging, and 3) a Celebration of This Blog's Greatest Posts and Products.

Associates vs Parties

Art Credit: Dan Scott
Side story: so I was just gunna use some generic art
of "an adventuring party" here but then I thought to
share this piece, which was the first D&D art I ever
remembering firing up my imagination. I stared at
this picture for hours when I was introduced to 4E D&D
back in 6th grade. I especially love that wizard-y dude
in the front.

I have just discovered an unconscious assumption I've been making in my design work. I discovered it while reading Matt Colville's Strongholds & Followers and then his follow-up book, Kingdoms & Warfare. It's a major philosophical difference between those two works than I'm having trouble mentally reconciling, but I also think it's one of the many general differences between the Old School and the New School. And it's a fracture I think I've already unintentionally baked into Brave.

Are the PCs a true party or are they just adventurers who associate?

Obviously that depends on the players, but game structures can have one of those two assumptions built in and won't really work that well if you disagree with the assumption.

The difference I'm imagining is, I think, easiest to describe by painting a picture of two different campaigns.

1. A true party is united by a purpose. They either all have the same patron or they operate a single enterprise together. A party that's also a thieves' guild or a pirate crew or an order of knights or something would be an example of this version. A victory for one is a victory for all, and they are frequently attacked, aided, and rewarded as a group. They probably share a single headquarters. Some games go so far as to create a "party sheet" that's like a character sheet but for elements that only exist as a feature of your unity, and aren't an element of any one single member alone (e.g. reputation or turf).
2. Adventurers who merely associate may still go out on adventures every week, delving into dungeons together and saving each other's bacon. But they each have separate goals and will break off from everyone else if they have good cause to. The wizard owns his own tower from which he performs magical research. The rogue owns her own tavern where she smuggles contraband. The cleric has built a temple in order to better serve their personal deity and the fighter has raised an army to conquer a fortress in order to better protect the peasantry. Especially if you're playing an open table game, then you may not even have a consistent party makeup from session to session. There is no "party," there's just instances of adventurers in a shared world choosing to work together temporarily, and the stories we play out are following different combinations of adventurers each time. You'll also almost certainly not all be the same level, and there may even arise competition between you! An old party member may grow powerful and corrupt and become a villain for everyone else!

In the rest of this post, I'll spell out more thoughts arising from this, how I see this affecting my own RPG, and my thoughts on those Matt Colville books as they relate to this concept (for anyone interested in his work since I'm sure I got some 5E players reading my blog).

Splitting the Party Isn't That Bad

I guess it partially depends on how patient and cool your players are, but I am here to argue my case that it's just not that bad in general.

The party usually operates as one unit. When they come to a major decision point, they get everyone's perspective and maybe take a vote. When they come to a complicated situation, each person contributes what they can to the course of action. And unlike in film or TV, the "camera" is pretty much always pointed at the party the entire time, with no occasional dramatic cuts to the villain's lair to show him talking to his cronies or whatever. That's the idea, anyway.

This does not always work out. Sometimes just because of circumstances outside of anyone's control, but oftentimes it's because of a deliberate decision. The party will eventually find themselves in a situation where they ask, "should we send the rogue to scout up ahead alone?" Even most experienced players will be uncomfortable taking the risk, and still always try to return to the status quo as soon as possible. "Don't split the party" is one of the most oft-repeated mantras in tabletop gaming.

But I have done it a fuck ton and it's been fine.

Official German Translation of Brave

Didn't see that one coming, didja? Me neither.

So recently a fellow by the name of Calvin Brandt reached out to me and said that he's translated my RPG, Brave, into German. And I said, "So this is the coolest thing anyone's ever done for me."

So here's the link to the PDF version, and here's a link to the Word document for anyone who'd like to edit it directly. Just as with the original, the formatting of the doc version is a bit messed up if you don't have the right fonts. So go ahead and make sure you've downloaded the free fonts Garamond, Hamlet Tertia 18, and Black Castle MF.

Although of course, the formatting in general is quite a bit different, just as a consequence of being written in a different language. Mr. Brandt is working on the Enchiridion right now and we'll be keeping the translation updated as the game gets updated.

I'd like to publicly thank him for this as fully and deeply as I can. I cannot, myself, read German (I took a year of it in high school but I was a lot more focused on Spanish and Latin), but I encourage folks to spread this in your German-speaking communities and see that this triumphantly dethrones The Dark Eye once and for all.

-Dwiz

Princess Mononoke and "DM-Prepared Plots" in Old School Games

Alternatively titled, "How to Have Your Cake and Eat it Too."

There is a commonly recognized dichotomy of gamers who like linear, "scene-based" games where the DM is a storyteller and has an epic and enchanting plot prepared in advance they're trying to deliver, versus games where the DM is a referee who impartially simulates an active world and hands the reigns off to the players to do whatever the hell they want. In the latter game, to the extent that there's a "story" or "plot" at all, it's usually one that emerges naturally and unplanned out of the consequences of the PCs' actions and how the world responds to them, but the point is that "player agency" is maintained above all else. In the former game, there's usually a much-needed Session 0 conversation where the DM convinces their players to try to "play ball" as often as possible so as not to "ruin the game," and typically as long as you're playing with reasonable people then you'll have a great time.

It's not actually as though all gamers fall strictly into one of these two types, but boy do these two types fight a lot and get very defensive.

There are essentially three main ways to think of this situation:

• Broke: DMs are/aren't storytellers and that's the only correct way to play
• (most sensible people recognize this is a childish take)
• Woke: There are many different playstyles that are all equally valid, and you should try to just figure out the one you prefer and then go find players who agree
• (this is what most sensible people settle on)
• Bespoke: A good DM can achieve a game that both keeps player agency perfectly intact and features a good amount of "emergent story" from the simulated world and has a DM-prepared plot that unfolds and wows the players with their storytelling prowess.

I am here to explain how. 

Reeeeeeeeeeeeeeeeeeeeeeeeeeee

I Want to Talk About The Green Knight

I don't do this very often but this post isn't about RPGs or gaming. It's just some thoughts on fantasy fiction in general, although it does occasionally reference RPGs because that's who I am and I know my audience.

I'll warn you when I'm about to get into spoilers. First I need to set the scene.

This post is a series of short essays. First, what I love about medieval European culture. Second, what I love about Arthurian mythology. Third, what I love about Sir Gawain and the Green Knight. Lastly, I'll talk about the movie. Warning: about half the sentences in this post begin with, "I like" or "I love," but I hope I'm still able to drive at something deeper than you might expect. 

Brave Design Notes 6: Settlements

Go to the master post

Brave is a hack of Ben Milton's Knave, an old-school adventure game toolkit without classes and a lot more emphasis on equipment. The earliest changes I made were miscellaneous tweaks and houserules I added as I would run Knave, but at this point I've bolted on several advanced play procedures. While Knave is optimized for a DIY "rulings over rules" style of play, I still felt it was valuable to write down many of those rulings that I've made over the years and codify them. One of the best parts of the original Knave were the designer's notes, but I've taken them out because I needed to make room for new stuff and I assume that anyone playing my game would already be familiar with the original version anyway. Instead, you get my blog.

These notes are written for version 1.9, which you can find on the sidebar of this blog or by clicking here. These rules also make use of a resource called a "settlement info sheet," which you can find here, along with the player copy template here and the version adapted for villages here.

Brave Design Notes 5: Dungeons

Go to the master post

Art credit: Tony DiTerlizzi

Brave is a hack of Ben Milton's Knave, an old-school adventure game toolkit without classes and a lot more emphasis on equipment. The earliest changes I made were miscellaneous tweaks and houserules I added as I would run Knave, but at this point I've bolted on several advanced play procedures. While Knave is optimized for a DIY "rulings over rules" style of play, I still felt it was valuable to write down many of those rulings that I've made over the years and codify them. One of the best parts of the original Knave were the designer's notes, but I've taken them out because I needed to make room for new stuff and I assume that anyone playing my game would already be familiar with the original version anyway. Instead, you get my blog.

These notes are written for version 1.9, which you can find on the sidebar of this blog or by clicking here. These rules also make use of a resource called a "dungeon control panel," which you can find here.

Brave Design Notes 4: Cohorts

Go to the master post

Brave is a hack of Ben Milton's Knave, an old-school adventure game toolkit without classes and a lot more emphasis on equipment. The earliest changes I made were miscellaneous tweaks and houserules I added as I would run Knave, but at this point I've bolted on several advanced play procedures. While Knave is optimized for a DIY "rulings over rules" style of play, I still felt it was valuable to write down many of those rulings that I've made over the years and codify them. One of the best parts of the original Knave were the designer's notes, but I've taken them out because I needed to make room for new stuff and I assume that anyone playing my game would already be familiar with the original version anyway. Instead, you get my blog.

These notes are written for version 1.9, which you can find on the sidebar of this blog or by clicking here.

Brave Design Notes 3: Alignment and Combat

Go to the master post

Art credit: William O'Connor

Brave is a hack of Ben Milton's Knave, an old-school adventure game toolkit without classes and a lot more emphasis on equipment. The earliest changes I made were miscellaneous tweaks and houserules I added as I would run Knave, but at this point I've bolted on several advanced play procedures. While Knave is optimized for a DIY "rulings over rules" style of play, I still felt it was valuable to write down many of those rulings that I've made over the years and codify them. One of the best parts of the original Knave were the designer's notes, but I've taken them out because I needed to make room for new stuff and I assume that anyone playing my game would already be familiar with the original version anyway. Instead, you get my blog.

These notes are written for version 1.9, which you can find on the sidebar of this blog or by clicking here.