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).

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

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.

Brave Design Notes 2: Items and Shopping

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 1: Various Rules

Go to the master post

Art credit: Hal Foster

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. It may also be valuable to see the character sheet, which you can find two copies of here.

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.

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.

Brave Class Hack Beta (again)

Picture is also a link to content

One of my most popular posts was the first Brave Class Hack, where I shared with the world my weird class system as well as the Knave, Warrior, Thief, and Cleric classes. I've made a lot of changes since then, including the addition of 3 more classes, so I figured it would be a fine time to update the world.

For anyone reading this who doesn't know, Brave is my personal hack of Ben Milton's Knave, which you can find the latest draft of linked on the sidebar of this blog as well as right here. If that link ever dies, it's because I forgot to return to this blog post to replace it. But the sidebar one should always be up to date.

Here is a link to the latest copy of the Brave: Enchiridion of Fates and Fortunes with some designer notes included. I also thought I might provide a preview below on each of the classes currently included, if you read below:

A Faction System That Doesn't Get in the Way

I'm following up on my last article but I get tired of numbering every blog post that's related to another because not everything is always part of a planned series, you know?

Once again, I need to credit Gundobad Games for sparking this thought process, albeit in a completely different context from last time. It was many months ago when I was trying to do research on domain-level play and I dug up a bunch of reddit posts about it and read people's game recommendations and blablabla and one of the most fruitful things I found were these blog posts: Part 1, Part 2, Part 3, Part 4. I could say a lot about those posts but right now I'm just gunna focus on Part 3, and I'm gunna re-write everything relevant from it here.

So the writer was putting a spotlight on Chris McDowell's Into the Odd, a nifty minimalist old-school RPG, and in particular, on its faction system. He calls them "enterprises" which is a decent name. Here is the full text of Into the Odd's enterprise rules, reproduced here:

Between expeditions, you can try your hand at business, or muster a military force. DETACHMENTS and ENTERPRISES each cost 10 Gold to establish. Detachments demand a further d6 Gold in upkeep each month, or else they revolt.

Income: New ENTERPRISES generate 1d4 Gold of Income each month. They also face a Threat that will cause 1d4 Gold in Losses unless dealt with. If an Enterprise cannot pay its debts, it collapses. Growth: If an ENTERPRISE ends a month with Profit, its income moves up to the next type of die, to a maximum of d12. However, this larger die also applies to losses from Threats.

By the by, a "detachment" is his name for a group of warriors fighting together, which we won't be discussing here. Maybe another day.

Anyway, today I'm gunna talk about the strengths and weaknesses of this system, the more immediate ways in which I've thought to tweak it, and then how I might go about reconciling it with all those other thoughts I vomited up in my last post.

A Freeform-Based Faction System

This isn't anything concrete, it's just stuff I've been swishing around in my mouth for a bit now.

I've been thinking of posting an article about "freeform mechanics" in RPGs, and I still might. But the basic idea is "resolving stuff in the game using your imagination and judgement rather than actual rules or mechanics," but, like, to the extreme. Like, say, maybe you want to run a war between two armies. On one end of the spectrum, you'd have a military simulation board game that defines each of your assets and unit types and whatever kinds of fictional resources you spend like "action points" or something, and it has a list of moves you can take and blablabla. Nothing freeform about it. On the other end of the spectrum, you'd ask the players to describe what they command their army to do. Just, like, from their creative thinking skills. Intimidating, right? But liberating. Exciting.

