Jeremy Crawford Reveals All About The Cavalier From Xanathar's Guide

So the Cavalier appears in Xanathar's guide and it is a subclass inspired by a character class that goes all the way back to first edition D&D. The Cavalier in first edition D&D; appeared in the original book "Unearthed Arcana." So, in a way, when we were doing our "Unearthed Arcana" series of subclasses we thought "Well, of course, in a series named after the book, 'Unearthed Arcana' we should have the Cavalier in it." Although, we didn't end up including the acrobat which was another option in that book." says Crawford to D&D Beyond.

So the Cavalier appears in Xanathar's guide and it is a subclass inspired by a character class that goes all the way back to first edition D&D. The Cavalier in first edition D&D; appeared in the original book "Unearthed Arcana." So, in a way, when we were doing our "Unearthed Arcana" series of subclasses we thought "Well, of course, in a series named after the book, 'Unearthed Arcana' we should have the Cavalier in it." Although, we didn't end up including the acrobat which was another option in that book." says Crawford to D&D Beyond.



[video=youtube;KoFRbxfTN98]https://www.youtube.com/watch?v=KoFRbxfTN98[/video]


"So, the Cavalier is in many ways the classic knight in shining armor with the added twist of being outstanding at horseback riding. Now, many people might think "Well, the game already has the classic knight in shining armor, and that's the paladin." The big difference between the Cavalier and the paladin is that the paladin is a holy warrior usually dedicated, if not to a particular god, to a cause of some kind, to a great concept like justice. Whereas, the Cavalier is a non-magical warrior. One who can be just as honorable as a paladin but who might be driven by allegiance to a particular monarch, a particular kingdom, to the Cavalier's family, a particular town. So, it has, in a way, more a grounded earthy feel than the paladin, who again is often this figure associated with these high ideals and divine magic."

So, we actually showed off more than one version of the Cavalier in our "Unearthed Arcana" series. Both version actually got kind of a mixed reception, to be honest, from fans - good enough to make it into the book, but, each time the score, the satisfaction score was just on the line enough that we kept saying, "Okay, we've got to do more work." And really, the dissatisfaction came down to the fact that the Cavalier relying on the use of superiority dice which is a mechanic that we borrowed from the "Battle Master" one of the fighter subclasses in the Player's Handbook. Now, we thought people might be interested in seeing this mechanic propagated elsewhere. But, instead, often the feedback we got was "No, that's the Battle Master's. We don't want to see it in other fighter subclasses. We want to see them do their own thing."

Feedback on the Cavalier also at times was very anxious about the role of the Cavalier's mount because, as cool as it is to be on horseback, or dragonback or griffinback, or whatever it is that you are riding in D&D, people know that often, if you go into a tight cave or a dungeon that mount is not a whole lot of good to you. And, so it then becomes problematic if too much of your class features rely on your mount being present because you could potentially wander into a particular environment and feel like "poof", half your character's abilities just got turned off. We wanted to make sure that in the final version of the Cavalier, the version that appears in the "Xanathar's Guide" we address those concerns.

So, in the version that's in the book is actually quite different from any version that people saw in the "Unearthed Arcana" series. What we ended up doing is, we took the parts that people liked best about the Cavalier. Then, we looked at some of the other subclasses we really released on the "Unearthed Arcana" series for the fighter, and that was the knight. And the knight and the Cavalier were super close to each other in terms of story. And again, story is our starting point with design for our subclasses. And we know as we were thinking about what was going to make it into this book, it was very unlikely that both the Cavalier and the knight were going to make it in. And, in fact, their scores were really close and the Cavalier just edged out the knight. And that's why the Cavalier ended up being the one that went in.

I have a feeling the Cavalier edged out the knight partly because of the nostalgia some people have for the name. You know, it goes all the way back to the first edition. It's also a name that appears in the "Dungeon's and Dragons" cartoon. Granted, for probably the most unlikable character
in the show... the strange Cavalier who does not have any kind of weapon and also does not have a mount. Poor Eric.

What we ended up doing for the final version is we went to the knight and looked at the features that people like the best there, took those, took the best features of the Cavalier and wove them together into essentially a brand new subclass. And really, the theme of this subclass and this is something that came up in both the Cavalier and the knight in their previous designs is that they are all about protecting others. Because, again, these are knights. Even if they are not, even if a particular Cavalier isn't a paragon of good, the Cavalier is going to be about protecting property, people, something. And so, the Cavalier has class features that are about protecting those around him or her.

