Brave 1.9: Tales of Sword and Sorcery

Click here to view version 1.9 of my RPG Brave. Here is the accompanying character sheet (it actually has 2 sheets on it since they're small), here is the dungeon control panel, here is the settlement sheet, here is the player version, and here is the village sheet. The total document is 19 pages including the cover art, which I recommend you print out (put the intro+table of contents on the inside front cover, facing the page that says "The Basics" as the header). This game uses the free fonts Garamond, Hamlet Tertia 18, and Black Castle MF. The cover illustration was done by me.

If you'd like the Word document to edit directly, you can find that here. You'll want to download those free fonts or else the formatting will be completely annihilated.

I have periodically updated the link on the side of this blog whenever several changes/additions accumulate, but I'm making a whole post about it this time because 1) this is the biggest single update to the game so far, and 2) it is (hopefully) the second-to-last update before the final version of the first core rulebook.

Why am I not waiting to post until the final update? Why isn't the title of this post "Brave 2.0: Electric Boogaloo"? At the end of this post, you'll see what content I haven't finished yet and I think you'll understand why that's going to take me a good amount of time. So no, my game isn't finished yet to my satisfaction, but it's finished enough to be a full game (more full than most old-school RPGs, even) and I just wanted to finally put it out there.

The rules probably speak for themselves just fine, but if you're interested in designer's notes then strap in. This whole week I'll be posting articles of design notes on each topic in the game, each pretty in-depth on my thinking and the intent behind each rule. Here's a list of what those posts will be covering, updated with links as they come out.

1. Various Rules (mostly stuff you find in the "Rules for Adventure" pages)
2. Items and Shopping
3. Alignment + Combat (they're both short)
4. Cohorts (sort of the "mass combat" rules)
5. Dungeons
6. Settlements

The rest of this post will explain the miscellaneous minor tweaks I made to Knave and then a list of the topics that are missing from this draft of the game (but are coming soon!).

The Wizard and the Grimoire

TL;DR: This post is about modifying the magic system in Knave (specifically how you acquire spells and what a "school" might mean under its rules) and it's about creating a Wizard class for my RPG Brave, which will probably not make much sense if you don't know anything about my game. But you should! So read about that here!

Introduction

In every edition of D&D, you can gain the ability to cast spells of powerful magic. Nowadays, most classes are spellcasters. Back in ye olden times, there was "the Magic-User" class. They have always carried three assumptions:

1. You acquire the ability to cast spells by enrolling in a spellcasting class.
2. You acquire more spells (both spells known and spells you can cast per day) automatically from leveling up.
3. You get access to better and better spells as you level.

Duh, right?

But the system I'm using does not agree with those three basic assumptions. There's about a billion and a half ways to do magic systems in fantasy fiction gaming. One of my favorites in the system found in Ben Milton's Knave, which is one of many reasons it forms the basis of my own game. And out of all stuff I'm changing, this is one of the few things I want kept the same. I'll summarize:

1. There are no classes. Rather, spells come in the form of books. One spell per book, and each book can be cast once per day. Thus, the spells you "know" are just the spells you own, and the number you can cast per day is the number of books you have on you.
2. Like all other items and magic artifacts and treasure, you acquire them by adventuring for them. They have to be put into the world itself by the referee and then fought for by the PCs. There is no automated system for gaining spells.
3. There are no spell levels. They're all of "equal" power. Now, many spells will have built-in numerical variables that are keyed to the level of the person casting them, so that they can scale in power. For example, Sleep targets a number of creatures equal to your level when you cast it. But many other spells don't scale at all. Read Mind lets you hear the surface thoughts of all nearby creatures and that's it.

So I am tasked with answering the following design prompt:

How do you mechanically create options for "improving" at spellcasting or somehow allow for a PC to "invest" in the magic system without breaking the current assumptions in place?

Let's discuss.

Unity vs Division

I've been sitting on this idea for a couple years now but I've only ever had an abstract conception of it. Now I have some concrete systems to apply it to. Sorta. This will build off of my previous post as well as various things I've talked about here and there throughout the blog.

It starts with the idea of "campaign qualities." See, most people have an idea of what handful of qualities they'd like to see characterize their campaign as a whole. "I want to play a game that makes me feel like a Greek demigod." "I want to play a game with serious acting and drama and consequences." "I want to play a low-magic game that's heavy on survival." That sort of thing. Some games are built entirely around achieving one playstyle. Other games are a bit more flexible, and can be played in different ways. Most of the time, people recommend you achieve your intended feel by way of smart Level Design, so that the rules don't need to be changed from what people are used to. "You play the horror genre in an RPG by making scary scenarios!" But sometimes all it takes is a tweak here or there to the rules and systems of Game Design to have major consequences. A very popular houserule for 5E D&D is the "gritty realism" variant described in the DMG (along with some tweaks people have suggested) in order to achieve a more slow-burn, resource-management focused game than the vanilla version. And apparently it works great!

One dichotomy I think has a great deal of potency is a concept I call "Unity or Division." Each of these has a broad definition that can affect a wide range of factors in gameplay, from economics to exploration to politics and more. They can be thought of as a template that you apply to an entire country, modifying the details of many rule systems to give it a distinct identity of gameplay. 

Let's jump in.

People, Power, and Land

"The Procession to Cavalry" by Pieter Bruegel the Elder

I've been getting some different ideas about how I might want to procedurally design open-world sandbox campaigns. Most people will just make a big hex map of varying terrains and then make a random encounter table for each terrain type, and that seems all well and good to me. But while I like monsters and wildlife and whatnot, I'm also deeply interested in people. Especially the relationship between people, power, and land. I dunno, I just like politics and political D&D. So to me, the most interesting things you can encounter while traveling between settlements would be stuff like garrison patrols of a paranoid leader, folks making a pilgrimage, wealthy merchants in a jam, that sort of thing.

Back when I used to watch Game of Thrones (when it was still pretty good), a huge chunk of the "non political" parts were plots about characters traveling over land, often through the wilderness. And yet, those plots almost always still involved the characters running into people and factions. Tyrion runs into Catelyn Stark and her retinue, then they run into wildlings or something, then the knights of the Vale, then he leaves and him and Bronn run into some hill folk, etc. Jaime and Brienne traveled in the wilderness and met bands of brigands and mercenaries, employed by lords with agendas. Arya traveled in the wilderness and met the Brotherhood Without Banners, the Hound, Lannister soldiers, some peasantry, a knight errant on a quest (Brienne), etc.

So I would still of course have monster encounters, but I've been thinking more and more about the logic to determine what sorts of people you'd meet and where. Here's what I've got so far:

A Thorough Look at Urban Gameplay in D&D

The Free City of Greyhawk
Artist credit: Valerie Valusek

See, the title is like a Noah Caldwell-Gervais video. Get it? Because I'm about to spend a lot of words being pretentious but hopefully insightful.

I've spent a lot of time in the last year thinking about adventuring in cities. Part of it's because I really miss going outside and having an active life in an urban area. Part of it's because my D&D group spent the better part of 2020 in a campaign arc involving our party trapped in a hostile city, Escape From New York-style. And even when we broke from that for a few one-offs here and there, many of those involved adventure in the city. Or at least, like, in a town or neighborhood. And I've noticed what's worked and what hasn't and I've done so much darn reading and I want to get this right once and for all. I've run games in this setting with different approaches and sometimes it's good and sometimes it's not. And I've tried to give feedback to my own DMs about how they might want to improve those sessions, and sometimes they take that advice and sometimes they don't. But the worst thing of all is that each of the really solid sessions my group has spent playing in an urban setting have largely relied on the strength of completely unrelated elements, like a fun combat encounter, social encounter, puzzle, or whatever. They always just skirted around the problems of answering those vital questions about city adventures, so even if the session was successful it was at least partially just luck.

Here's a brief table of contents for this post:

1. Bibliography for research I did, and further reading you may enjoy
2. An analysis of how most people seem to run urban settings
3. An explanation of my line of thinking that led to my version
4. My Brave settlement guidelines and examples, with a bit of elaboration on certain parts
5. Why I care so much about this

If you just want the goodies, you can skip down to the 4th part.

Game Design vs Level Design

This is a mistake I've seen many people make when discussing rules and content and stuff like that. Here it is: game design and level design are two different things. There's a lot of overlap, to be sure. Strong game design can go a long way towards shaping the level. And creative enough level design might involve some intrinsic game design, too. But don't confuse them.

Game design is when you make rules and procedures. It's answering the "how" in how things work. It's the description of how skill checks work, or how combat works.

Level design is when you make content with which to use those rules. It's answering the "what" in what the players are doing. It's the adventure module that tells you which skill checks to roll, and the encounters of monsters and battlefields where combat will be happening.

When Super Mario 64 came out in 1996, it was a smash hit and a breakthrough in gaming. It was the perfect 3D game, seamlessly translating the 2D genre of platforming into a 3D context better than any other attempt to do so. And trust me, the other attempts failed hard. It was an exceptionally tricky and ambitious design goal to tackle, but once they got it right, it blew the doors wide open for the future of 3D gaming. And you know how they did it?

First they designed the mechanics for Mario's movement. That's it. That's the only thing they focused on initially. They created the little minigame of chasing down the rabbit and catching it, so they'd have a way of testing their system. But they worked their asses off to make sure, above all else, that it was fun and easy to control Mario. That merely having to run around and jump on stuff and use your different moves was strong enough on its own. Only after they nailed that down did they begin to design the courses that would be in the final game.

First they nailed game design. Then, when it was so good it could be fun just by itself, then they poured their hearts and souls into making incredible levels. But the point is that these are two separate steps, and two separate goals. So I want to talk about the role that each one plays in tabletop design.

The Points Don't Matter!

That's right, the points are just like advantage on your check to attack Cthulhu!

People like being rewarded bonus points. Behold below and see the evidence of my claims! And then see my own method of serving this base, vulgar, hubris-laden need.