D20 Design Diary: Why Do Inquisitors Get Teamwork Feats?
After I posted my draft of a Starfinder version of the PF1 inquisitor class, game designer and industry veteran Ryan Costello asked me a key question (and gave me permission to quote him on my blog about it):
“I noticed you mentioned in the conclusion that you are carrying over the PF1 Inquisitor teamwork feat focus. I always saw it as a strange fit for the theme. Any insight into why the class went that direction and why you are keeping it?”
So, this blog post is essentially my response.
I can only guess at the original design intent behind granting inquisitors bonus teamwork feats and solo tactics (which lets an inquisitor treat their teammates as having the same teamwork feats, making them much more useful) as a class feature in PF 1. While I worked on the book that was was introduced in, it was as a freelancer and all my work was to fill out support sections (archetypes, feats, spells, and so on), rather than do any design work on the base classes themselves. It’s worth noting that book was the APG, which is also where teamwork feats themselves were introduced, so it might be a simply and pragmatic decision to have one of the new classes tie into the new category of feats (as the cavalier class also did), and help differentiate them from clerics.
Of course one of the biggest fictional settings to heavily feature inquisitors is Warhammer 40k, and in that setting most inquisitors have a team of specialized agents that work for them. That doesn’t immediately equal teamwork, but the connection isn’t so tenuous I would discount it.
And you have to give inquisitors some kind of thematic hooks, and real-world examples of things like torture and bigotry don’t lend themselves well to the kind of heroic character Pathfinder mostly assumes players take the roles of. Also, with solo tactics, it’s less that an inquisitor is good at teamwork (working with people), and more that they are good at predicting how both allies and enemies will react in a way so precise they can use teamwork feats even when no one else is trained in those techniques, or even trying to use them. The inquisitor can work off people, taking advantage of their mere presence, almost like a kind of Super Combat Sense Motive.
Ultimately, I included the same thematic ideas because I set myself the task of creating a Starfinder version of the Pathfinder class, and I think this is a key element of that class, regardless of what the original thinking behind it was. But the fact it’s a different ecological niche remains true in Starfinder, which helps differentiate my inquisitor in a game system where there have been only 2 attack bonus progressions and 2 spell progressions to date, so something brand new always helps a class stand apart.
And, of course, since I designed my own teamwork feats, and plan to introduce them in the same book I introduce the final version of the Starfinder Inquisitor, the pragmatic consideration also applies. By putting a class with teamwork feats as a part of their legacy into a book that adds such feats (or, rather, my improved Starfinder versions of those feats) to the game, I am also driving greater engagement with different parts of the book.
Writing things like this is work, and it takes time from my other paying projects. If you got any use out of this article, or have enjoyed any of my content, please consider supporting my Patreon to cover the cost of my doing it. You can join for the cost of a cup of coffee a month.
Posted on September 6, 2021, in Business of Games, Game Design, Starfinder Development and tagged Base Classes, d20 Design Diary, Essays, Game Design, gaming, Geekery, SF Inquisitor, Starfinder. Bookmark the permalink. Leave a comment.
Leave a comment