And then we also have a few features related to the mount, but we made sure that the mount is always, sort of like, a little extra. For most of the features the mount is not required. But the Cavalier will always be happy when the mount gets to shine. But, in a way, the mount is kind of frosting. And also, it is important to us that the Cavalier has an identity of its own. That's not reliant on this other creature being present. Because even in history where we had Cavaliers there was so much more than horse-back riders. I mean, they were knights with many other responsibilities and martial abilities. Although, we do point out in the book and this was something we pointed in "Unearthed Arcana" as well that the Cavalier is not meant to be an accurate portrayal of Cavaliers in history.

And that's true for anything in D&D. D&D is often filled with things that were inspired by things from real world history, myths from different human cultures, and D&D always sort of takes them and transform them, and often turns them into an archetypal form that feels natural in high fantasy. And that's really what we've done with the Cavalier who is now this mighty protector, awesome at holding the line and locking people down who try to run away. Really great at charging into battle whether on foot or on horseback and doing mighty initial strikes.

I think people are going to enjoy what emerged from the kind of revision process that we went through over those multiple versions that appeared in "Unearthed Arcana" and then culminating in the version that appears in the book."



Screen Shot 2017-09-27 at 18.11.31.png
 

log in or register to remove this ad

default_entry

First Post
I'm actually fine if they have a little overlap between "Fighter who is a X" and "Class X". Go on and give battlemasters the full class treatment in a later edition- or even dip into those prestige class rules! Make it a 15 level class you take *instead* of continuing as a fighter. Want the guy with a fancy-pants mount? make a cavalier class, even if there's a fighter archetype.
 

log in or register to remove this ad

Sacrosanct

Legend
One of my big peeves about the paladin acting as the default knight class was the spells. Like many people who have issues with rangers having spells, I had issue with all paladins having them for that particular archetype. Admittedly it wasn't a huge problem with me, because when I want to play a knight, I've always just played a fighter who acted like a knight. Worked fine. But it's nice to see a spellless paladin of sorts officially.
 

I have to say, I'm glad they didn't give superiority dice to every fighter subclass. I know several people who vastly prefer the simplicity of the champion, and would be deeply upset if there weren't such a mechanically simple fighter option.

That said, I'm not opposed to other SD-based subclasses. They just have to do something very different with it than the battlemaster. It can't be "like the battlemaster, but with fewer or only slightly differing maneuvers."
 

lkj

Hero
I have to say, I'm glad they didn't give superiority dice to every fighter subclass. I know several people who vastly prefer the simplicity of the champion, and would be deeply upset if there weren't such a mechanically simple fighter option.

That said, I'm not opposed to other SD-based subclasses. They just have to do something very different with it than the battlemaster. It can't be "like the battlemaster, but with fewer or only slightly differing maneuvers."

It's a sailed ship. But what if the battlemaster had been several subclasses to begin with, each restricted thematically to a particular set of maneuvers? Or maybe there was a set of 'general maneuvers' that any battlemaster could choose from and then specialty maneuvers that fit your subclass thematically?

I'm honestly asking. It's been something I've wondered about since the battlemaster was first released. Another option, of course, would be to just have a big pool of maneuvers and you can build your own (with some suggested combos for a 'cavalier', etc.). Then, rather than adding subclasses, you just add 'maneuver sets' to the maneuver pool. Disadvantage of that is that it could get overwhelming for someone coming in. Though the 'suggested sets' might solve that. Interactions that cause power creep is another problem with this approach.

Anyway. Just rambling.

AD
 

Alexemplar

First Post
You could have made a simple superiority dice mechanic. Just limit the use of Superiority die to Athletics checks, attack rolls, and damage rolls.
 

Mistwell

Crusty Old Meatwad (he/him)
Enough of the community threw fits about the "Warlord" class that they decided to throw it away in order to appease the small-minded, selfish Grognards.

I liked the Warlord. However, people disagreeing with you concerning matters of taste like which class they like does not make them small minded. And plenty of people who are on the newer end of the cycle of being players didn't like the Warlord as well, meaning it wasn't just Grognards. And finally, saying you don't like a class does not make one selfish any more than saying you like a class makes one selfish. You might want to check your assumptions on this issue. They seem to be pretty misguided. And insulting, purely because people have different tastes than you.

It was literally the only base class of any D&D edition that they didn't properly bring back.

It's really not. In fact, this thread is about a class which existed in a prior edition which hasn't existed in this one. And in the video they also mention the Thief Acrobat, which still isn't back. Both of those have a much longer history than the Warlord, which was only around for what, three years?

Well... as things stand, I am quite certain that reading between the lines of this PR talk that the Cavalier class is going to feel like a subpar Paladin unless they have their mount-- and mounted combat is so very uninteresting in 5E that basically no adventures utilize it.