[EDIT: I was provided the source for this story so I'm re-writing this chunk to be accurate] 

I've been reading a truly ridiculous amount of literature on the subject and I want to share this anecdote from Gundobad Games:

My favorite example so far: from Tony Bath's old Hyboria campaign - one player was concerned about a potential rival's construction of a naval fleet, but didn't want to openly provoke hostilities. So he asked Bath whether he could arrange an 'accident' - merchant ships sinking [scuttling!] right at the mouth of the rival's harbor, blocking their port for the near future! Bath agreed, came up with a range of likely results, and then rolled the dice...

I love that. I love the freeform potential of RPGs and I keep finding myself drawn to that direction of design. But it's a double-edged sword. Because of the "tyranny of the blank canvas," many players find freeform gaming to be really unintuitive. When you ask them what they want to do, they don't have an answer. They're more comfortable if you give them options to pick from.

So here's something I've found in the middle that I'm working with and I'd like to share. I'm going to give three examples that illustrative something like what I'm approaching. These are all examples of "freeform but with a little bit of structure, just, like, for help."

Organization and Presenting Content When Making an RPG

Art credit: Trina Schart Hyman

The original Knave ruleset is a 7 page document. The current "latest draft" of Brave on the sidebar of this blog is 10 pages. I already know the final version will be expanding at least a little bit more. Part of the wonderful thing about Knave is how short it is. Players used to 300+ page rulebooks are shown those measly 7 pages and are amazed by how quickly they'll be able to jump into the system. So, obviously, I'd like to replicate that virtue.

But I have more content to add in. While many gamers prefer "rulings over rules" and don't want the game to tell them how to do every single last tiny activity imaginable, the implication is that they'd rather come up with their own rules for those activities. Maybe on the fly, but their own rules nonetheless. These same people often advocate making sure to use your on-the-spot ruling consistently from then on if possible, meaning that it would best be codified somewhere. Well, while I have shared Brave with the world with the intention of other people using it, it is fundamentally a collection of my houserules for my table. If I played something like 1st Edition AD&D and rejected their rules for an activity, then the substitute I come up with would go in Brave, because Brave is "the rules DwizKhalifa uses in his campaign." I've made a special effort to make the whole thing as modular and hackable as possible, just as most other DIY games do. Just like any good OSR game, nothing will break if you substitute my HP system or my magic rules or how I run wilderness stuff. But on the other hand, I know I'm not the only one tired of buying "incomplete rulesets" because creators are just a little too dedicated to the DIY ethic. In my mind, my own rules wouldn't be worth putting out to the world unless they were comprehensive enough to cover all of my needs. So, yes, it's worth including, say, the rules I use for sailing.

So we have a problem. I want the "core rules" to remain simple and easy to offer up to a player (like how 1st edition AD&D had the Basic counterpart, or how 5E D&D offers free Basic Rules online). But I also want to add more content, and when that sort of content is adopted for your campaign and you find yourself commonly using it, you'll wish it were included in the core rules. I play 5E D&D and ever since Xanathar's Guide to Everything was released, my group has been using the expanded rules and guidelines for toolsets. They're great! But we constantly find ourselves wishing that stuff had just been in the Player's Handbook rather than looking it up in the "miscellaneous other shit we're adding into the game" chapter in a supplement book. I'm sure if 5.5 Edition ever came out, they would relocate that stuff to the PHB. The only reason it wasn't there all along was because those rules didn't exist in 2014.

So how do I package all my content? I have a few ideas, so strap in.

Outline of Brave's Magic System

God I fucking hate magic systems.

Seriously, is there anything that epitomizes pure nerdiness more than designing magic systems? Part of me feels like I seriously wouldn't mind playing fantasy dungeoncrawl RPGs with absolutely no magic for eternity.

But I also love wizards, dammit.

Okay, I assure that what follows will not be lame and cliched. No "elemental spheres of magic + soul + positive + negative + whatever other stupid word" diagrams. I don't want to pick on anyone specifically because worldbuilding is very personal to people and it can be difficult to open up and share. But just go on reddit.com/r/worldbuilding and search "magic system" and you'll see plenty of examples of the kind of diagram I'm talking about. I will not abide such rampant nerdiness.

The logic of my system that follows is mostly a response to issues with the conventional D&D magic system and inspiration from Necropraxis's Wonders & Wickedness and Marvels & Malisons. The basic goal is to open up possibilities and begin allowing for far more, zanier ideas about what can constitute a "school" of magic.

Decent Rules to Make Languages Fun

First, here's some supplemental reading you may find insightful. All of it is from other RPG bloggers tackling the same subject as me:

1. https://goblinpunch.blogspot.com/2020/04/dungeoncrawling-languages.html 
2. https://monstersandmanuals.blogspot.com/2016/03/on-language.html
3. https://monstersandmanuals.blogspot.com/2008/11/languages-or-why-we-shouldnt-be-able-to.html
4. https://falsemachine.blogspot.com/2020/05/soft-ass-d.html (he covers language as a specific part of the post and I think his take is neat)
5. https://thelastdaydawned.blogspot.com/2016/11/making-languages-make-sense.html
6. http://thealexandrian.net/wordpress/38698/roleplaying-games/untested-fantasy-lorem-ipsum
7. https://www.paperspencils.com/making-languages-relevant/

The RPG Mausritter, about playing as tiny mice in a fantasy world, has some really cool language rules that I don't think can easily work for most other settings:

As a general rule of thumb, the more closely related two creatures are, the more likely they are able to be able to understand each other. Use the creature’s taxonomy to make a ruling. Magical or highly intelligent creatures may break these rules. • Same species (mouse): Can easily communicate. • Same family (rodent): Can speak and communicate, with some difficulty and difference of custom. • Same class (mammal): Make a WIL save to see if communication is possible. • Otherwise: Can’t directly communicate.

So yeah, all those thoughts are very neat. I'll throw in my two cents.

A Revised Dungeoncrawl Procedure

I recently drafted this page on dungeoncrawl procedure I may add to Brave. It needs playtesting. Some of it's weird, so I felt like it would be worth explaining the design choices I made. My intention is that this page would comprise 100% of the dungeon-related advice and rules in the game. But for context, earlier in the rules I've established a timescale called the "active turn" that lasts 10 minutes, which should be familiar. The main reason I even felt this was worth making and putting into the game was because, the more I thought about it, the more I believed that 1) having a committed dungeoncrawling procedure has great value, especially baking one into the system itself, and 2) I have issues with the standard options.

For those who want context on the old-school tradition of dungeon procedure, I'd point you to threads like this one, this one, and this one. But of course, the main point of contrast is going to be the codified procedure from B/X D&D, as re-packaged by Old School Essentials (courtesy of Necrotic Gnome), which is far and away the most popular option these days. Here is the 2-page spread included in OSE:

Let's talk about what they have in common before talking about the differences. 1) There is a play sequence up front, which is there for both the referee and the player to see and understand. 2) They both cover movement, traps, random encounters, and at least a little bit about miscellaneous common activities. So what's my problem with the original?

BRAVE Character Sheets

Finally got around to this part, since I always treat it as an afterthought. So here's the deal. In Brave, there are two character sheets. The first (link to it here) is for new characters up to level 3. As you can see, it's small enough that you can fit two on one sheet of paper. Anything that doesn't have a designated place on this sheet but that you need to write down, go ahead and jot it on the back.

Then, once you reach level 4, you've proven yourself a cut above the rest and have probably outgrown that old sheet. You have a decent chance of maybe not dying young, so it's worth it to actually have a full sheet. That's where this second (link to it here) sheet comes in.  I figured that, even though I'm adding a lot onto Knave, the majority of characters are still gunna be pretty disposable and won't need a full sheet.

I'll need to playtest these as well but they look promising. And anything on there that you might not yet recognize (the speeds, languages, whatever) are gunna be in the next draft of Brave so don't worry.

-Dwiz