He addresses this issue and says that's not how it will work. So where are you getting that?
 

GreenTengu

Adventurer
I liked the Warlord. However, people disagreeing with you concerning matters of taste like which class they like does not make them small minded. And plenty of people who are on the newer end of the cycle of being players didn't like the Warlord as well, meaning it wasn't just Grognards. And finally, saying you don't like a class does not make one selfish any more than saying you like a class makes one selfish. You might want to check your assumptions on this issue. They seem to be pretty misguided. And insulting, purely because people have different tastes than you.

No, saying you don't like the class doesn't make one small-minded and selfish.
Saying that the class should never be officially published in any form for any person to ever play or you will boycott the entire edition and get everyone else you know to do so as well makes one small-minded and selfish.

And you know which one they did?...
Yeah, it was the second one. Its why it isn't in the PHB when even the 4E version of Tiefling and the watered-down Dragonpeople are in the book, and instead of making it in an expansion book they are instead making these really niche subclasses that aren't going to be very satisfying because they designed subclasses in a way that there really isn't much you can do with one to alter the class as drastically as they want to do so.


One only gets 5 levels at which a subclass gets features that are distinct from the standard class. Just level 3, 7, 10, 14 and 18. Using only those 5 levels out of a 20 level progression they are going to try to duplicate the abilities of the Paladin in the Fighter class. Moreover, some of those features are set aside for mount abilities despite the fact that they acknowledge that basically no one uses mounted combat.

So take a moment and reflect on that. Then you will realize... obviously that can't work.
 

Pauln6

Hero
This is why it's a shame that superiority dice have been stripped out. The 5minute work day maneuvers and commander fan supplement has manoeuvres based off 4e Warlord tricks that you could allow someone wanting to play a Warlord to pick instead of the phb ones. There is also a Warlord subclass if you want to go that far.

If a subclass has access to SDs then the martial adept feat allows expansion into themed manoeuvres. It's a sticking plaster using fan content but linking it to manoeuvres means you can allow your players to dip as lightly or as heavily as you want. Subclasses can limit the choice of manoeuvres to certain features or certain thematic manoeuvres. Without the SDs the subclasses are stuck with more limited customisation.
 

Mistwell

Crusty Old Meatwad (he/him)
No, saying you don't like the class doesn't make one small-minded and selfish.
Saying that the class should never be officially published in any form for any person to ever play or you will boycott the entire edition and get everyone else you know to do so as well makes one small-minded and selfish.

And you know which one they did?...
Yeah, it was the second one.

I think a couple of people did that, and I think it had zero impact on how this game was designed. I think your assumptions about why the Warlord is not in this game are completely unsupported and are based mostly just on your own personal disappointment rather than what actually happened.

Its why it isn't in the PHB when even the 4E version of Tiefling and the watered-down Dragonpeople are in the book, and instead of making it in an expansion book they are instead making these really niche subclasses that aren't going to be very satisfying because they designed subclasses in a way that there really isn't much you can do with one to alter the class as drastically as they want to do so.

So far their subclasses and expansion books have sold extremely well. Maybe your view isn't well shared?

So take a moment and reflect on that. Then you will realize... obviously that can't work.

Or they can work just fine, like they have been working just fine, and it's just not your preference?
 

Chaosmancer

Legend
I have to say, I'm glad they didn't give superiority dice to every fighter subclass. I know several people who vastly prefer the simplicity of the champion, and would be deeply upset if there weren't such a mechanically simple fighter option.

That said, I'm not opposed to other SD-based subclasses. They just have to do something very different with it than the battlemaster. It can't be "like the battlemaster, but with fewer or only slightly differing maneuvers."

Yeah, like you said the problem with the 2nd UA cavalier was not the fact that it used superiority dice


It was the fact that they had what, 4 or 5 manuevers, 2 or 3 of them were simply taken directly off the Battlemaster list, one was only useful in adding to Animal Handling Checks (which have come up exactly once in my entire time running 5e) and then they had one ability that was unique and interesting.


And if you are going to have 75% or more of the useful maneuvers just be the exact same manuevers the Battlemaster already has access to, why bother with a new subclass at all, it is majority battlemaster.


Of course, the secondary problem is that they did not plan for different versions of Superiority dice in the game when they designed the Battlemaster, so there is a large amount of space that the Battlemaster fills at it is going to be very difficult to create additional maneuvers that are not simply re-skinnned versions of what the Battlemaster can do.
 

Related Articles

Remove ads

Remove ads

Top